The product described by this documentation, Anthos Clusters on AWS (previous generation), is now in maintenance mode. All new installs must use the current generation product, Anthos clusters on AWS.
Stay organized with collections
Save and categorize content based on your preferences.
GKE on AWS (previous generation) will be deprecated as of April 1, 2023.
What this means
GKE on AWS (previous generation) is being replaced by the next generation
of Anthos Clusters on AWS. Google will cease maintenance and contracted support
for the previous generation product when maintenance mode ends.
The schedule below lists the significant dates in this transition.
Jan 1, 2022: Maintenance mode starts
Google continues to fix bugs, support new Kubernetes versions, and resolve
CVEs during this phase
Google support contracts continue as before
No new functionality will be added except as needed to fix bugs
The previous generation product can still be used to reinstall existing
installations, but should not be used for new clusters in new environments
April 1, 2023: Product deprecation completes
No further upgrades or bug fixes occur
All GKE on AWS installations should migrate to the current generation
of Anthos Clusters on AWS well before this point
Why we're doing this
Google is committed to providing the best possible Kubernetes management
experience for our customers. Our new generation of GKE on AWS
offers a richer feature set, simplified installation and configuration, and
greater security. And through its integration with Google Cloud console, it
participates in Google's consolidated dashboard for unified monitoring and
maintenance of clusters in all the cloud environments that Google supports.
What you should do now
Google support has notified our customers of this schedule, so you may
have started planning your migration strategy already. We recommend
beginning this process if you haven't already.
As your first step, contact Google support. Our customer
engineers are committed to making this migration a simple and straightforward
process for all our customers.
General upgrade strategy
Your upgrade strategy must be tailored to your environment, but the
broad strategy will be similar for most customers:
Upgrade your existing previous generation clusters to Kubernetes v1.21. This
version is supported on both the previous and current generation of
GKE on AWS.
Deploy current generation clusters with identical Kubernetes configurations.
Consider using
Config Management
to ensure identical configurations across your old and new clusters.
Deploy a single service on your new cluster, and update the DNS settings for
your previous generation cluster to point to the same services on the new cluster.
Test the service on the new cluster.
Repeat these two steps for your remaining services.
Your account's lead customer engineer is your best contact point for migration
support. Alternatively, you can
file a support case
through Google Cloud console. Your request will be routed to your account's customer
engineering group.
[[["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-09-04 UTC."],[],[],null,["# GKE on AWS Deprecation Announcement\n\nGKE on AWS (previous generation) will be deprecated as of April 1, 2023.\n\nWhat this means\n---------------\n\nGKE on AWS (previous generation) is being replaced by the next generation\nof Anthos Clusters on AWS. Google will cease maintenance and contracted support\nfor the previous generation product when maintenance mode ends.\n\nThe schedule below lists the significant dates in this transition.\n\n- Jan 1, 2022: Maintenance mode starts\n - Google continues to fix bugs, support new Kubernetes versions, 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 - The previous generation product can still be used to reinstall existing installations, but should not be used for new clusters in new environments\n- April 1, 2023: Product deprecation completes\n - No further upgrades or bug fixes occur\n - All GKE on AWS installations should migrate to the current generation of Anthos Clusters on AWS well before this point\n\nWhy we're doing this\n--------------------\n\nGoogle is committed to providing the best possible Kubernetes management\nexperience for our customers. Our new generation of GKE on AWS\noffers a richer feature set, simplified installation and configuration, and\ngreater security. And through its integration with Google Cloud console, it\nparticipates in Google's consolidated dashboard for unified monitoring and\nmaintenance of clusters in all the cloud environments that Google supports.\n\nWhat you should do now\n----------------------\n\nGoogle support has notified our customers of this schedule, so you may\nhave started planning your migration strategy already. We recommend\nbeginning this process if you haven't already.\n| **Note:** although upgrading your cluster version is part of the process, this is an upgrade to the entire GKE on AWS product.\n\nAs your first step, contact Google support. Our customer\nengineers are committed to making this migration a simple and straightforward\nprocess for all our customers.\n\nGeneral upgrade strategy\n------------------------\n\nYour upgrade strategy must be tailored to your environment, but the\nbroad strategy will be similar for most customers:\n\n1. Upgrade your existing previous generation clusters to Kubernetes v1.21. This\n version is supported on both the previous and current generation of\n GKE on AWS.\n\n2. Deploy current generation clusters with identical Kubernetes configurations.\n Consider using\n [Config Management](/kubernetes-engine/multi-cloud/docs/aws/previous-generation/how-to/installing-config-management)\n to ensure identical configurations across your old and new clusters.\n\n3. Deploy a single service on your new cluster, and update the DNS settings for\n your previous generation cluster to point to the same services on the new cluster.\n\n4. Test the service on the new cluster.\n\n5. Repeat these two steps for your remaining services.\n\n6. After all services have been migrated and tested,\n [decommission the previous generation](/kubernetes-engine/multi-cloud/docs/aws/previous-generation/how-to/uninstalling)\n cluster and management service.\n\nContact Cloud Customer Care\n---------------------------\n\nYour account's lead customer engineer is your best contact point for migration\nsupport. Alternatively, you can\n[file a support case](https://console.cloud.google.com/support)\nthrough Google Cloud console. Your request will be routed to your account's customer\nengineering group."]]
