k8s-multitenant
k8s-multitenant is a production-ready Helm chart that gives platform engineering teams a single declarative interface to onboard tenants onto a shared Kubernetes cluster. Instead of manually creating namespaces, writing RBAC manifests, and configuring resource quotas for each team, you describe your tenants in a values.yaml and the chart does the rest.
Repository: clouddrove/k8s-multitenant
Helm repository: helm repo add k8s-multitenant https://clouddrove.github.io/k8s-multitenant
Supported clusters: EKS, AKS, GKE
What it creates
For every tenant you define, the chart provisions:
| Resource | Purpose |
|---|---|
Namespace | Isolated workspace for the tenant |
ResourceQuota | CPU, memory, and object-count limits |
LimitRange | Default container requests/limits injected at admission |
Role + RoleBinding | Namespace-scoped RBAC with support for users, groups, and service accounts |
NetworkPolicy | Default-deny isolation with configurable allow-lists |
Architecture
┌──────────────────────────────────────────────────┐
│ k8s-multitenant Helm Chart │
│ │
│ tenants[].name ──► Namespace │
│ ──► ResourceQuota │
│ ──► LimitRange │
│ ──► Role + RoleBinding │
│ ──► NetworkPolicy │
└──────────────────────────────────────────────────┘
│ │ │
ns/team-alpha ns/team-beta ns/team-gamma
Quick install
helm repo add k8s-multitenant https://clouddrove.github.io/k8s-multitenant
helm repo update
helm upgrade --install tenants k8s-multitenant/k8s-multitenant \
-f values.yaml \
-n platform-system --create-namespace
Next steps
- Getting Started — full install walkthrough
- Configuration — all values explained
- Platform guides: EKS · AKS · GKE