This page provides an overview of Kubernetes alpha features, and explains how alpha clusters work in Google Kubernetes Engine. You can create an alpha cluster or learn more about cluster configuration choices.
Overview
You can experiment with Kubernetes alpha features by creating an alpha cluster. Alpha clusters are short-lived clusters that run stable Kubernetes releases with all Kubernetes APIs and features enabled. Alpha clusters are designed for advanced users and early adopters to experiment with workloads that take advantage of new features before those features are production-ready. You can use Alpha clusters just like normal GKE clusters.
Alpha clusters default to running the current default version of Kubernetes. You
can specify a different version
during cluster creation. To learn which Kubernetes versions are available, refer
to Versioning and Upgrades and
Release Notes, or run
gcloud container get-server-config.
Limitations
Alpha clusters have the following limitations:
- Not covered by the GKE SLA
- Cannot be upgraded
- Node auto-upgrade and auto-repair are disabled on alpha clusters
- Automatically deleted after 30 days
- Do not receive security updates
- Not supported with Windows Server node pools.
Difference between alpha clusters and alpha GKE versions
Alpha clusters do not necessarily run "alpha" versions of GKE. The term alpha cluster means that alpha APIs are enabled, both for Kubernetes and GKE, regardless of the version of Kubernetes the cluster runs. Periodically, Google offers customers the ability to test GKE versions that are not generally available, for testing and validation. These early-access versions can be run as alpha clusters or as clusters without the Kubernetes alpha APIs enabled.
Latest Kubernetes alpha features
Most Kubernetes releases contain new Alpha features that you can test in alpha clusters. For a full list of Kubernetes releases and the features they include, see the Kubernetes changelog.
About feature stages
New Kubernetes features are introduced in four stages: early development, alpha, beta, and stable.
To ensure stability and production quality, normal GKE clusters only enable features that are beta or higher. Alpha features are not enabled on normal clusters because they are not production-ready or upgradeable.
Since GKE automatically upgrades the Kubernetes control plane, enabling alpha features in production could jeopardize the reliability of the cluster if there are breaking changes in a new version.
To learn more about the stages of Kubernetes features, see Alpha, Beta, and Stable Versions in the Kubernetes documentation.
To learn more about determining which features are enabled for a given GKE control plane version, see Feature gates.