Validate node reboots healthy about terraform-hcloud-kube-hetzner HOT 8 CLOSED

Ok for me, my cluster worked like a charm..

from terraform-hcloud-kube-hetzner.

@phaer @mnencia Worked like a charm! 🍾 k3s-control-plane-2 finally rebooted and was admitted back into the cluster like a prince! :)

from terraform-hcloud-kube-hetzner.

Folks, thanks to the "new pattern" for waiting for stuff without sleep, that I learned from @mnencia, was able to kill most sleep and we are now a lot faster! I believe in under 5 minutes, it is up and running for 5 nodes ⚡

from terraform-hcloud-kube-hetzner.

As you stated sooner, Rancher confirms that for HA, the number of control plane nodes must be odd, so a minimum of 3 indeed. Let's see! 🤞

Source: https://rancher.com/docs/k3s/latest/en/installation/ha-embedded/

from terraform-hcloud-kube-hetzner.

Seems to have worked like a charm, the last reboot command confirms it on the nodes, only node remaining to reboot is k3s-control-plane-2,

from terraform-hcloud-kube-hetzner.

Interesting learning, was that it did not reboot because there was a lock acquired on k3s-control-plane-1 already, so it waited the next hour to reboot.

from terraform-hcloud-kube-hetzner.

As soon as one of you validates the above with your own cluster, we'll be good to go into master.

from terraform-hcloud-kube-hetzner.

I believe we are good to merge to master, what do you think?

from terraform-hcloud-kube-hetzner.