Usage Telemetry

[bryantbiggs]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

What is the outcome that you are trying to reach?

• AWS uses customer feedback and usage information to improve the quality of the services and software we offer to customers. We should look at adding the ability to measure the usage and adoption of EKS Blueprints in order to better understand what customers are utilizing today to drive future improvements and innovation

Describe the solution you would like

• One potential solution is to replicate the functionality used by the Kubeflow team
  • https://github.com/awslabs/kubeflow-manifests/blob/main/website/content/en/docs/about/usage-tracking.md
  • https://github.com/awslabs/kubeflow-manifests/blob/main/charts/common/aws-telemetry/templates/Job/aws-kubelow-telemetry-kubeflow-Job.yaml
• It would be great if the metrics generated could shed further light on:
  • What addons are customers utilizing from EKS Blueprints
  • Percentage of addons deployed via Terraform, ArgoCD, other
  • The number of EKS clusters created by EKS Blueprints
  • The number of EKS clusters where EKS Blueprint addons have been provisioned

Describe alternatives you have considered

• N/A

Additional context

• As with the Kubeflow implementation, users would have the ability to opt out of sharing telemetry data