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

Taught in

References

Certification courses