Q: How do you run a pod on the control plane node?
Control plane nodes are tainted with node-role.kubernetes.io/control-plane:NoSchedule. Add a toleration to your pod: tolerations: [{key: ...
#Kubernetes #Additional Kubernetes Scenarios (Q101-Q200) #L2 #Container Orchestration #K8s
🎙️ Candidate Opening & Architectural Context
""In one of our high-traffic production clusters, our SRE team handled this incident using a standardized runbook. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix.""
Advertisement
🛠️ Production Runbook & Step-by-Step Resolution
1️⃣
Production Solution & Architecture
Control plane nodes are tainted with node-role.kubernetes.io/control-plane:NoSchedule. Add a toleration to your pod: tolerations: [{key: "node-role.kubernetes.io/control-plane", operator: "Exists"}]. Or use nodeSelector with the control-plane node label.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Control plane nodes are tainted with node-role.kubernetes.io/control-plane:NoSchedule. Add a toleration to your pod: tolerations: ."
⚡ 60-Second Elevator Pitch Talking Points
- Immediate Triage: Control plane nodes are tainted with node-role.kubernetes.io/control-plane:NoSchedule. Add a to
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Advertisement