Sharing is Caring: Your Kubernetes Cluster, Namespaces, and You
summary
Covers concrete namespace patterns (per-team, per-application, per-environment), risks like an accidental creation of 80,000 namespaces, and measurable controls: RBAC roles (admin/edit/view), ResourceQuota limits, PodSecurityPolicy and NetworkPolicy enforcement, and image whitelist. Recommends admission controllers for enforcement and using Open Policy Agent to push consistent policies across cluster groups, plus label-based cluster/namespace groupings and automated templates so namespaces are created with PodSecurityPolicy and quotas applied.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:27NAMESPACES VS. CLUSTERS
- 3:51USE CASE 1: ONE TEAM PER CLUSTER
- 5:23USE CASE 2: SHARED CLUSTERS
- 7:41WHAT DO YOU NEED TO CREATE VIRTUAL CLUSTERS ?
- 11:58COMMON APPROACHES
- 14:15INFRASTRUCTURE (CLUSTER) VS. APP (NAMESPACE)
- 16:44SECURITY BOUNDARIES
- 23:21QUOTA ENFORCEMENT
- 25:34HOW? ADMISSION CONTROLLERS
- 28:15PEOPLE ARE... MESSY
- 29:42CONFLICTING NEEDS
- 32:13HOW OPEN POLICY AGENT (OPA)
related talks
35mOMG Namespaces!
38mMulti-Tenancy Support & Security Modeling with RBAC and Namespaces
32mKubernetes Namespaces Unleashed: Unlocking the Full Potential of You...
32mClusters wla Namespaces? Kifach blan Multitenancy f Kubernetes
24mOne stop talk for kubernetes security !!
06mLightning Talk: Why Your Cluster-Wide Policies Are a Risk (And What To Do About It)
37mMulti-Tenancy in Kubernetes: Best Practices Today, and Future Directions
25mSecuring Kubernetes Multi-Tenancy: Navigating Challenges Through DevSecOps Control and Visibility
