Emergency-management builds a single-node kubeadm lab and needs application Pods to schedule on the control-plane node. What must they understand about the default control-plane taint?
Select an answer to reveal the explanation.
Short Explanation
By default the control plane is like a locked server room—workloads aren’t invited unless you unlock the door. kubeadm stamps a NoSchedule taint on that node, so app Pods bounce elsewhere (or stay Pending on a single-node lab). For a throwaway lab you can remove the taint on purpose; just don’t treat that as everyday production advice.
Full Explanation
kubeadm marks control-plane nodes with a NoSchedule taint so general workloads prefer (or require) workers. On a single-node lab, administrators often remove that taint or add matching tolerations so application Pods can schedule. Production HA designs normally keep control-plane taints in place and run workloads on workers.