Separate your teams safely on a shared GKE cluster.
Plans and configures isolated team environments on shared GKE clusters with access controls, resource limits, and cost attribution.
When to use it
Use when teams share a GKE cluster, environments need isolation, access needs least-privilege controls, or costs need team attribution.
Give it a GKE multi-tenancy setup request; it configures team namespaces, isolation controls, resource limits, and cost allocation on the cluster.
Cluster configuration requires an existing GKE cluster.
Uses kubectl to create and label team namespaces.
This skill
GKE
Configures isolation on your GKE cluster
Cloud Billing
Views GKE cost allocation