[EKS] [request]: Allow configuring tracing
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, 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
**Tell us about your request**
We'd like to be able to consume the [default tracing generated by the apiserver](https://kubernetes.io/docs/concepts/cluster-administration/system-traces/#enabling-tracing-in-the-kube-apiserver). At minimum configuring the endpoint, but it would be useful to configure the sampling rate too.
**Which service(s) is this request for?**
EKS
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.
We're currently making use of a lot of Kyverno policies to manage our cluster, as well as ArgoCD, Datadog mutatingwebhookconfigurations, etc. Sometimes things get slow, or don't work, and it can be difficult to figure out why. Having all of this linked together by tracing would be great - but the apiserver sits in the middle, and we can't see what happens there. This slows down our response to issues, and wastes developer time.
**Are you currently working around this issue?**
No
**Additional context**
**Attachments**
Contributor guide
Research direction
Start with the linked Kubernetes system-traces documentation and the EKS service context; no repository files or tests are mentioned. Clarify how endpoint and sampling-rate configuration should be exposed, with completion meaning EKS can configure tracing for default kube-apiserver traces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100