Back to all scenarios
Scenario #279
Security
Kubernetes v1.22, Shared Dev Cluster
Shared Cluster with Overlapping Namespaces
Multiple teams used the same namespace naming conventions, causing RBAC overlaps and security concerns.
Find this helpful?
What Happened
Two teams created namespaces with the same name across dev environments. RBAC rules overlapped and one team accessed another’s workloads.
Diagnosis Steps
- 1Reviewed RBAC bindings across namespaces.
- 2Found conflicting roles due to reused namespace names.
- 3Inspected access logs and verified misuse.
Root Cause
Lack of namespace naming policies in a shared cluster.
Fix/Workaround
• Introduced prefix-based namespace naming (e.g., team1-dev).
• Scoped RBAC permissions tightly.Lessons Learned
Namespace naming is security-sensitive in shared clusters.
How to Avoid
- 1Enforce naming policies.
- 2Use automated namespace creation with templates.