Kubernetes - RBAC and Security
You created a ServiceAccount but your pod fails to use it. Which of these is the most likely cause?
You created a ServiceAccount but your pod fails to use it. Which of these is the most likely cause?
medium📝 Troubleshoot Q14 of 15
Step-by-Step Solution
Solution:
Step 1: Check namespace consistency
ServiceAccounts are namespace-scoped. If the pod is in one namespace but the ServiceAccount in another, the pod cannot use it.Step 2: Verify pod spec and ServiceAccount existence
Even if the ServiceAccount exists in the same namespace, the pod must specify the ServiceAccount name in its spec to use it.Final Answer:
The pod spec does not specify the ServiceAccount name -> Option DQuick Check:
Pod spec must specify serviceAccountName to use it [OK]
Quick Trick: Pod spec must specify serviceAccountName [OK]
Common Mistakes:
- Forgetting to specify serviceAccountName in pod spec
- Assuming missing secrets cause pod failure
- Blaming pod image unrelated to ServiceAccount
Master "RBAC and Security" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes