gke-multitenancy

Configure multi-tenant GKE clusters with namespace isolation, RBAC, and resource quotas.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/wangx7/skills-collection --skill gke-multitenancy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gke-multitenancy
Source: https://github.com/wangx7/skills-collection/tree/main/google-skills/skills/cloud/gke-multitenancy
Command: npx skills add https://github.com/wangx7/skills-collection --skill gke-multitenancy

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about gke-multitenancy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure multi-tenancy in GKE to isolate workloads across multiple teams?

Configuring multi-tenancy in GKE involves using namespace isolation, network policies for traffic segmentation, and least-privilege RBAC to securely share a single cluster across multiple teams without manual configuration.

What is the best way to prevent resource contention in a shared Kubernetes cluster?

The best way to prevent resource contention in a shared Kubernetes cluster is by applying resource quotas and LimitRanges. These controls enforce fair resource usage and prevent any single team from consuming all available compute.

How do I track GKE cost allocation for different namespaces and projects?

You can track GKE cost allocation by enabling GKE cost allocation features and applying namespace labels. This attributes infrastructure spending to specific teams or projects, reducing cloud costs for consolidated workloads.

When should I choose hard cluster isolation over soft namespace-based isolation in GKE?

You should choose hard cluster or node pool-based isolation over soft namespace-based isolation when your compliance requirements and budget constraints demand strict boundary enforcement between teams sharing the GKE infrastructure.

Does soft multi-tenancy with namespace isolation work for compliant workloads?

Soft multi-tenancy using namespace isolation works for compliant workloads when combined with least-privilege RBAC, network policies for traffic segmentation, and resource quotas to enforce secure and fair usage across teams.