timetobail

Google Kubernetes Engine (GKE) · Forced move · Tracked since October 17, 2026 · Sources checked Oct 17

Time to bail on GKE clusters on version 1.32?

Time to Bail · Boarding pass

FromGKE clusters on version 1.32
ToYour pick

Act. You can stay.

Extended support for GKE 1.32 ends February 11, 2027. Then GKE upgrades the cluster for you.[1]

Act means: change a setting or plan before the date. You can stay.

Gate closes
End of extended support
Time left
116days
Status
Act

GKE 1.32 extended support ends February 11, 2027

Extended support for GKE version 1.32 ends on February 11, 2027. After that, GKE upgrades these clusters itself. Clusters past standard support also pay an extra fee per hour.

Email me 7 days before Feb 11

One email with the first steps. Nothing else.

Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar

What to do before February 11

Tick steps as you go. Your progress stays in this browser.

  1. Check your cluster versions

    In the console, open Kubernetes Engine and check each cluster. Look for 1.32.

  2. Upgrade before GKE does it

    Upgrade the control plane, then the node pools. Test your apps after each step.

  3. Plan the next upgrade

    Each month past standard support on the Extended channel costs a fee.

Email me 7 days before Feb 11

One email with the first steps. Nothing else.

Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar

Facts we checked

Facts and their sources
End of extended supportFebruary 11, 2027[1]
VersionGKE 1.32; its standard support ended April 27, 2026[1]
If you do nothingGKE upgrades the cluster to the next minor version (1.33), even if it uses deprecated APIs[3]
After that dateNo more security patches for this version[3]
Extended period fee$0.50 per cluster per hour, on top of $0.10, for a total of $0.60 per cluster per hour[2]
When the fee appliesAfter a cluster on the Extended channel reaches the end of standard support[2]
Next dates1.33 extended support ends June 12, 2027; 1.34 standard support ends January 25, 2027[1]
Can the dates change?Yes. Google says the dates are best-effort predictions and might be delayed[1]
Clusters still on 1.32Upgraded by GKE after February 11, 2027[1]

After February 11, 2027 you will see

GKE upgrades clusters still on 1.32 to the next minor version, 1.33. It does this even if the cluster uses deprecated features or APIs. 1.32 gets no more security patches.

Fix

  1. Upgrade the control plane yourself first: gcloud container clusters upgrade CLUSTER_NAME --master --location=CONTROL_PLANE_LOCATION
  2. Then upgrade each node pool: gcloud container clusters upgrade CLUSTER_NAME --node-pool=NODE_POOL_NAME --location=CONTROL_PLANE_LOCATION

Source: [1] GKE release schedule (Google Cloud) · [3] GKE versioning and support (Google Cloud) · [4] Manually upgrading a cluster or node pool (Google Cloud)

Sources

Check it yourself. Every fact above links here.

  1. GKE release schedule Google Cloud · primary · checked Oct 17
  2. Google Kubernetes Engine pricing Google Cloud · primary · checked Oct 17
  3. GKE versioning and support Google Cloud · primary · checked Oct 17
  4. Manually upgrading a cluster or node pool Google Cloud · primary · checked Oct 17
Read the published editorial report

What changed

Time to bail on GKE clusters on version 1.32? Act. You can stay. Extended support for GKE 1.32 ends February 11, 2027. Then GKE upgrades the cluster for you.

On our scale this is Act: change a setting or plan before the date. You can stay.

Extended support for GKE version 1.32 ends on February 11, 2027. After that, GKE upgrades these clusters itself. Clusters past standard support also pay an extra fee per hour.

Here are the facts we checked:

  • End of extended support: February 11, 2027 (Google Cloud)
  • Version: GKE 1.32; its standard support ended April 27, 2026 (Google Cloud)
  • If you do nothing: GKE upgrades the cluster to the next minor version (1.33), even if it uses deprecated APIs (Google Cloud)
  • After that date: No more security patches for this version (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 dates: 1.33 extended support ends June 12, 2027; 1.34 standard support ends January 25, 2027 (Google Cloud)
  • Can the dates change?: Yes. Google says the dates are best-effort predictions and might be delayed (Google Cloud)
  • Clusters still on 1.32: Upgraded by GKE after February 11, 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 still on 1.32: Upgraded by GKE after February 11, 2027.

The date to remember is February 11, 2027. Make the change before then.

What to do before February 11

  1. Check your cluster versions. In the console, open Kubernetes Engine and check each cluster. Look for 1.32.
  2. Upgrade before GKE does it. Upgrade the control plane, then the node pools. Test your apps after each step.
  3. Plan the next upgrade. Each month past standard support on the Extended channel costs a fee.

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

Thanks.

Did this answer your question?

Run SaaS spend at work? Get these changes before the invoice

Arrivals · for builders

Building where they land?

People on GKE clusters on version 1.32 can stay if they make the change. Some would rather leave. Get the playbook for this change, and list your product here.

Listing is free. An editor checks it. Not ranked. Not paid.