Google Workspaces SSO for Kubernetes Rancher
You set up google workspaces sso for kubernetes rancher by linking your identity provider to your cluster manager. This link lets your team log in with their work email accounts. Most teams map broad directory groups straight to cluster roles during this setup. When roles are too broad, users get write permissions across every namespace. How google workspaces sso for kubernetes rancher works The login flow starts when an engineer opens the cluster dashboard. The manager sends the user to Goog
Your coding agents run with your access.
Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.
You set up google workspaces sso for kubernetes rancher by linking your identity provider to your cluster manager. This link lets your team log in with their work email accounts. Most teams map broad directory groups straight to cluster roles during this setup. When roles are too broad, users get write permissions across every namespace.
How google workspaces sso for kubernetes rancher works
The login flow starts when an engineer opens the cluster dashboard. The manager sends the user to Google to check their work email and password. Google checks the user and sends back their profile and group list. The cluster manager reads these groups and maps them to Kubernetes permissions.
Under the hood, Kubernetes uses roles to hold sets of permission rules. These rules are additive, which means there are no deny rules in the system. A standard role sets permissions inside one single namespace for a specific team. A cluster role covers the whole cluster, including nodes and all namespaces.
Role bindings connect your Google directory groups to these specific permission sets. A role binding grants permissions inside one namespace to a mapped Google group. A cluster role binding gives that Google group access across the entire cluster. When a user logs in, the API server checks their group bindings before running requests.
How subresources and role bindings shape cluster access
Kubernetes permissions also control subresources like pod logs and container shell commands. In the role rules, the API writes these subresources with a slash. For example, reading logs uses the pods slash log subresource rule. Running a shell inside a container uses the pods slash exec subresource rule.
Many teams grant pod shell rules to whole developer groups during SSO setup. They do this so engineers can debug broken apps in production namespaces. Still, Kubernetes role rules cannot restrict create actions on subresources by specific resource names. Once a role allows container shell access, the user can enter any pod in that namespace.
This creates a common problem when teams map large Google groups to shared namespaces. Every person in the group gets the exact same additive permissions in that space. You must create many small roles and bindings if you want tighter rules. Keeping dozens of Google groups in sync with namespace roles takes constant manual work.
Kubernetes RBAC + Rancher Access Control: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
What native SSO solves and what it leaves open
Linking Google Workspaces to your cluster manager solves the initial login problem well. You no longer need to create static client certificates for every new engineer. When someone leaves the company, you disable their Google account in one place. That single action blocks their login to the cluster manager right away.
Still, SSO and Kubernetes role bindings only decide who can enter the cluster. They do not inspect what individual commands or queries do after login succeeds. Once a user opens a container shell, native RBAC stops checking their actions. The API server knows a shell started, but it does not read the shell commands.
The same gap appears when engineers read pod logs or app secrets. A user with log access can pull sensitive data printed to standard output. Native SSO cannot rewrite sensitive fields like emails, phone numbers, card numbers, or national IDs in flight. It also cannot ask a manager to approve a single risky command before it runs.
Check Kubernetes API requests and responses on the wire
Kubernetes RBAC decides who may call the API server. RBAC does not check response payloads or split listing Secret names from reading Secret values when a role grants get access. With hoop.dev, you run an open-source proxy, a sidecar for your Kubernetes API, inline on the API connection. On every kubectl or API call an AI agent or engineer runs against production, hoop.dev decides to pass, mask, block, or hold it for human review.
On each call, hoop.dev guardrails read the method, normalized path, and headers to refuse bad deletes or full Secret reads with a 403 error, or hold risky calls for approval. On the way back, hoop.dev data masking walks JSON responses by key and masks matched values in Secrets, ConfigMaps, and pod logs in memory. View the project on GitHub.
Frequently asked questions
Does Google SSO remove the need for Kubernetes RBAC?
No, Google SSO only checks who the user is during login. Kubernetes RBAC still controls what resources that user can read or change.
Can Kubernetes RBAC block a single command inside a pod shell?
No, RBAC only checks if the user can open the pod shell subresource. Once the shell opens, Kubernetes does not check the commands typed inside it.
How do deny rules work when mapping Google groups to roles?
Kubernetes RBAC does not have deny rules because all permissions are additive. To remove access, you must remove the user from the group or role binding.
Related guides
In this post