API versioning
Kubernetes grows continuously. Its features change and this results in the API changing as well. To deal with those changes and to not break compatibility with existing clients over an extended period of time, Kubernetes supports multiple API versions, each with a different API path, such as /api/v1
or /apis/extensions/v1beta1
. There are three API levels in the Kubernetes API specification: alpha, beta, and stable. Let's get to know the difference.
Alpha
The alpha version level is disabled by default, as with the other software, an alpha version should be considered as buggy and not production ready. Also, you should note that any featured introduced in the alpha version might not always be available later, in the stable version. Also, the changes in the API may be incompatible in the next release. You should not use the alpha
version, unless you are very eager to test new features or do some experiments.
Beta
The beta level totally different from the alpha
level of the API, code...