Q: A developer says they can't list pods in the `production` namespace but they can in `staging`. How do you debug this?
RBAC controls are namespace-scoped. Check:
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: "Kubernetes is a declarative desired state system; understanding the reconciliation loop is how you diagnose this quickly. 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
RBAC controls are namespace-scoped. Check:
kubectl auth can-i list pods --namespace=production --as=— quick check.kubectl get rolebinding -n production— see what roles are bound in the production namespace.kubectl get clusterrolebinding | grep— check if there's a cluster-level binding.
Remediation & Permanent Safeguards
Fix: Create a RoleBinding in the production namespace giving the user the view or appropriate role:
kubectl create rolebinding dev-view --clusterrole=view --user=<username> -n production
- kubectl auth can-i list pods --namespace=production --as= — quick check.
- kubectl get rolebinding -n production — see what roles are bound in the production namespace.
- kubectl get clusterrolebinding | grep — check if there's a cluster-level 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 developer says list 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 developer says list
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 developer says list 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 developer says list Cluster events provide sequential timestamps of scheduler decisions, probe failures, and image pull timeouts essential for rapid root-cause isolation.