-
Notifications
You must be signed in to change notification settings - Fork 521
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configure kubelet parameters via BR API #2481
Comments
Thanks @nkvetsinski - this looks like good functionality to support. I don't have any timeframe yet, but I'll take a look and I should be able to get to this soon(ish!). ^^ That said, if any community members are interested in picking this up, just let me know. :) |
Small update, the |
Sweet! |
Here are the equivalent Bottlerocket settings: Existing
New in v1.11.0 (or whichever release after #2536 lands)
All cert settings take the base64 content of the files that will be decoded and written out on the host and the kubelet configuration will be updated to point to those local files. Disclaimer: New setting names are subject to change based on review feedback. Will try to remember to edit/update this comment with any changes. |
Updated the previous comment with the final names of the settings. This should be in the v1.11.0 release. |
What I'd like:
Our team needs to change some of the kubelet parameters (in our case we change
-v --client-ca-file, --tls-cert-file, --tls-key-file
). We would like to have these parameters exposed to the API, ideally all of the flags can be changed.Any alternatives you've considered:
To unblock our usecase we have created privileged host container that changes KubeletConfig file on the filesystem.
The text was updated successfully, but these errors were encountered: