Pattern 1: Standalone Kubernetes Gateway

• Kubernetes Gateway per cluster

  Install a single gateway instance that serves all namespaces in the cluster—ideal for shared infrastructure and centralized traffic management.

• Multi gateways per cluster with cluster-scoped permissions

  Deploy one gateway instance in each namespace for stronger isolation, separate configuration, and per-team autonomy with a cluster scope permission

• Multi Gateways per cluster with Namespaced-scoped permission

  Deploy one gateway instance in each namespace for stronger isolation, separate configuration, and per-team autonomy with namespace scope permission

Important

Upon installation, the Kubernetes Gateway creates Roles and ClusterRoles to manage permissions. If you install it at the cluster level, the necessary RBAC resources are generated automatically. If you don’t have cluster-wide permissions in your production setup, choose the per-namespace installation option instead.