Hands-On Microservices with Kubernetes

Writing multi-tenant systems

Multi-tenant systems are systems where totally isolated entities share the same physical or virtual resources. Kubernetes namespaces provide several mechanisms to support this. You can define network policies that prevent connectivity between namespaces (except for interaction with the Kubernetes API server). You can define resource quotas and limits per namespace to prevent rogue namespaces from hogging all the cluster resources. If your system is already set up for multi-tenancy, you can treat a test namespace as just another tenant.