Namespace Multi-Tenancy, But All The Problems Related To It
summary
Kubernetes hits scale pain around 200–300 microservices, where namespaces and clusters both fail; Project Capsule wraps multiple namespaces into a tenant that enforces replicated RBAC, network policies (Calico, Cilium), and per-tenant resource pools to prevent quota overrun. It integrates with Argo CD/GitOps, Rancher, Velero and exposes tenant-level configuration so owners self-serve while admins control boundaries. Maintainer claims this reduces cluster sprawl, cost surprises, and developer friction by combining native primitives with a lightweight control plane.
AI-written summary · about
related talks
30mMulti-Tenancy in Kubernetes: How We Avoided Clusters Sprawl W...
40mMulti-tenancy in Kubernetes
37mMulti-Tenancy in Kubernetes: Best Practices Today, and Future Directions
51mMulti-tenant Kubernetes
26mThe Future of Multi-Tenancy in Kubernetes
40mPanel Discussion: Multi-Tenancy in Kubernetes: Current State and Future Roadmap
24mMulti-Tenancy: Tips, Tricks, Tools And Tests
05mProject Lightning Talk: Capsule: Launching Multi-Tenancy to New Kubernetes Horizons
