Sailpoint SSO for Kubernetes AKS
You set up sailpoint sso for kubernetes aks by linking your identity provider to Azure AD. Then you map your directory groups to native cluster roles for your team. Engineering teams use this setup to manage who can log in to a cluster. Admins assign users to groups based on their job titles or team names. When a user joins a project, the identity tool grants them a group role. That group maps to a cluster role inside the Kubernetes API server. Still, teams often grant broad permissions so deve
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 sailpoint sso for kubernetes aks by linking your identity provider to Azure AD. Then you map your directory groups to native cluster roles for your team.
Engineering teams use this setup to manage who can log in to a cluster. Admins assign users to groups based on their job titles or team names. When a user joins a project, the identity tool grants them a group role. That group maps to a cluster role inside the Kubernetes API server. Still, teams often grant broad permissions so developers can fix broken apps fast. When roles are too broad, a single login gives a user full control. They can read secrets, change live apps, or run shell commands across namespaces.
How sailpoint sso for kubernetes aks works with native roles
Identity governance tools do not talk to the Kubernetes API server directly. Instead, they manage users and group memberships inside your main cloud directory. When a developer needs cluster permissions, they request a role in the governance portal. Once approved, the tool adds the user to a cloud directory group. Azure Kubernetes Service reads that group membership when the user logs in.
Inside the cluster, native role-based access control takes over to check permissions. Kubernetes uses Role and ClusterRole objects to hold sets of permission rules. In Kubernetes, permissions are purely additive, meaning there are no deny rules. A Role sets permissions within one single namespace for your team. A ClusterRole is not namespaced and can cover resources across all namespaces. It can also cover cluster-scoped resources like nodes or non-resource endpoints.
To link directory groups to these rules, you create binding objects. A RoleBinding grants permissions inside one namespace to a user or directory group. It can point to a Role in that namespace or a shared ClusterRole. A ClusterRoleBinding grants permissions across the entire cluster at once. When a user runs a command, the API server checks their group bindings. If a matching rule exists, the server allows the request to run.
What native identity setup solves and what it misses
Linking your identity tool to cluster roles solves the user lifecycle problem. When an employee leaves the company, the system removes their group access right away. You also get a clear record of who approved a role request. Auditors can check which users belong to admin groups at any time. This stops teams from sharing static admin keys or local user files.
SailPoint + Kubernetes RBAC: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Still, this setup only decides who can log in to the cluster. It does not control what individual commands or requests do during a session. Kubernetes checks permissions at the API resource level, including subresources like pod logs. A rule for the pod exec subresource lets a user open a shell. Once that shell opens, native roles cannot inspect the commands the user types.
A developer with pod exec permissions can run any command inside that container. They might read local files, inspect memory, or pull data from connected databases. If pod logs hold emails, phone numbers, or card numbers, the user sees them. Native role bindings cannot rewrite matched fields in results to hide sensitive data. Also, group approvals happen days or weeks before an engineer runs a command. Approving a broad role today gives a user standing permissions they rarely need. To stay safe, teams need a way to check single commands in flight. They also need to mask sensitive data before it reaches the user screen.
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 HTTP proxy, a sidecar for your Kubernetes API. The kubectl client changes only the server address it talks to while RBAC stays in place.
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. On the way back, hoop.dev data masking walks JSON responses by key and masks matched values in Secrets, ConfigMaps, and pod logs. Every request and verdict is logged without storing bearer tokens. View the project on GitHub.
Frequently asked questions
Can I write a deny rule in Kubernetes RBAC to block specific commands?
No, Kubernetes role permissions are purely additive and do not support deny rules. You must grant only the exact resource verbs a user needs to work.
How does a RoleBinding differ from a ClusterRoleBinding in AKS?
A RoleBinding grants permissions inside one specific namespace to a user or group. A ClusterRoleBinding grants permissions across all namespaces and cluster-wide nodes at once.
Does SailPoint log the shell commands a developer runs inside a pod?
No, identity governance tools only track group memberships and role approval history. They do not see or log commands run inside a container shell session.
Related guides
In this post