gke-multitenancy

What problem does it solve?

Organizations sharing a single GKE cluster across multiple teams or environments struggle with securing workloads, preventing resource contention, and accurately tracking infrastructure costs without manual, repetitive configuration of isolation controls.

Core Features & Use Cases

• Multi-Tenancy Model Selection: Choose the right isolation level (soft namespace-based or hard cluster/node pool-based) based on your compliance requirements and budget constraints.
• Isolation & Governance Setup: Configure namespace-scoped RBAC with least-privilege access, network policies for traffic segmentation, and resource quotas/LimitRanges to enforce fair resource usage across teams.
• Cost Tracking: Enable GKE cost allocation and apply namespace labels to attribute infrastructure spending to specific teams or projects. Ideal for engineering leaders looking to reduce cloud costs by consolidating workloads into shared GKE clusters without sacrificing security or compliance.

Quick Start

Use the gke-multitenancy skill to set up namespace isolation, RBAC permissions, and resource limits for your shared GKE cluster to support three product teams.