What problem does it solve? Sharing a single GKE cluster across multiple teams risks resource contention, weak access control, and unclear cost attribution. This Skill provides the patterns and manifests needed to isolate tenants safely without provisioning separate clusters. ## Core Features & Use Cases - Namespace Isolation: Create labeled namespaces per team or environment with namespace-scoped RBAC Roles and RoleBindings bound to Google Groups. - Resource Governance: Apply ResourceQuotas and LimitRanges with mandatory default and defaultRequest values so no team can exhaust cluster capacity. - Network Segmentation & Cost Allocation: Deploy default-deny NetworkPolicies with DNS egress rules, and enable GKE cost allocation with cost-center labels for billing breakdowns. - Use Case: A platform engineer onboarding three teams onto one production cluster can use this Skill to set up per-team namespaces, least-privilege RBAC, CPU/memory quotas, and intra-team network policies in a single workflow. ## Quick Start Set up multi-tenancy on my GKE cluster with separate namespaces, RBAC roles, resource quotas, and network policies for two teams.