What changed
Time to bail on GKE clusters on version 1.34? Act. You can stay. Standard support for GKE 1.34 ends January 25, 2027. Then GKE upgrades the cluster, or the Extended channel fee starts.
On our scale this is Act: change a setting or plan before the date. You can stay.
Standard support for GKE version 1.34 ends on January 25, 2027. GKE then upgrades clusters that are not on the Extended channel. Clusters on the Extended channel can stay, for an extra fee per hour.
Here are the facts we checked:
- End of standard support: January 25, 2027 (Google Cloud)
- Version: GKE 1.34 (Google Cloud)
- If you do nothing: GKE upgrades clusters that are not on the Extended channel to a supported minor version (Google Cloud)
- Nodes too: GKE also upgrades nodes on unsupported versions, even with auto-upgrade off (Google Cloud)
- Extended channel: 1.34 gets security patches until November 25, 2027 (Google Cloud)
- Extended period fee: $0.50 per cluster per hour, on top of $0.10, for a total of $0.60 per cluster per hour (Google Cloud)
- When the fee applies: After a cluster on the Extended channel reaches the end of standard support (Google Cloud)
- Next date: GKE 1.35 standard support ends April 11, 2027 (Google Cloud)
- Can the dates change?: Yes. Google says the dates are best-effort predictions and might be delayed (Google Cloud)
- Clusters on 1.34: Upgraded by GKE, or pay the extended fee, after January 25, 2027 (Google Cloud)
You can stay on Google Kubernetes Engine (GKE). You have to change a setting or plan before the date.
Leaving is a choice here, not a must.
Google Cloud is the main source for this page. Google Kubernetes Engine (GKE) has not said more than what is listed here. If a fact is not on this page, we do not know it yet.
Who is affected
Clusters on 1.34: Upgraded by GKE, or pay the extended fee, after January 25, 2027.
The date to remember is January 25, 2027. Make the change before then.
What to do before January 25
- Check your clusters. In the console, check the version and release channel of each cluster. Look for 1.34.
- Upgrade on your own schedule. Upgrade the control plane, then the node pools. Test your apps after each step.
- Or plan the Extended channel. If you must stay, budget for the extra fee per cluster per hour.
A few tips:
- Make the change yourself before the date. Do not wait for the last reminder email.
- Write down your current plan or settings first, so you can compare after the change.
- After the change, open your settings again and check that it worked.
How to tell your users
If the change affects your members or team, send one short email. Say what changes for them and when. Put the most important line first.
If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.
Options people mention
Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.
Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.
Questions people ask
No questions collected yet.
Sources