update how KubeadmConfigTemplates are linked to machine deployments#25
Open
update how KubeadmConfigTemplates are linked to machine deployments#25
Conversation
added 2 commits
February 20, 2026 13:04
Currently the key `kubeadm` holds configuration to kubadm for all cluster machines. That implies that changing the kubeadm impacts in **all** machine deployments (including control planes). Add support to set custom kubeadmconfig per machine deployment; so, when needed, custom configs can be applied to each machinedeployment independently
lucasdc6
reviewed
Feb 20, 2026
| users: {{ toYaml $kadmconfig.users | nindent 8 }} | ||
| {{ end }} | ||
| joinConfiguration: | ||
| {{- toYaml (required ".Values.kubeadm.joinConfiguration" |
Collaborator
There was a problem hiding this comment.
Should this message be updated?
Author
There was a problem hiding this comment.
In general at the event of no defining any spec on the machine deploy the general kubeadm configs will be applied. This line does the trick
It can be a good place to harden a litle bit control planes or any other machine deploy granting different users access to those.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently the key
kubeadmholds configuration to kubadm for allcluster machines. That implies that changing the kubeadm impacts in
all machine deployments (including control planes).
Add support to set custom kubeadmconfig per machine deployment; so, when
needed, custom configs can be applied to each machinedeployment
independently