A ClusterRole defines Kubernetes RBAC permissions at cluster scope. Like a Role, it lists API groups, resources, and verbs; unlike a Role, it grants access across namespaces or to cluster-wide resources. section 12.6
A ClusterRole is useful when a subject must access resources outside one namespace:
- Specify permissions additively with API groups, resources, and verbs; omitted permissions are not granted. section 12.6
Allowing cluster-level deployment prerequisites
A developer successfully deploys within team1 but receives Forbidden when creating a PriorityClass because the required cluster-level permission is absent. A ClusterRole grants access to PriorityClasses and StorageClasses, plus get and list access to PersistentVolumes and namespaces; a ClusterRoleBinding assigns it to the developer.


