Q: Someone accidentally ran `kubectl delete clusterrolebinding cluster-admin` and deleted the cluster admin binding. Now no one can manage the cluster. What do you do?
This is a serious situation. If you're locked out of the API server entirely:
Want to master this scenario in a live sandbox? KodeKloud's CKA & CKAD Hands-On Certification Track covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "When troubleshooting Kubernetes, I always follow a structured layered model: Pod status -> Events -> Logs -> Network. 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."
Initial Diagnostics & Root Cause Analysis
This is a serious situation. If you're locked out of the API server entirely:
- SSH directly to a control plane node.
- Use
kubectlwith the admin kubeconfig at/etc/kubernetes/admin.conf(setKUBECONFIG=/etc/kubernetes/admin.conf). This uses certificate-based auth that bypasses RBAC. - Recreate the cluster-admin binding:
Remediation & Permanent Safeguards
Prevention: Never give a single ClusterRoleBinding a name that might be confused with a default. Back up RBAC configs. Use --dry-run=client before destructive commands.
kubectl create clusterrolebinding cluster-admin \
--clusterrole=cluster-admin \
--user=<your-user>
- SSH directly to a control plane node.
- Use kubectl with the admin kubeconfig at /etc/kubernetes/admin.conf (set KUBECONFIG=/etc/kubernet...
- Recreate the cluster-admin binding:
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Over-granting cluster-admin permissions to pod ServiceAccounts instead of scoping namespace Roles when configuring Someone accidentally kubectl Over-granting cluster-wide permissions violates least-privilege principles and allows compromised pods to escalate privileges across namespaces.
-
Referencing mutable latest container tags across production Kubernetes Deployment specs when configuring Someone accidentally kubectl
Deployments referencing
:latestrisk inconsistent versions across replica pods and break deterministic rollback capabilities. - Omitting pod readiness probes, causing traffic to hit uninitialized application containers when configuring Someone accidentally kubectl Readiness probes gate traffic delivery; missing probes cause Kubernetes to route user requests to pods before dependencies or caches are loaded.
- Executing diagnostic triage without analyzing chronological cluster events and describe outputs when configuring Someone accidentally kubectl Cluster events provide sequential timestamps of scheduler decisions, probe failures, and image pull timeouts essential for rapid root-cause isolation.