Skip to content

"kubeletconfiguration" patch target patches not respected on kubeadm join #3091

Closed
kubernetes/kubernetes
#126224
@neolit123

Description

slack
https://kubernetes.slack.com/archives/C2P1JHS2E/p1721299761889029

users are reporting that 1.30.2 does not respect a custom kubeletconfiguration.yaml patch that looks like this:

healthzBindAddress: foobar
healthzPort: 4321

reporduction steps:

  • create a kubeadm init single node
  • call kubeadm join ... --patches some-dir that has the above patch

what happens:

  • kubeadm join still uses the values for healthz in the kubelet-config config map and ignores the patches
  • /var/lib/kubelet/config.yaml is patched correctly.

i will investigate the problem.
cc @SataQiu i think we tried to fix a recent bug about that.

Metadata

Assignees

Labels

area/patcheskind/bugCategorizes issue or PR as related to a bug.priority/backlogHigher priority than priority/awaiting-more-evidence.

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions