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
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."
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.
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-appin the pod spec.
- 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.
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 addressing orchestration 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
Deployments referencing
:latestrisk inconsistent versions across replica pods and break deterministic rollback capabilities. - 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.
- 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.