Skip to content

Conversation

@afbjorklund
Copy link
Member

@afbjorklund afbjorklund commented Jan 5, 2026

Allows joining an agent / worker to an existing cluster,
instead of creating a control plane node and doing reset.

Don't check for control plane config / images / processes,
and don't output any message about the kubeconfig either.

Fixes #4481

@AkihiroSuda AkihiroSuda added this to the v2.1.0 milestone Jan 6, 2026
Allows joining an agent / worker to an existing cluster,
instead of creating a control plane node and doing reset.

Don't check for control plane config / images / processes,
and don't output any message about the kubeconfig either.

Signed-off-by: Anders F Björklund <[email protected]>
There was no error, but the Param was always empty map.

Which made it impossible to customize the message text.

Signed-off-by: Anders F Björklund <[email protected]>
@afbjorklund afbjorklund force-pushed the kubernetes-join branch 2 times, most recently from 42cc3b3 to ac1bfb8 Compare January 7, 2026 11:37
@afbjorklund
Copy link
Member Author

There should probably be some more "elegant" method, of propagating parameters from master to minions...

Currrently you are required to run low-level commands on the node, and then copy them into a complex yq

This reverts commit 93055a1.

Signed-off-by: Anders F Björklund <[email protected]>
All commands are copied from the templates.

This leads to some duplication, but so be it.

Signed-off-by: Anders F Björklund <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

k8s: multi-node mode shouldn't require kubeadm reset

2 participants