general availability
The stage at which a Kubernetes API or feature is declared stable, served under a plain version such as v1.
In more detail
Kubernetes APIs move from alpha to beta to general availability. A stable version keeps its fields and is not removed within a major release, while beta versions are deprecated and later removed. Manifests written against a beta API must be migrated to the stable version before the cluster stops serving the old one.
Example
batch/v1beta1 CronJob became generally available as batch/v1 in Kubernetes 1.21.Related terms
- apiVersion — The manifest field that names which API group and version defines an object, such as v1 or apps/v1.
- 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.
Taught in
- API Deprecations And Migrations — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Who Decides What Ships: The CNCF And Its Community — Kubernetes and Cloud Native Associate (KCNA) Exam Prep