Kubernetes RoleBinding is a Role-Based Access Control, or RBAC, object in Kubernetes that grants permissions within a single namespace by connecting a Role or ClusterRole to subjects such as users, groups, or service accounts. It answers who can do what in a namespace, such as allowing a service account to read ConfigMaps, letting a developer view Pods, or giving a CI/CD pipeline permission to update Deployments. A RoleBinding does not define permissions itself; the referenced Role or ClusterRole defines allowed actions like get, list, create, or delete on resources such as Pods, Secrets, Services, or Jobs. Use a RoleBinding when access should stay limited to one namespace, and use a ClusterRoleBinding when the same permissions should apply across the whole cluster. In practice, RoleBindings help teams apply least-privilege access, separate responsibilities by namespace, and manage safer platform workflows in environments such as Azure Kubernetes Service or other managed Kubernetes platforms.
DevOps Glossary
Kubernetes RoleBinding
Kubernetes RoleBinding assigns a Role’s namespace permissions to users, groups, or service accounts for RBAC control.