Which statement accurately describes the difference between Roles and ClusterRoles in Kubernetes?

Which statement accurately describes the difference between Roles and ClusterRoles in Kubernetes?

• A. ClusterRoles are used to define permissions at the cluster level, while Roles are used to define permissions at the namespace level
• B. Roles are used to define cluster-wide permissions
• C. ClusterRoles define permissions for nodes only
• D. Roles can be bound to service accounts

Answer: (A)

Roles and ClusterRoles define who can do what to which resources in Kubernetes, and they differ mainly in scope. Roles are namespace-scoped, meaning they specify permissions that apply only within a single namespace. ClusterRoles, in contrast, describe permissions that exist at the cluster level and can apply across all namespaces. You can attach a ClusterRole to a subject in a specific namespace using a RoleBinding, or grant those same cluster-wide permissions across the entire cluster with a ClusterRoleBinding. This distinction is the essence: permissions confined to a namespace versus permissions that span the whole cluster.

Roles and ClusterRoles define who can do what to which resources in Kubernetes, and they differ mainly in scope. Roles are namespace-scoped, meaning they specify permissions that apply only within a single namespace. ClusterRoles, in contrast, describe permissions that exist at the cluster level and can apply across all namespaces. You can attach a ClusterRole to a subject in a specific namespace using a RoleBinding, or grant those same cluster-wide permissions across the entire cluster with a ClusterRoleBinding. This distinction is the essence: permissions confined to a namespace versus permissions that span the whole cluster.