⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All Kubernetes Interview Questions Scenario 46 of 207 in Kubernetes
Senior DevOps / SRE [L2] Kubernetes RBAC & Security Production Scenario [L2]
🎯 Target Role / Context: Kubernetes Scenario #33 (L2) · RBAC & Security

Q: You run a pod that needs to call the Kubernetes API (e.g., to list other pods). How do you set this up securely?

1. Create a ServiceAccount: kubectl create serviceaccount my-app -n my-namespace

#Kubernetes #RBAC & Security #L2 #Container Orchestration #K8s
🎙️ Candidate Opening & Architectural Context
""In our production Kubernetes clusters running microservices on EKS/AKS, this was a classic operational challenge. 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
⚡ Recommended Practice Lab

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: "In our production Kubernetes clusters running microservices on EKS/AKS, this was a classic operational challenge. 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."

1️⃣

Initial Diagnostics & Root Cause Analysis

The pod will then have a token mounted at /var/run/secrets/kubernetes.io/serviceaccount/token which it can use to authenticate to the API server.

  • Create a ServiceAccount: kubectl create serviceaccount my-app -n my-namespace
  • Create a Role with only the needed permissions (principle of least privilege):
  • Create a RoleBinding linking the ServiceAccount to the Role.
2️⃣

Remediation & Permanent Safeguards

Avoid using the default ServiceAccount — it often has more permissions than needed.

rules:
- apiGroups: [""]
  resources: ["pods"]
  verbs: ["get", "list"]
  • Set serviceAccountName: my-app in the pod spec.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Create a ServiceAccount: kubectl create serviceaccount my-app -n my-namespace."
⚡ 60-Second Elevator Pitch Talking Points
  • Create a ServiceAccount: kubectl create serviceaccount my-app -n my-namespace
  • Create a Role with only the needed permissions (principle of least privilege):
  • Create a RoleBinding linking the ServiceAccount to the Role.
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. Over-granting cluster-admin permissions to pod ServiceAccounts instead of scoping namespace Roles when addressing orchestration Over-granting cluster-wide permissions violates least-privilege principles and allows compromised pods to escalate privileges across namespaces.
  2. Referencing mutable latest container tags across production Kubernetes Deployment specs Deployments referencing :latest risk inconsistent versions across replica pods and break deterministic rollback capabilities.
  3. Omitting pod readiness probes, causing traffic to hit uninitialized application containers Readiness probes gate traffic delivery; missing probes cause Kubernetes to route user requests to pods before dependencies or caches are loaded.
  4. Executing diagnostic triage without analyzing chronological cluster events and describe outputs Cluster events provide sequential timestamps of scheduler decisions, probe failures, and image pull timeouts essential for rapid root-cause isolation.
Advertisement
📥 FREE DOWNLOAD · 101-PAGE COMPANION HANDBOOK
Studying for Kubernetes & SRE Technical Rounds?
Download the complete 100-question PDF field guide covering all 11 core modules with offline diagnostic runbooks.
📥 Download PDF (Free) Read Online Guide →
Want more Kubernetes scenarios?
Explore our complete collection of scenario-based Kubernetes interview runbooks.
Browse All Kubernetes Questions →