[Solved] A ClusterRoleBinding is created but users still lack permissions. What could be wrong? — Ans: The ClusterRoleBinding references a Role instead of a ClusterRole | Kubernetes

Kubernetes - RBAC and Security

A ClusterRoleBinding is created but users still lack permissions. What could be wrong?

AThe ClusterRoleBinding is applied in the wrong namespace

BThe ClusterRoleBinding references a Role instead of a ClusterRole

CThe ClusterRoleBinding is missing the apiVersion field

DThe ClusterRoleBinding's subject kind is incorrectly set to 'Group' instead of 'User'

Step-by-Step Solution

Solution:

Step 1: Understand ClusterRoleBinding requirements
ClusterRoleBinding must reference a ClusterRole, not a Role, because Roles are namespace-scoped.
Step 2: Check other options
Subject kind 'Group' is valid; ClusterRoleBindings are cluster-scoped and do not use namespaces; missing apiVersion causes YAML errors.
Final Answer:
The ClusterRoleBinding references a Role instead of a ClusterRole -> Option B
Quick Check:
ClusterRoleBinding must reference ClusterRole [OK]

Quick Trick: ClusterRoleBinding links only to ClusterRole, not Role [OK]

Common Mistakes:

Master "RBAC and Security" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

More Kubernetes Quizzes

A ClusterRoleBinding is created but users still lack permissions. What could be wrong?