Stay organized with collections
Save and categorize content based on your preferences.
Updating a cluster means updating the attributes or version associated with
GKE attached clusters. This doesn't change the Kubernetes version that the cluster
is running or update cluster attributes not related to GKE attached clusters. You can
update the cluster with the Google Cloud CLI or the Google Cloud console.
Select the Google Cloud project that the cluster is in.
Click the name of the cluster you want to update, and then select View
more details in the side panel.
On the Details tab, you can update basic information about the
cluster or upgrade the GKE attached clusters version.
To update cluster basics:
Select edit Edit next to
a field that you want to change.
When you are finished making changes, select Done.
To upgrade the GKE attached clusters version:
Select editUpgrade available next to Platform version.
Select the version from the list, and click Done.
Upgrading the platform version doesn't change the Kubernetes version
on the cluster.
Use the --platform-version argument to upgrade your cluster
Use the optional --platform-version argument with the
gcloud container attached clusters update command to upgrade the
version of the GKE attached clusters software installed on your
cluster. For example, this lets you upgrade from version 1.28.0-gke.1 to
1.28.0-gke.3, or from version 1.28.x to 1.29.y.
However, the gcloud container attached clusters update command can't be used
to upgrade a cluster attached using the previous generation of
GKE attached clusters to the current generation. This previous generation
is older and unmanaged software that no longer receives new features, fixes, or
support.
To migrate a cluster from the previous generation to the current generation,
follow the steps in
Migrate your cluster.
Platform version numbering
These documents refer to the GKE attached clusters version as the platform version,
to distinguish it from the Kubernetes version. GKE attached clusters uses the same
version numbering convention as GKE - for example, 1.21.5-gke.1. When attaching
or updating your cluster, you must choose a platform version whose minor version
is the same as or one level below the Kubernetes version of your cluster. For
example, you can attach a cluster running Kubernetes v1.22.* with
GKE attached clusters platform version 1.21.* or 1.22.*.
This lets you upgrade your cluster to the next minor version before upgrading
GKE attached clusters.
[[["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-25 UTC."],[],[],null,["# Update your CNCF conformant attached cluster\n\nUpdating a cluster means updating the attributes or version associated with\nGKE attached clusters. This doesn't change the Kubernetes version that the cluster\nis running or update cluster attributes not related to GKE attached clusters. You can\nupdate the cluster with the Google Cloud CLI or the Google Cloud console. \n\n### gcloud CLI\n\nTo update an attached cluster, use the\n[`gcloud container attached clusters update` command](/sdk/gcloud/reference/container/attached/clusters/update):\n\n```sh\ngcloud container attached clusters update CLUSTER_NAME \\\n --location GOOGLE_CLOUD_REGION\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e: the name of the cluster\n- \u003cvar translate=\"no\"\u003eGOOGLE_CLOUD_REGION\u003c/var\u003e: the name of the Google Cloud region to administer your cluster from\n\nFor information about all the arguments you can use when updating a cluster,\nsee the\n[`gcloud container attached clusters update` command](/sdk/gcloud/reference/container/attached/clusters/update).\n\n### Console\n\n1. In the Google Cloud console, go to the **Google Kubernetes Engine clusters\n overview** page.\n\n [Go to GKE clusters](https://console.cloud.google.com/kubernetes/list/overview)\n2. Select the Google Cloud project that the cluster is in.\n\n3. Click the name of the cluster you want to update, and then select **View\n more details** in the side panel.\n\n4. On the **Details** tab, you can update basic information about the\n cluster or upgrade the GKE attached clusters version.\n\n - To update cluster basics:\n\n 1. Select edit **Edit** next to\n a field that you want to change.\n\n 2. When you are finished making changes, select **Done**.\n\n - To upgrade the GKE attached clusters version:\n\n 1. Select edit\n **Upgrade available** next to **Platform version**.\n\n 2. Select the version from the list, and click **Done**.\n\n Upgrading the platform version doesn't change the Kubernetes version\n on the cluster.\n\nUse the `--platform-version` argument to upgrade your cluster\n-------------------------------------------------------------\n\nUse the optional `--platform-version` argument with the\n`gcloud container attached clusters update` command to upgrade the\nversion of the GKE attached clusters software installed on your\ncluster. For example, this lets you upgrade from version 1.28.0-gke.1 to\n1.28.0-gke.3, or from version 1.28.x to 1.29.y.\n\nHowever, the `gcloud container attached clusters update` command can't be used\nto upgrade a cluster attached using the previous generation of\n[GKE attached clusters](/kubernetes-engine/multi-cloud/docs/attached/previous-generation/how-to/attach-kubernetes-clusters) to the current generation. This previous generation\nis older and unmanaged software that no longer receives new features, fixes, or\nsupport.\n\nTo migrate a cluster from the previous generation to the current generation,\nfollow the steps in\n[Migrate your cluster](/kubernetes-engine/multi-cloud/docs/attached/generic/how-to/migrate-cluster).\n\nPlatform version numbering\n--------------------------\n\nThese documents refer to the GKE attached clusters version as the platform version,\nto distinguish it from the Kubernetes version. GKE attached clusters uses the same\nversion numbering convention as GKE - for example, 1.21.5-gke.1. When attaching\nor updating your cluster, you must choose a platform version whose minor version\nis the same as or one level below the Kubernetes version of your cluster. For\nexample, you can attach a cluster running Kubernetes v1.22.\\* with\nGKE attached clusters platform version 1.21.\\* or 1.22.\\*.\n\nThis lets you upgrade your cluster to the next minor version before upgrading\nGKE attached clusters."]]
