This message was deleted.

have you heard of https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/

are the following labels

<http://node-role.kubernetes.io/control-plane=true,node-role.kubernetes.io/master=true|node-role.kubernetes.io/control-plane=true,node-role.kubernetes.io/master=true>

not enough to prevent by default?

Those are labels, not taints 👍

Thanks, I added Taint and it works now. Is this just for K3d? I haven't seen the similar requirements for Managed K8s, like EKS, etc. It appears they automatically have it already.

K3d (like other local cluster tools, e.g. KinD, Minikube, microK8s, Docker for Desktop, Rancher Desktop) by default creates a single node which is a server/master/control-plane node. It would be pretty bad if that single node couldn't run a workload, right? In managed K8s, you usually don't even see the CP nodes and don't have access to them. Don't know how that is in EKS.

makes perfect sense, Thx!

👍

K3d (like other local cluster tools, e.g. KinD, Minikube, microK8s, Docker for Desktop, Rancher Desktop) by default creates a single node which is a server/master/control-plane node. It would be pretty bad if that single node couldn't run a workload, right

👏 👏 👏 👏 👏