Using a single Development cluster and a single Production cluster (rather than a separate project and cluster pair per team) minimizes the number of clusters and their associated overhead, keeping costs low. Within each cluster, creating one Kubernetes namespace per team provides logical separation of each team's resources. Kubernetes RBAC (Role-Based Access Control) is the native mechanism for restricting access to specific namespaces — by binding Roles/RoleBindings scoped to a namespace to each team's users or groups, you ensure a team can only view or modify resources in its own namespace, satisfying the isolation requirement without the cost of provisioning additional clusters or projects. Identity-Aware Proxy, by contrast, is intended for controlling access to HTTP(S) applications behind a load balancer and is not the appropriate control for restricting access to Kubernetes namespaces/API objects.
Community Discussion