domains / families / devops / gke-multitenancy

gke-multitenancy

separate

Plans and configures multi-tenancy on GKE. Covers namespace isolation, RBAC planning for teams, resource quotas, LimitRanges, network isolation, and cost allocation. Use when designing GKE multi-tenancy, configuring GKE namespaces, setting up resource quotas, or isolating GKE teams. Don't use for single-tenant cluster configuration or general deployment instructions (use gke-basics or gke-app-onboarding instead).

When to use

• Multiple teams sharing a single GKE cluster
• Isolating workloads by environment (dev/staging/prod) within one cluster
• Implementing least-privilege access control
• Cost allocation across teams or projects

When not to use

• single-tenant cluster configuration
• general deployment instructions

Skill page

Source