API group
A named family of related Kubernetes object types, such as apps for Deployments or batch for Jobs, that is versioned on its own.
In more detail
The core group has no name, which is why a Pod says apiVersion v1 and an RBAC rule for pods lists an empty string as its group. Other groups appear in apiVersion before the slash, such as apps/v1 or rbac.authorization.k8s.io/v1. A CRD adds a brand new group of your own.
Example
apiGroups: [""] # the core group, where pods liveRelated terms
- apiVersion — The manifest field that names which API group and version defines an object, such as v1 or apps/v1.
- role-based access control — An authorization model where permissions are grouped into named roles, such as reader or editor, and people or services are given roles.
- CRD — A CustomResourceDefinition: an object that teaches the API server a new kind, with its own name, group, scope and schema.
- Role — A namespaced RBAC object listing which verbs are allowed on which resources inside one namespace.
Taught in
- API Deprecations And Migrations — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Authentication, Authorisation And Admission — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Custom Resources And Operators — Certified Kubernetes Application Developer (CKAD) Exam Prep
- From Docker To Desired State — Kubernetes: Production-Grade Container Orchestration
- Control Plane: etcd, API Server, Scheduler, Controllers — Kubernetes: Production-Grade Container Orchestration
- RBAC: Roles, Bindings And Least Privilege — Kubernetes: Production-Grade Container Orchestration
- Least Privilege In IAM And RBAC — Application Security & Threat Modeling for Engineers