liveBook · Manning

Cluster role binding

As explained in Effective Platform Engineering

A cluster role binding is a Kubernetes authorization resource that grants the permissions of a cluster role to specified subjects across the cluster.

A ClusterRoleBinding is a Kubernetes authorization resource that grants a ClusterRole’s permissions to specified subjects across the cluster. A typical platform setup binds the cluster-admin role to a GitHub-backed platform engineering group, giving its members administrative kubectl access. section 7.4.5

Platform-team administrator binding

Store the resource as tpl/admin-clusterrolebinding.yaml, bind the platform team group to cluster-admin, and apply it during base configuration.

How Effective Platform Engineering covers it

How deep it goes
Defines and deploys one administrative binding, but does not detail RBAC evaluation or permission design.
Examples
Uses an administrator YAML manifest that binds epetech/platform-team to cluster-admin.
What it assumes
Assumes Kubernetes authentication, authorization, GitHub team membership, and ClusterRole concepts.
What you can do after
Operate cluster administration through kubectl after applying a declarative group binding.
How it connects
Connects Kubernetes RBAC, ClusterRole, group-based identity, OIDC, GitHub teams, and kubectl.

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 Effective Platform Engineering. The section links point to the parts of the book it draws on.