[EKS] [request]: send control-plane logs to self-managed logging system
- 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're looking for a way to send the control-plane logs (API server, Audit, Authenticator, Controller Manager, and Scheduler) to a self-managed logging system and not only to cloudwatch.
**Which service(s) is this request for?**
EKS
Contributor guide
Research direction
No files, tests, or entry points are identified in the issue. Begin by investigating how EKS exposes control-plane logs for the API server, Audit, Authenticator, Controller Manager, and Scheduler, and define completion as sending those logs to a self-managed logging system rather than only to CloudWatch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100