Find your next open-source project

Search by name, purpose, or keyword — or paste a GitHub repository URL
All skills

gke-multitenancy

Plan and configure GKE multi-tenancy with namespaces, RBAC, quotas, LimitRanges, and network isolation.

  • Part of google/skills
  • 7.8k installs
  • DevOps & Self-hosting · Containers and clusters

When to use it

You have one GKE cluster shared by several teams and need to split it into isolated namespaces with fair resource limits.

For example

You say

Use gke-multitenancy to set up namespace-per-team isolation for team-a and team-b on our shared GKE cluster, including RBAC, resource quotas, and default-deny network policies.

You get
  • Namespace and RBAC manifests
  • ResourceQuota and LimitRange YAML
  • NetworkPolicy manifests

How it works

  • Recommends starting with namespace-per-team isolation and escalating only when compliance requires it.
  • Warns that setting min or max in a LimitRange requires matching default and defaultRequest values, or pods without limits are rejected.