
Replace namespace-wide admin with two namespaced Roles, bind them to a user, a group and a ServiceAccount, and prove with access reviews what is granted, what is refused and what a revoked binding takes away.
Read the full problemReplace a Role pasted into every namespace with one ClusterRole, bind it cluster-wide and again inside a single namespace, and prove where each grant reaches and where the cluster-scoped rule stops.
Read the full problemGive release automation its own ServiceAccounts, mint tokens for them, call the API as each account to prove where its binding stops, run a pod as one of them, and revoke an inherited account's access.
Read the full problemPut a namespace on least privilege in one release - Roles for the app team, one auditor ClusterRole bound cluster-wide and namespace-wide, ServiceAccount tokens for the automation, a revoked god-mode binding, and an access report re-derived from the cluster on every run.
Read the full problem