-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Support Kubelet Config #8670
Comments
This issue is currently awaiting triage. If CAPI contributors determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
The One option for setting the KubeadmConfig would be to directly pass a file into the This is a very interesting discussion though - I think it's linked to #8425 |
ideally, CAPI should let kubeadm manage the kubeletconfiguration v1beta1 GVK.
+1 to close in favor of 8425, where documenting existing approaches was proposed. |
@killianmuldoon @neolit123 |
I prepared several examples for #8425. This would help for this purpose. |
@fabriziopandini: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What would you like to be added (User Story)?
In currently, when user add additional config of kubelet, user add params to KubeadmConfigSpec resource
.spec.joinConfiguration.nodeRegistration.kubeletExtraArgs
.But, recently kubelet warns some args will be removed and recommended that should be set via config file specified by kubelet's --config flag.
So when we use new version Kubernetes, this how to specify kubelet args maybe will be cannot use I think.
Therefore, I suggest to make setting KubeletConfig (https://pkg.go.dev/k8s.io/kubelet/config/v1beta1#KubeletConfiguration) via KubeadmConfig resource.
Detailed Description
NONE
Anything else you would like to add?
No response
Label(s) to be applied
/kind feature
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.
The text was updated successfully, but these errors were encountered: