Control-plane-0 should be tainted with 'node-role.kubernetes.io/master=true:NoSchedule' about terraform-hcloud-kube-hetzner HOT 5 CLOSED

Thanks for catching that @valb3r! I think keeping it optional, but tainting the control nodes by default would be the best choice as, in my understanding that's generally the expected behavior for kubernetes clusters? Could be different for k3s though?

from terraform-hcloud-kube-hetzner.

AFAIK, it is must have for production k8s clusters.
For k3s i.e. - https://gabrieltanner.org/blog/ha-kubernetes-cluster-using-k3s also enforces master node taints.
As here we are talking about Hetzner and therefore cheap clusters I would agree with @mysticaltech that it is optional parameter depending on workload, but it should be documented

from terraform-hcloud-kube-hetzner.

Ok, definitely a good thing to make optional! I for instance like to use all nodes for computing, but am not using things like Cassandra! So will give the option definitely 🙏

from terraform-hcloud-kube-hetzner.

Definitely, will do, but in the meantime, just shoot a PR adding a variable for that if you can, tainted by default indeed.

from terraform-hcloud-kube-hetzner.

Added by default, thanks again @mnencia!

from terraform-hcloud-kube-hetzner.