Study. uk . com
  1. Home
  2. All questions
  3. Question 976

CKA study material · question 976 of 1000

Why does kubectl create clusterrolebinding accept only --clusterrole and not --role?

  1. Because a namespaced Role cannot be granted cluster-wide
  2. Because Roles may only be bound by their own namespace's administrator
  3. Because Roles are deprecated in favour of ClusterRoles
  4. Because a ClusterRoleBinding may name only one subject
Show the answer

Answer: A. Because a namespaced Role cannot be granted cluster-wide

A Role's permissions are scoped to its namespace, so there is nothing coherent for a cluster-wide binding to grant; only a ClusterRole can be bound that way.

Source: kubectl create clusterrolebinding (Kubernetes) — Synopsis

Challenge yourself on this topic → Study as cards