Cluster roles and Cluster Role Bindings are two of the core components of Kubernetes authorization. They define which users and service accounts can access Kubernetes resources, and which operations they can perform on those resources.
A Cluster Role is an abstract way to describe a set of permissions within a cluster. For example, a Cluster Role might define that a user can create, get, and list deployments. A Cluster Role is namespaced, meaning that each cluster can have its own custom set of Cluster Roles.
A Cluster Role Binding applies a Cluster Role to a user or service account, granting that user or service account the permissions described by the Cluster Role. This lets you easily grant a certain set of permissions to a user or service account without having to manually specify each permission.
In short, Cluster Roles define what permissions a user or service account has, and Cluster Role Bindings apply those permissions to a user or service account. Using these two components together makes it easy to manage the permissions of users and service accounts across your cluster.
Pingback: What is the difference between RoleBinding and ClusterRoleBinding in Kubernetes? - MtroView
Pingback: What is Role and RoleBinding in Kubernetes? - MtroView
Pingback: What is service account in Kubernetes? - MtroView