Add kubeadm v1beta4 support for Kubernetes 1.36+ - #481
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6c49a05396
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| featureGates: | ||
| KubeletInUserNamespace: true |
There was a problem hiding this comment.
When this template is selected for the newly supported 1.36.1 image, kubeadm writes KubeletInUserNamespace into the kubelet configuration, but Kubernetes 1.36 has removed that feature gate. The kubelet rejects the unknown gate and never becomes healthy, so 1.36+ KindContainer instances—including the default latest version—fail during provisioning; omit this feature-gate entry from the 1.36 template.
Useful? React with 👍 / 👎.
1 participant
Adds a kubeadm v1beta4 configuration template and selects it for Kubernetes 1.36.0 and newer.
This is stacked on top of the KindContainer 1.36.1 support PR so CI can exercise the new kubeadm configuration immediately with Kubernetes 1.36.1. Older Kubernetes versions continue to use the existing v1beta3 template.
The migration mirrors upstream kind's version boundary: kubeadm v1beta4 is used from Kubernetes 1.36 onward, while Kubernetes 1.37 removes v1beta3 support entirely.
Notable schema changes in v1beta4 include list-based
extraArgsandkubeletExtraArgs, which are reflected in the new template.