What does a ClusterRole in Kubernetes define?

What does a ClusterRole in Kubernetes define?

• A. A list of namespaces
• B. A set of API versions
• C. A mapping of services
• D. Permissions on resources across cluster resources

Answer: (D)

A ClusterRole defines the permissions to act on Kubernetes resources. It contains rules that specify the API group, the resources, and the verbs (like get, list, watch, create, update, delete) that are allowed, effectively describing what actions are permitted across the cluster. This makes it possible to grant those permissions cluster-wide (via a ClusterRoleBinding) or scoped to a namespace when used with a RoleBinding. The other ideas—listing namespaces, defining API versions, or mapping services—do not capture what a ClusterRole is about; it’s fundamentally about what actions are allowed on which resources.

A ClusterRole defines the permissions to act on Kubernetes resources. It contains rules that specify the API group, the resources, and the verbs (like get, list, watch, create, update, delete) that are allowed, effectively describing what actions are permitted across the cluster. This makes it possible to grant those permissions cluster-wide (via a ClusterRoleBinding) or scoped to a namespace when used with a RoleBinding. The other ideas—listing namespaces, defining API versions, or mapping services—do not capture what a ClusterRole is about; it’s fundamentally about what actions are allowed on which resources.