RoleBindings and ClusterRoleBindings in Kubernetes - Commands & Configuration

Introduction

In Kubernetes, you often need to control who can do what inside your cluster. RoleBindings and ClusterRoleBindings connect users or groups to permissions, letting you manage access safely and clearly.

When you want to give a user permission to manage resources only in one specific namespace.

When you need to allow a service account to read pods across all namespaces.

When you want to restrict a developer to only view resources without changing them.

When you want to grant cluster-wide admin rights to a trusted user.

When you want to assign permissions to a group of users instead of one person.

Config File - rolebinding.yaml

rolebinding.yaml

apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: read-pods-binding
  namespace: example-namespace
subjects:
- kind: User
  name: alice
  apiGroup: rbac.authorization.k8s.io
roleRef:
  kind: Role
  name: pod-reader
  apiGroup: rbac.authorization.k8s.io
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: cluster-admin-binding
subjects:
- kind: User
  name: bob
  apiGroup: rbac.authorization.k8s.io
roleRef:
  kind: ClusterRole
  name: cluster-admin
  apiGroup: rbac.authorization.k8s.io

This file defines two bindings:

• RoleBinding named read-pods-binding in the example-namespace namespace. It gives user alice the permissions defined in the pod-reader Role, which is limited to that namespace.
• ClusterRoleBinding named cluster-admin-binding that gives user bob the cluster-admin ClusterRole, which applies cluster-wide.

Commands

This command creates the RoleBinding and ClusterRoleBinding in the cluster, assigning the specified permissions to users alice and bob.

Terminal

kubectl apply -f rolebinding.yaml

Expected Output

rolebinding.rbac.authorization.k8s.io/read-pods-binding created

clusterrolebinding.rbac.authorization.k8s.io/cluster-admin-binding created

This command checks the details of the RoleBinding named read-pods-binding in the example-namespace to confirm it was created correctly.

Terminal

kubectl get rolebinding read-pods-binding -n example-namespace -o yaml

Expected Output

apiVersion: rbac.authorization.k8s.io/v1

kind: RoleBinding

metadata:

  name: read-pods-binding

  namespace: example-namespace

roleRef:

  apiGroup: rbac.authorization.k8s.io

  kind: Role

  name: pod-reader

subjects:

- apiGroup: rbac.authorization.k8s.io

  kind: User

  name: alice

→

-n - Specifies the namespace to look in

→

-o yaml - Outputs the full resource details in YAML format

This command shows the details of the ClusterRoleBinding named cluster-admin-binding to verify it grants cluster-wide admin rights to bob.

Terminal

kubectl get clusterrolebinding cluster-admin-binding -o yaml

Expected Output

apiVersion: rbac.authorization.k8s.io/v1

kind: ClusterRoleBinding

metadata:

  name: cluster-admin-binding

roleRef:

  apiGroup: rbac.authorization.k8s.io

  kind: ClusterRole

  name: cluster-admin

subjects:

- apiGroup: rbac.authorization.k8s.io

  kind: User

  name: bob

→

-o yaml - Outputs the full resource details in YAML format

Key Concept

RoleBindings grant permissions within a namespace, while ClusterRoleBindings grant permissions across the whole cluster.

Common Mistakes

Creating a RoleBinding but expecting it to grant cluster-wide permissions.

RoleBindings only apply to a single namespace, so permissions won't work outside that namespace.

Use a ClusterRoleBinding to grant cluster-wide permissions.

Not specifying the correct namespace when creating or checking a RoleBinding.

RoleBindings are namespace-scoped, so commands without the right namespace won't find them.

Always use the -n flag with the correct namespace for RoleBindings.

Using a User kind in subjects without the user existing in the cluster's authentication system.

Kubernetes RBAC checks users based on authentication; if the user is unknown, permissions won't apply.

Ensure the user is recognized by your cluster's authentication method or use service accounts.

Summary

RoleBindings connect users or groups to Roles within a specific namespace.

ClusterRoleBindings connect users or groups to ClusterRoles across the entire cluster.

Use kubectl apply to create bindings and kubectl get to verify them.

Practice

1. What is the main difference between a RoleBinding and a ClusterRoleBinding in Kubernetes?

easy

A. RoleBinding and ClusterRoleBinding are exactly the same.

B. RoleBinding grants permissions cluster-wide, while ClusterRoleBinding grants permissions within a single namespace.

C. RoleBinding is used only for system users, ClusterRoleBinding is for regular users.

D. RoleBinding grants permissions within a single namespace, while ClusterRoleBinding grants permissions cluster-wide.

Solution

1. Step 1: Understand RoleBinding scope

   RoleBinding assigns permissions only inside one namespace.

2. Step 2: Understand ClusterRoleBinding scope

   ClusterRoleBinding assigns permissions across the entire cluster, not limited to a namespace.

3. Final Answer:

   RoleBinding is namespace-scoped; ClusterRoleBinding is cluster-scoped. -> Option D

4. Quick Check:

   Scope difference = RoleBinding grants permissions within a single namespace, while ClusterRoleBinding grants permissions cluster-wide. [OK]

Hint: Remember: RoleBinding = namespace, ClusterRoleBinding = whole cluster [OK]

Common Mistakes:

• Confusing the scope of RoleBinding and ClusterRoleBinding
• Thinking both bindings work cluster-wide
• Assuming RoleBinding is for system users only

2. Which of the following is the correct syntax to create a RoleBinding in Kubernetes YAML?

easy

A. apiVersion: v1
kind: RoleBinding
metadata:
name: read-pods
subjects:
- kind: User
name: jane
roleRef:
kind: Role
name: pod-reader

B. apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: read-pods
subjects:
- kind: User
name: jane
apiGroup: rbac.authorization.k8s.io
roleRef:
kind: Role
name: pod-reader
apiGroup: rbac.authorization.k8s.io

C. apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: read-pods
subjects:
- kind: User
name: jane
roleRef:
kind: Role
name: pod-reader
apiGroup: rbac.authorization.k8s.io

D. apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: read-pods
subjects:
- kind: User
name: jane
roleRef:
kind: ClusterRole
name: pod-reader
apiGroup: rbac.authorization.k8s.io

Solution

1. Step 1: Check apiVersion and kind

   Correct apiVersion for RoleBinding is rbac.authorization.k8s.io/v1 and kind is RoleBinding.

2. Step 2: Validate subjects and roleRef fields

   Subjects must include kind, name, and apiGroup. roleRef must reference a Role with correct apiGroup.

3. Final Answer:

   apiVersion: rbac.authorization.k8s.io/v1, kind: RoleBinding, with complete subjects including apiGroup, and roleRef to Role. -> Option B

4. Quick Check:

   Correct apiVersion and fields = apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: name: read-pods subjects: - kind: User name: jane apiGroup: rbac.authorization.k8s.io roleRef: kind: Role name: pod-reader apiGroup: rbac.authorization.k8s.io [OK]

Hint: RoleBinding YAML needs apiVersion rbac.authorization.k8s.io/v1 and kind RoleBinding [OK]

Common Mistakes:

• Using wrong apiVersion or kind
• Omitting apiGroup in subjects or roleRef
• Confusing RoleBinding with ClusterRoleBinding syntax

3. Given this YAML snippet for a ClusterRoleBinding:

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

What permission scope does user alice get?

medium

A. Permissions cluster-wide with cluster-admin rights

B. No permissions because ClusterRoleBinding requires a ServiceAccount subject

C. Permissions only in the default namespace

D. Permissions only in the namespace where the ClusterRoleBinding is created

Solution

1. Step 1: Identify the binding type and role

   The YAML defines a ClusterRoleBinding that binds user alice to the cluster-admin ClusterRole.

2. Step 2: Understand ClusterRoleBinding scope

   ClusterRoleBinding grants permissions cluster-wide, so alice has admin rights across all namespaces.

3. Final Answer:

   User alice has cluster-wide admin permissions. -> Option A

4. Quick Check:

   ClusterRoleBinding + cluster-admin = cluster-wide admin [OK]

Hint: ClusterRoleBinding with cluster-admin role = full cluster access [OK]

Common Mistakes:

• Assuming permissions are limited to one namespace
• Thinking only ServiceAccounts can be subjects
• Confusing ClusterRoleBinding with RoleBinding scope

4. You applied this YAML to create a RoleBinding:

apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: read-pods
subjects:
- kind: User
  name: bob
roleRef:
  kind: Role
  name: pod-reader
  apiGroup: rbac.authorization.k8s.io

But bob cannot list pods in the namespace. What is the likely problem?

medium

A. The subjects field is missing apiGroup for the user.

B. The roleRef kind should be ClusterRole instead of Role.

C. The RoleBinding must be created in the kube-system namespace.

D. The user bob does not exist in Kubernetes.

Solution

1. Step 1: Check subjects field completeness

   The subjects entry for user bob lacks the required apiGroup field, which is needed to identify the user correctly.

2. Step 2: Understand impact of missing apiGroup

   Without apiGroup, Kubernetes cannot match the user to the RoleBinding, so permissions are not granted.

3. Final Answer:

   Missing apiGroup in subjects causes permission failure. -> Option A

4. Quick Check:

   Subjects need apiGroup for user binding [OK]

Hint: Always include apiGroup in subjects for users [OK]

Common Mistakes:

• Omitting apiGroup in subjects
• Confusing Role and ClusterRole in roleRef
• Assuming namespace or user existence is the problem

5. You want to grant a service account named deploy-bot in namespace dev permission to create pods across all namespaces. Which is the correct approach?

hard

A. Create a RoleBinding in each namespace binding deploy-bot to a Role with pod creation rights.

B. Create a RoleBinding in the dev namespace binding deploy-bot to a Role with pod creation rights.

C. Create a ClusterRoleBinding binding the deploy-bot service account to a ClusterRole with pod creation rights.

D. Create a ClusterRole with pod creation rights but no binding is needed.

Solution

1. Step 1: Identify scope needed

   Permission to create pods across all namespaces requires cluster-wide scope.

2. Step 2: Choose correct binding type

   A ClusterRoleBinding is needed to bind the deploy-bot service account to a ClusterRole with pod creation rights cluster-wide.

3. Final Answer:

   Create a ClusterRoleBinding for deploy-bot to a ClusterRole with pod creation rights. -> Option C

4. Quick Check:

   ClusterRoleBinding = cluster-wide permissions [OK]

Hint: ClusterRoleBinding for cluster-wide access to service accounts [OK]

Common Mistakes:

• Using RoleBinding for cluster-wide permissions
• Not creating any binding after ClusterRole
• Creating RoleBinding in only one namespace