Stay organized with collections
Save and categorize content based on your preferences.
GKE on Azure deprecation announcement
GKE on Azure will no longer be supported on March 17, 2027.
What this means
Google will cease maintenance and contracted support for GKE on Azure
from March 17, 2027.
The following schedule lists the significant dates in this shutdown.
March 17, 2025: Maintenance mode starts.
Google continues to fix bugs and resolve CVEs during this phase.
Google support contracts continue as before.
No new functionality will be added except as needed to fix bugs.
March 17, 2027: Product no longer supported.
No further upgrades or bug fixes occur.
APIs will be disabled.
What you should do now
We recommend that you migrate to GKE or another Kubernetes
distribution before March 17, 2027. To continue using
GKE Enterprise features, you can use
GKE attached clusters.
To migrate from GKE on Azure to another Kubernetes distribution, keep
the following points in mind:
Deploy new Kubernetes clusters with the same configurations as your
GKE on Azure clusters. To ensure identical configurations across
your old and new clusters, you can use
Config Sync
or another GitOps solution.
Identify the workloads that you want to migrate to the new GKE on Azure cluster.
Deploy a single workload on your new cluster and update the DNS settings to
enable your old GKE on Azure cluster to point to the same workload on
the new cluster.
Test the new workload.
Repeat the preceding two steps for all the workloads that you want to deploy on the
cluster.
Your account's lead customer engineer is your best contact point for deprecation
support. Alternatively, you can file a support case
through Google Cloud console or contact Cloud Customer Care.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[],[],null,["# GKE on Azure deprecation announcement\n=====================================\n\nGKE on Azure will no longer be supported on March 17, 2027.\n\nWhat this means\n---------------\n\nGoogle will cease maintenance and contracted support for GKE on Azure\nfrom March 17, 2027.\n\nThe following schedule lists the significant dates in this shutdown.\n\n- **March 17, 2025**: Maintenance mode starts.\n\n - Google continues to fix bugs and resolve CVEs during this phase.\n - Google support contracts continue as before.\n - No new functionality will be added except as needed to fix bugs.\n- **March 17, 2027**: Product no longer supported.\n\n - No further upgrades or bug fixes occur.\n - APIs will be disabled.\n\nWhat you should do now\n----------------------\n\nWe recommend that you migrate to GKE or another Kubernetes\ndistribution before March 17, 2027. To continue using\nGKE Enterprise features, you can use\n[GKE attached clusters](/kubernetes-engine/multi-cloud/docs/attached).\n\nTo migrate from GKE on Azure to another Kubernetes distribution, keep\nthe following points in mind:\n\n1. Deploy new Kubernetes clusters with the same configurations as your GKE on Azure clusters. To ensure identical configurations across your old and new clusters, you can use [Config Sync](/anthos-config-management/docs/config-sync-overview) or another GitOps solution.\n2. Identify the workloads that you want to migrate to the new GKE on Azure cluster.\n3. Deploy a single workload on your new cluster and update the DNS settings to enable your old GKE on Azure cluster to point to the same workload on the new cluster.\n4. Test the new workload.\n5. Repeat the preceding two steps for all the workloads that you want to deploy on the cluster.\n6. After all workloads are migrated and tested, [delete your GKE on Azure clusters](/kubernetes-engine/multi-cloud/docs/azure/how-to/delete-cluster).\n\nContact Cloud Customer Care\n---------------------------\n\nYour account's lead customer engineer is your best contact point for deprecation\nsupport. Alternatively, you can [file a support case](https://console.cloud.google.com/support)\nthrough Google Cloud console or contact [Cloud Customer Care](/support/docs/customer-care-procedures#manage_a_support_case)."]]
