k8s-rbac-troubleshooting
RBAC troubleshooting
Find out why Kubernetes refuses a request, and propose the smallest grant that fixes it. Read first, ask before changing. Run the investigation commands freely. Run a command under an "Ask first" line only after the user approves that exact command; if your credentials do not allow it, give it to the user to run. Never run a "Proposed fix"; hand it to the user.
Every request is made by a subject: a user, a group, or a ServiceAccount, which
authenticates as system:serviceaccount:<namespace>:<name>. RBAC allows a request only
when a binding gives the subject a role whose rules cover the verb, the API group,
the resource and the namespace. There are no deny rules: a 403 means that no binding
allowed it. A RoleBinding grants its role in its own namespace only; a
ClusterRoleBinding grants a ClusterRole everywhere, including cluster-scoped
resources such as nodes and namespaces.