GKE versioning and support | Google Kubernetes Engine (GKE) | Google Cloud Documentation
Skip to main content Console English Deutsch Español Español – América Latina Français Indonesia Italiano Português Português – Brasil עברית 中文 – 简体 中文 – 繁體 日本語 한국어 Sign in Google Kubernetes Engine (GKE) Start free Home Documentation Application hosting Google Kubernetes Engine (GKE) Resources GKE versioning and support Stay organized with collections Save and categorize content based on your preferences.
This page explains versioning in Google Kubernetes Engine (GKE), and the policies for version support. Over time, GKE upgrades clusters to newer versions of Kubernetes. To learn more about how upgrades work, see About GKE cluster upgrades . You can see the current versions rollout and support schedule in the GKE release schedule . Minor version support GKE support for Kubernetes minor versions is based on Kubernetes open source policies.
To support available minor versions during their lifecycle, GKE provides patch versions and regularly performs automatic cluster upgrades to apply those newer patches. For information about how GKE supports patch versions, see Patch version support . In addition to supporting available minor versions, GKE also provides alpha patch versions of the next minor version in the Kubernetes release cycle up to four months before that minor version becomes available to all clusters in the Rapid channel.
These alpha versions are available only to GKE alpha clusters in the Rapid channel and are intended for early adopters who want to experiment with upcoming features. How Kubernetes supports a minor version The Kubernetes Open Source Software (OSS) community releases a minor version with new features and enhancements three times a year . Each release cycle is approximately 15 weeks long. Kubernetes supports each minor version for 14 months.
Major bugs and security vulnerabilities found in a supported minor version are fixed with the release of an ad hoc patch version. The Kubernetes community sometimes revises their version support calendar, as necessary. To learn more, see Support period . How GKE supports a minor version Before the release of a stable new minor version, the Kubernetes project releases experimental, unstable patch versions of that minor version.
GKE introduces alpha patch versions that are based on these experimental versions in the Rapid channel to only GKE alpha clusters. Similarly to other patch versions in the Rapid channel, alpha versions are excluded from the GKE SLA . After Kubernetes releases the stable new minor version, GKE removes the alpha versions of that minor version and makes patch versions for that minor version available to any cluster that's in the Rapid channel.
Because the Rapid channel provides the newest GKE patch versions, these versions are excluded from the GKE SLA and might contain issues without known workarounds. After the initial availability in the Rapid channel, GKE promotes the new minor version to the Regular channel. GKE provides up to a total of 24 months of support for a minor version after the version has been made available for new cluster creation in the Regular channel.
This support includes around 14 months of standard support and approximately an additional 10 months of extended support available with the Extended channel. To see the availability of specific minor versions, review the GKE release schedule . GKE minor version lifecycle The lifecycle of a GKE minor version includes the following key steps: Up to four months before the release date for a minor version, GKE makes alpha patch versions for that minor version available in the Rapid channel to only alpha clusters.
Kubernetes releases the new minor version. GKE makes the new minor version available in the Rapid channel and removes any existing alpha patch versions for that minor version. GKE makes the new minor version available in the Regular channel (start of standard support period). During the standard support period, GKE provides patches for the minor version which include new features, security fixes, and bug fixes. The minor version reaches the end of standard support after approximately 14 months in total, entering the period of extended support.
After this time, GKE provides security patches for clusters in the Extended channel. The minor version reaches the end of extended support, meaning that the minor version will receive no further security patches. Adjustments of version availability GKE might revise the end of support for GKE versions, due to shifts in policy in the Kubernetes OSS community, the discovery of vulnerabilities, or other technical issues that cannot be reasonably resolved.
GKE might also extend end of support dates around key business periods such as Black Friday and Cyber Monday. GKE provides at least 14 months of standard support, and up to a total of 24 months of support with extended support. To get the latest available versions, see the GKE release notes . GKE regularly updates the release schedule to reflect the timing of auto-upgrades. Periods of availability in the minor version lifecycle GKE provides the following periods of availability for a Kubernetes minor version: See the following table summarizing the periods of availability, described in detail in the next sections: Period of availability Approximate timespan from Regular channel availability What support does GKE provide Access to this period of availability Alpha version availability period Month -5 through Month -1 GKE introduces new alpha patch versions in the Rapid channel until the start of the Rapid-only availability period.
The alpha patch versions are available only to alpha clusters, have no technical support or SLA, and are highly likely to contain issues. When the minor version becomes available to all clusters in the Rapid channel at the end of the alpha-only availability period, GKE removes all alpha versions from the Rapid channel. Rapid channel only (requires alpha clusters) Rapid-only availability period Month -1 through Month 0 GKE makes the minor version available to all clusters in the Rapid channel by providing patch versions with new features, security fixes, and bug fixes.
However, these versions are excluded from the GKE SLA and may contain issues without known workarounds. GKE also removes any available alpha versions for that minor version from the Rapid channel. Rapid Channel only Standard support period Month 1 through Month 14 GKE provides patch versions with new features, security fixes, and bug fixes. Rapid, Regular, Stable, Extended, No Channel ( deprecated ) Extended support period Month 15 through Month 24 GKE provides patch versions with security fixes.
Extended Channel only (requires additional fee per cluster, see Get long-term support with the Extended channel ) Period of alpha version availability GKE releases alpha patch versions of an upcoming minor version in the Rapid channel up to four months before the release of that minor version. The alpha versions are available only for alpha clusters. GKE releases additional alpha patch versions in the weeks that follow and typically maintains between one and three active alpha versions.
This period lasts until GKE releases the stable minor version in the Rapid channel. After the stable release, GKE removes all of the alpha patch versions for that minor version from the Rapid channel because stable patch versions are available to install. Period of Rapid-only availability GKE first releases a new minor version in the Rapid channel. The version first accumulates usage and demonstrates stability across clusters in this channel before being promoted to the Regular channel.
Only clusters enrolled in the Rapid channel can run a new minor version during this period of availability. This period typically lasts around 1-2 months, however the exact timing depends on each minor version. For details, see Estimated schedule for release channels . Period of standard support The period of standard
The rest of this page is on the live site.