-
Notifications
You must be signed in to change notification settings - Fork 288
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
KubeletConfiguration doesn't work while using ntpConfiguration #8594
Comments
Thank you for creating this issue. Do you mind adding more details about the cluster configuration? Was this a create or an upgrade? If it was an upgrade, what version was the cluster originally created with? What was the kubernetes version used? In the When the cluster was created, did the NTP server settings get set properly? |
Hi, @mitalipaygude !
I tried both creating new cluster, and upgrading freshly created cluster, behavior was the same in both scenarious. Every time I add
No, only
Yes, NTP settings was correct and got applied to nodes Example of config with both
|
Hello @kobin23 , thank you for the response. We are looking into this issue and mostly should have a fix in the upcoming patch release for the same. |
Fixed in v0.20.4 version |
What happened: Kubelet configuration didn't apply to kubernetes nodes, when ntp configuration used in VSphereMachineConfig manifests of these nodes
What you expected to happen: Kubelet configuration applied correctly along with configured ntp servers
How to reproduce it (as minimally and precisely as possible): Set any settings in kubeletConfiguration for controlPlane or workerNode (ex. maxPods), set any valid servers for ntp in VSphereMachineConfig manifests of nodes, for which kubeletConfiguration used
Anything else we need to know?: Bottlerocket OS used for cluster
Environment:
The text was updated successfully, but these errors were encountered: