Kubernetes - RBAC and Security
Why does Kubernetes use a provider list with multiple encryption methods (like aescbc and identity) in the encryption config?
Why does Kubernetes use a provider list with multiple encryption methods (like aescbc and identity) in the encryption config?
hard📝 Conceptual Q10 of 15
Step-by-Step Solution
Solution:
Step 1: Understand provider list purpose
The provider list allows Kubernetes to try providers in order, enabling key rotation and fallback.Step 2: Clarify fallback role of identity provider
Identity means no encryption; it allows reading old unencrypted data during rotation.Final Answer:
To allow seamless key rotation and fallback to unencrypted data. -> Option BQuick Check:
Provider list enables rotation and fallback [OK]
Quick Trick: Provider list supports rotation and fallback to unencrypted data. [OK]
Common Mistakes:
- Thinking multiple providers mean double encryption
- Assuming selective encryption by secret
- Believing encryption only during upgrades
Master "RBAC and Security" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes