[EKS] [Bottlerocket]: Ability to specify custom values to containerLogMaxWorkers & containerLogMonitorInterval kubelet configs for Bottlerocket
- 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**
I want to specify custom values to kubelet parameters: containerLogMaxWorkers & containerLogMonitorInterval.
**Which service(s) is this request for?**
EKS - Bottlerocket
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Bottlerocket ( aws-k8s-1.32* ) has default values set "containerLogMaxWorkers": 1, "containerLogMonitorInterval": "10s",
I want to specify custom values to kubelet parameters: containerLogMaxWorkers & containerLogMonitorInterval to improve our logging operations' performance.
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.
**Are you currently working around this issue?**
There is no alternate option available, via karpenter nodeclass or userdata, to pass custom values for these configs to bottlerocket's kubelet.
**Additional context**
I use Karpenter v1.3 + Bottlerocket (aws-k8s-1.32) in EKS.
Contributor guide
Research direction
No repository files, tests, or implementation entry points are identified. Start by reviewing how Bottlerocket configures the kubelet for aws-k8s-1.32 and where containerLogMaxWorkers and containerLogMonitorInterval are set. Done means users can supply custom values through a supported EKS or Bottlerocket configuration path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100