Skip to content
Managed Kubernetes

Google Kubernetes Engine (GKE) Releases

Track GKE Kubernetes version support, release channel comparison (Rapid/Regular/Stable), auto-upgrade behavior, and feature compatibility across versions.

Total Versions

Supported

Latest

Version Timeline

All tracked releases with lifecycle status and EOL dates.

Loading version data…

Lifecycle Timeline

Visual overview of active support and maintenance windows.

1.27
1.28
1.29
1.30
1.31
1.32
2023 2024 2025 2026 2027 2028
Active
Maint
Active
Maint
Active
Maint
Active
Maint
Active
Maint
Active
Maint
Active / LTS
Maintenance
Today

Upgrade Paths

Migration guidance between major versions — breaking changes, effort estimates, and tips.

1.27/1.28 1.31+ Low-Medium Difficulty
Est. 30-60 minutes per version (auto-upgrade: hands-off)

Breaking Changes

  • Must upgrade one version at a time
  • Deprecated APIs removed at each K8s version
  • GKE-specific add-on compatibility
  • Workload Identity Federation changes
  • Container-Optimized OS updates

Migration Notes

GKE makes upgrades easier than EKS/AKS. If on a release channel, auto-upgrade handles it. For manual upgrades: use the GKE console or gcloud container clusters upgrade. GKE performs pre-upgrade checks and warns about deprecated APIs. Surge upgrades ensure zero downtime for node pools.

Version Risk Assessment

Evaluate risk factors before choosing a version for production.

Version EOL Risk CVE Risk Ecosystem Cloud Support Overall Recommended Action
Google Kubernetes Engine (GKE) 1.27 and older Critical High Extended Paid only Critical Past standard support — upgrade or pay for extended
Google Kubernetes Engine (GKE) 1.28 High Medium Maintenance Full High Nearing end of standard support
Google Kubernetes Engine (GKE) 1.29/1.30 Low Low Active Full Low Supported — on track
Google Kubernetes Engine (GKE) 1.31/1.32 None Low Active Full Low Current — recommended

GKE supports 4-5 K8s versions with standard support plus extended support. Auto-upgrade on release channels reduces risk significantly. Assessed March 2026.

GKE Kubernetes Version Feature Comparison

Side-by-side feature differences across major versions.

Feature 1.28 1.29 1.30 1.31 1.32
Autopilot support Full Full Full Full Full
Gateway API Beta Beta Stable Stable Stable
Sidecar containers No Alpha Beta Stable Stable
Workload Identity Fed. Stable Enhanced Enhanced Enhanced Enhanced
GKE Dataplane V2 Stable Stable Enhanced Enhanced Enhanced
Release channel avail. All All All All Rapid+Regular
Multi-cluster mesh Anthos Anthos Fleet Fleet Fleet
Cost optimization Basic Improved Enhanced Enhanced Enhanced

Embed Badges

Add live Google Kubernetes Engine (GKE) status badges to your README, docs, or dashboard.

Health Status

Overall support health

Google Kubernetes Engine (GKE) Health Status
![Google Kubernetes Engine (GKE) Health Status](https://img.releaserun.com/badge/health/google-kubernetes-engine.svg)

EOL Countdown

Next end-of-life date

Google Kubernetes Engine (GKE) EOL Countdown
![Google Kubernetes Engine (GKE) EOL Countdown](https://img.releaserun.com/badge/eol/google-kubernetes-engine.svg)

Latest Version

Current stable release

Google Kubernetes Engine (GKE) Latest Version
![Google Kubernetes Engine (GKE) Latest Version](https://img.releaserun.com/badge/v/google-kubernetes-engine.svg)

CVE Status

Known vulnerabilities

Google Kubernetes Engine (GKE) CVE Status
![Google Kubernetes Engine (GKE) CVE Status](https://img.releaserun.com/badge/cve/google-kubernetes-engine.svg)

Frequently Asked Questions

Common questions about Google Kubernetes Engine (GKE) releases and lifecycle.

What are GKE release channels?
GKE offers three release channels: Rapid (newest versions first, for testing), Regular (default, balanced), and Stable (most tested, for production). Each channel gets the same K8s versions but at different times. Rapid gets a version ~2 weeks after upstream, Regular ~4-6 weeks, and Stable ~2-3 months. Google handles patch upgrades automatically within your channel.
What is GKE Autopilot?
Autopilot is a fully managed GKE mode where Google manages the nodes, scaling, security, and OS. You only define pods/workloads. Pricing is per-pod resource request (no paying for idle node capacity). Autopilot enforces best practices (no privileged pods, no host network, mandatory resource requests). It is recommended for most new clusters. Standard mode gives you node-level control.
How does GKE auto-upgrade work?
GKE auto-upgrades clusters enrolled in a release channel. Minor version upgrades happen during maintenance windows with surge upgrades (extra nodes for zero downtime). You can set exclusion windows to block upgrades during critical periods. If you opt out of release channels, you must manage upgrades manually. Auto-upgraded clusters cannot skip versions.
How far behind upstream K8s is GKE?
GKE Rapid channel gets new K8s versions within 2-3 weeks of upstream GA. Regular channel within 4-6 weeks. Stable within 2-3 months. GKE runs additional testing against Google Cloud services (GCE persistent disks, Cloud Load Balancing, Workload Identity) before releasing each version. GKE supports the latest 4-5 K8s minor versions.
GKE vs EKS vs AKS: when to choose GKE?
GKE has the best managed Kubernetes experience: Autopilot removes node management entirely, release channels automate upgrades, and the GKE dashboard is the most polished. Choose GKE if you are on Google Cloud, want minimal K8s operations overhead, or need advanced features like multi-cluster mesh (Anthos). EKS is better for AWS-native workloads. AKS is cheapest (free control plane).
What is the GKE extended support policy?
When a K8s version leaves standard support, GKE offers extended support for an additional period (varies by version). Extended support provides security patches but no new features. Unlike EKS, GKE extended support pricing is included for Enterprise tier clusters. For Standard tier, it is an additional charge. Always upgrade proactively to avoid relying on extended support.

Related Tools