liveBook · Manning

Group

A group is a named collection of identities or resources managed together for shared permissions, access policies, or administrative properties.

How 2 Manning books explain it

Authorization in Action

A group is a named collection of principals or resources to which shared access rules can be applied.

How it is used
Applies shared access rules to collections of principals or resources, avoiding repeated individual policy entries.
How deep it goes
Defines groups, contrasts them with roles, and examines ACL and scaling limitations without prescribing a membership-management workflow.
Examples
Uses CustCo document viewers, a Marketing ACL, and health-record departments, shifts, roles, and patient consent.
What you can do after
Evaluate/understand when group membership can express shared access and when roles or contextual policies are needed.

Read how Authorization in Action explains group →

Acing the Certified Kubernetes Administrator Exam, Second Edition

A collection of Kubernetes user identities represented in authentication credentials for authorization decisions.

How it is used
Supports RBAC authorization by applying permissions to multiple certificate-authenticated identities through a shared subject.
How deep it goes
Explains certificate encoding, CertificateSigningRequest fields, bindings, kubeconfig contexts, and permitted versus forbidden operations.
Examples
Uses Carol, the developers group, a pod-reader binding, CertificateSigningRequest YAML, kubeconfig contexts, and pod access checks.
What you can do after
Apply group-based RBAC with kubectl, construct certificate credentials, switch contexts, and verify effective permissions.

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

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.