Agent skill · software engineering · google

gke-multitenancy

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).

Why this skill is useful

Provides specific GKE multi-tenancy configuration patterns and Kubernetes resource management commands that the AI wouldn't reliably generate on its own.

What it needs

Requires kubectl installed locally. About 3k tokens when loaded. Last updated 2026-08-06. 15,831 stars on the source repository.

What this skill does

GKE Multi-Tenancy This reference covers enterprise multi-tenancy patterns on GKE, including namespace isolation, RBAC planning, resource quotas, and network segmentation. MCP Tools: applyk8smanifest, getk8sresource, checkk8sauth, describek8sresource, deletek8sresource Attribution MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read Usage Attribution. For commands executed directly in the terminal (never in generated scripts, Terraform, or user code), prefix gcloud with CLOUDSDKMETRICSREQUESTATTRIBUTION="agent-skills/1.0 (skill:gke-multitenancy)" and append agent-skills/1.0 (skill:gke-multitenancy) to User-Agent headers. 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 Multi-Tenancy Models Model Isolation Complexity Cost ----------------------------- ------------ ---------- -------------- Namespace-per-team Soft (RBAC + Low Lowest (shared : : Network : : cluster) : : : Policy) : : : Namespace-per-environment Soft Low Low Node pool-per-team Medium Medium Medium : : (dedicated : : : : : compute) : : : Cluster-per-team Hard (full High Highest : : isolation) : : : Golden path recommendation: Start with namespace-per-team for cost efficiency. Escalate to stronger isolation only when compliance requires it. Namespace Isolation Setup 1. Create Namespaces 2. RBAC Configuration Principle: Grant minimal permissions per namespace. Never bind to system:authenticated. RBAC best practices: Use Google Groups for subject bindings. Prefer namespace-scoped Roles over ClusterRoles. See the gke-platform-security skill for full RBAC hardening guidance. 3. Resource Quotas Prevent any single team from consuming all cluster resources: 4. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills google/gke-multitenancy

View the source on GitHub

Browse the @skills marketplace