Which RBAC object binds a role to a user or service account within a namespace?

Which RBAC object binds a role to a user or service account within a namespace?

• A. ClusterRole
• B. RoleBinding
• C. Role
• D. ClusterRoleBinding

Answer: (B)

In Kubernetes RBAC, permissions are defined in Roles and ClusterRoles, and who gets those permissions is granted through bindings. A RoleBinding ties a Role (or a ClusterRole) to one or more subjects—such as a user or a service account—within a specific namespace. This means the subject receives the permissions described by the Role, but only inside that namespace. A Role by itself is just a set of permissions and doesn’t grant access by itself, while a ClusterRole is a permissions set that applies cluster-wide. A ClusterRoleBinding would grant those permissions across all namespaces (cluster-wide), not scoped to a single namespace. Thus, the binding that connects a role to a user or service account within a namespace is a RoleBinding.

In Kubernetes RBAC, permissions are defined in Roles and ClusterRoles, and who gets those permissions is granted through bindings. A RoleBinding ties a Role (or a ClusterRole) to one or more subjects—such as a user or a service account—within a specific namespace. This means the subject receives the permissions described by the Role, but only inside that namespace. A Role by itself is just a set of permissions and doesn’t grant access by itself, while a ClusterRole is a permissions set that applies cluster-wide. A ClusterRoleBinding would grant those permissions across all namespaces (cluster-wide), not scoped to a single namespace. Thus, the binding that connects a role to a user or service account within a namespace is a RoleBinding.