liveBook · Manning

Cluster role binding

As explained in Kubernetes for Developers

A Kubernetes ClusterRoleBinding assigns a ClusterRole to subjects at cluster scope.

A ClusterRoleBinding assigns a ClusterRole to subjects and grants its permissions at cluster scope. It handles access that extends beyond one namespace. section 12.6

Use the binding to connect an identity with a reusable cluster-wide permission set:

  • Grant only the required resources and verbs; permissions are additive. section 12.6

Extending a namespace developer role

A developer can deploy within team1 through a RoleBinding but cannot create a cluster-scoped PriorityClass. A ClusterRole granting access to priorityclasses, storageclasses, and read-only namespaces or persistent volumes supplies those additional permissions.

How Kubernetes for Developers covers it

How deep it goes
Defines role references and subjects through YAML, but stops short of explaining authorization evaluation internals.
Examples
Uses developer access, team1, PriorityClass, StorageClass, PersistentVolume, and namespace permissions as concrete examples.
What it assumes
Assumes familiarity with Kubernetes identities, namespaces, resources, verbs, and basic YAML object definitions.
What you can do after
Configure cluster-wide permissions for a user by binding a ClusterRole with kubectl-applied YAML.
How it connects
Connects ClusterRole, RoleBinding, Role, subjects, namespaces, resources, verbs, and RBAC.

Also explained in

Compare how 4 books explain cluster role binding →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Kubernetes for Developers. The section links point to the parts of the book it draws on.