Skip to content
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

Question: Is it possible to add additional control plane nodes after initializing the k0s cluster? #721

Open
vyas-n opened this issue May 28, 2024 · 3 comments

Comments

@vyas-n
Copy link

vyas-n commented May 28, 2024

Hey Folks,

I currently have a k0s cluster deployed using k0sctl with the following topology:

  • node1 (controller+worker)
  • node2 (worker)
  • node3 (worker)

And I wondered if it's possible to add the following nodes to make the control plane HA:

  • node4 (controller)
  • node5 (controller)

I've previously added worker nodes this way no problem, I just don't know if control plane nodes can be joined the same way.

Is this possible using k0sctl?

@kke
Copy link
Contributor

kke commented May 29, 2024

It should be, but there is a bug that may prevent doing so in some conditions which will be fixed by #714

@twz123
Copy link
Member

twz123 commented May 29, 2024

NB: If you're going from single-node control plane to HA control plane, you need to have some sort of load balancing in place, then, and a restart of all workers (including the controller+worker) node is required to pick that up (in case of NLLB). In case of using spec.api.externalAddress, it might even be necessary to rejoin the workers, or manually adjust the k0s worker's kubeconfig files, to point to the new address.

@kke
Copy link
Contributor

kke commented May 30, 2024

Hmm, maybe some of those could/should be automated or at least detected in k0sctl?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants