The Namespace Scaling Problem

▶ Watch (0:23)

Most teams start with three namespaces: dev, staging, production. At 200-300 microservices, that breaks down. kubectl get namespaces takes long enough to brew a coffee. RBAC sprawls across dozens of namespaces with no coherent ownership. Developers work around quota limits by claiming new namespaces. The obvious fix is cluster-per-team multi-tenancy, but managing multiple clusters multiplies the patching and security burden, and developers break them too. The cloud provider sends a “thank you” letter for meeting their quarterly revenue target.

Capsule’s Tenant Model

▶ Watch (1:59)

Capsule sits between a namespace and a full cluster. A tenant wraps multiple namespaces into one boundary. Developer teams work inside that boundary with full self-service access, isolated from other tenants. Administrators allocate resource pools per tenant, and teams decide how to consume the allocation. Tenant configurations let admins set policies that govern how resources get used. The approach keeps costs low because teams share one cluster rather than owning one each.

Architecture Built on Kubernetes Primitives

▶ Watch (3:03)

Capsule uses standard Kubernetes primitives. The capsule configuration object handles RBAC: user groups, service accounts, and permissions. Network policies replicate from Calico and Cilium. The newest addition, resource pools, enforces tenant quotas so teams cannot exceed their allocation. Tenant owners define sub-policies within their tenant boundary. Developers simply create namespaces within it. The three-level hierarchy: cluster admin sets rules, tenant owners customize within those rules, developers consume.

GitOps Compatibility and Ecosystem Integration

▶ Watch (3:59)

Capsule integrates with the full CNCF toolchain. Argo CD works out of the box, making the project fully GitOps-compatible. Rancher, Velero, Calico, and Cilium also plug in. Adopters include Odyssey North and Kubermatic. For enterprise support, Qualitics and Pixie Labs contribute to the project and provide commercial backing. The team is at the project pavilion on Wednesday from 14:00 to 17:00 at P13A for a full demo.

Notable Quotes

enough time to make a coffee, come back, Hristo Hristov · ▶ 0:53

way too much for you. And what we do is Hristo Hristov · ▶ 2:08

Key Takeaways

  • Namespace sprawl and cluster-per-team both break at 200-300 microservices; Capsule sits between them.
  • The tenant abstraction wraps multiple namespaces and enforces resource quotas without requiring a dedicated cluster.
  • Capsule integrates with Argo CD, Calico, Cilium, Rancher, and Velero, covering GitOps and network policy out of the box.

About the Speaker(s)

Hristo Hristov is a Staff Engineer at Tide.co. He works on cloud-native platform engineering with a focus on Kubernetes, multi-tenant architectures, and policy-driven governance, and contributes to open-source projects in the Kubernetes space.