search

techno-tim / k3s-ansible

The easiest way to bootstrap a self-hosted High Availability Kubernetes cluster. A fully automated HA k3s etcd install with kube-vip, MetalLB, and more. Build. Destroy. Repeat.
https://technotim.live/posts/k3s-etcd-ansible/
Apache License 2.0
2.41k stars 1.05k forks source link

How to add more control plane modes without tearing down and reinstalling the cluster? #32

Closed rexdavid closed 2 years ago

rexdavid commented 2 years ago

Thanks for the video!

dennismi commented 2 years ago

Hi @rexdavid

You actually can. You just need to prepare the additional control plane node for ansible. And then add the node to hosts file, and re-run the site.yml ... then it will look like it is recreating the cluster when in fact it will just add the node to cluster, and the cluster will keep running...

I know this because I have added multiple clusters to an rancher install, and the new node just showed up in the correct cluster.

@timothystewart6 - you can close this issue, as it works like a charm. Thanks for the video, and the work on the ansible playbooks.

timothystewart6 commented 2 years ago

Thank you!

RodriMora commented 2 years ago

Hi @rexdavid

You actually can. You just need to prepare the additional control plane node for ansible. And then add the node to hosts file, and re-run the site.yml ... then it will look like it is recreating the cluster when in fact it will just add the node to cluster, and the cluster will keep running...

I know this because I have added multiple clusters to an rancher install, and the new node just showed up in the correct cluster.

@timothystewart6 - you can close this issue, as it works like a charm. Thanks for the video, and the work on the ansible playbooks.

Hi! This worked for me but only for adding worker nodes. I didn't manage to make it work with "control-plane,etcd,master" nodes