liveBook · Manning

Role

A Kubernetes Role is a namespace-scoped RBAC authorization resource that defines permitted actions on specified Kubernetes API resources.

How 2 Manning books explain it

Acing the Certified Kubernetes Administrator Exam, Second Edition

A role is a Kubernetes RBAC object that defines permitted actions on specified resources within a namespace.

How it is used
Controls permitted API actions on resources within a namespace when assigned through a RoleBinding.
How deep it goes
Works through Role creation, YAML inspection, binding, and permission checks; does not examine RBAC authorization internals.
Examples
Uses a pod-reader Role, a user RoleBinding, get-versus-delete permission checks, and a ServiceAccount pod-list Role.
What you can do after
Operate/configure it with kubectl to grant namespace-scoped permissions and verify allowed actions with `kubectl auth can-i`.

Read how Acing the Certified Kubernetes Administrator Exam, Second Edition explains role →

Google Anthos in Action

A Kubernetes Role is a namespace-scoped RBAC resource that defines permissions on resources.

How it is used
Controls namespace-scoped access to Kubernetes resources in a shared cluster.
How deep it goes
Defines Role scope and distinguishes permission sets from bindings, without providing a Role manifest or creation command.
Examples
Contrasts Role scope with ClusterRole and binding tables, then shows service-account access through ClusterRoleBindings for console login.
What you can do after
Evaluate/understand whether permissions should remain namespace-scoped or use cluster-level RBAC resources.

Read how Google Anthos in Action explains role →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.