RoleBindings and ClusterRoleBindings in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Difference between RoleBinding and ClusterRoleBinding

Which statement correctly describes the difference between a RoleBinding and a ClusterRoleBinding in Kubernetes?

A RoleBinding is deprecated; ClusterRoleBinding is the only supported binding type.

B RoleBinding grants permissions cluster-wide; ClusterRoleBinding grants permissions within a specific namespace.

C RoleBinding and ClusterRoleBinding both grant permissions only within a namespace but differ in API versions.

D RoleBinding grants permissions within a specific namespace; ClusterRoleBinding grants permissions cluster-wide.

💡 Hint

Think about the scope of permissions each binding type controls.

A RoleBinding assigns permissions to users or groups within a single namespace. A ClusterRoleBinding assigns permissions across the entire cluster, spanning all namespaces.

💻 Command Output

intermediate

kubectl command output for RoleBinding listing

What is the output of the command kubectl get rolebindings -n dev if there is one RoleBinding named read-pods in the dev namespace?

Kubernetes

kubectl get rolebindings -n dev

A

NAME        ROLE                 AGE
read-pods   Role/read-pods-role   10d

B

NAME        CLUSTERROLE          AGE
read-pods   ClusterRole/read-pods 10d

C No resources found in dev namespace.

D error: the server doesn't have a resource type "rolebindings"

💡 Hint

Consider the resource type and namespace specified in the command.

The command lists RoleBindings in the dev namespace. The output shows the RoleBinding name, the Role it references, and its age.

❓ Configuration

advanced

Correct ClusterRoleBinding YAML for cluster-wide admin access

Which YAML snippet correctly creates a ClusterRoleBinding named cluster-admin-binding that grants the cluster-admin ClusterRole to the user alice?

A

apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: cluster-admin-binding
subjects:
- kind: User
  name: alice
  apiGroup: rbac.authorization.k8s.io
roleRef:
  kind: ClusterRole
  name: cluster-admin
  apiGroup: rbac.authorization.k8s.io

B

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: cluster-admin-binding
subjects:
- kind: Group
  name: alice
  apiGroup: rbac.authorization.k8s.io
roleRef:
  kind: ClusterRole
  name: cluster-admin
  apiGroup: rbac.authorization.k8s.io

C

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: cluster-admin-binding
subjects:
- kind: User
  name: alice
  apiGroup: rbac.authorization.k8s.io
roleRef:
  kind: ClusterRole
  name: cluster-admin
  apiGroup: rbac.authorization.k8s.io

D

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: cluster-admin-binding
subjects:
- kind: User
  name: alice
roleRef:
  kind: Role
  name: cluster-admin
  apiGroup: rbac.authorization.k8s.io

💡 Hint

Check the kind of binding, subject kind, and roleRef kind carefully.

The binding must be ClusterRoleBinding to grant cluster-wide permissions. The subject kind must be User for a user named alice. The roleRef must reference a ClusterRole named cluster-admin.

❓ Troubleshoot

advanced

Error when creating RoleBinding with cluster-wide ClusterRole

You try to create a RoleBinding in namespace test that references the cluster-admin ClusterRole, but get an error. What is the most likely cause?

A The namespace <code>test</code> does not exist.

B RoleBindings cannot reference ClusterRoles; only ClusterRoleBindings can.

C The <code>cluster-admin</code> ClusterRole does not exist.

D RoleBinding subjects must be service accounts only.

💡 Hint

Think about the scope of RoleBindings and ClusterRoles.

RoleBindings can reference Roles or ClusterRoles, but when referencing a ClusterRole, the RoleBinding is limited to the namespace. However, some cluster-wide ClusterRoles like cluster-admin are intended to be bound cluster-wide using ClusterRoleBinding. Some Kubernetes versions or policies may restrict RoleBindings from referencing cluster-wide ClusterRoles.

🔀 Workflow

expert

Sequence to grant namespace admin rights to a user

Arrange the steps in the correct order to grant a user named bob admin rights in the production namespace using Kubernetes RBAC.

A 3,1,2,4

B 1,3,2,4

C 3,2,1,4

D 2,1,3,4

💡 Hint

Think about prerequisites before creating resources and verifying access last.

First, ensure the namespace exists. Then create the Role with admin permissions. Next, bind the Role to the user with a RoleBinding. Finally, test the user's access.