Multitenancy lets multiple independent teams or tenants share one platform while keeping workloads and resources logically separated. In Kubernetes, namespaces provide the logical partition; tenants remain physically integrated in the same cluster. section 3.2.6
Build safer tenant boundaries with namespace-scoped controls:
- Use namespaces to scope resource names and organize each tenant's workloads. section 3.2.6
- Apply RBAC to control which users and administrators can access tenant resources. section 3.2.6
- Combine resource quotas, network policies, and namespace security resources to constrain usage and communication. section 3.2.6
Namespace-based tenant identity
A sales namespace can contain services such as myweb1 and myweb2, whose cluster DNS names include the namespace: myweb1.sales.svc.cluster.local and myweb2.sales.svc.cluster.local. section 3.2.6
Centralized multitenant operations can aggregate clusters and workloads into one dashboard, but require safeguards because administrators may not need access to every environment or tenant. section 2.1


