Update your AKS attached cluster

Updating a cluster means updating the attributes or version associated with GKE attached clusters. This does not 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.

gcloud CLI

To update an attached cluster, run the following command:

gcloud container attached clusters update CLUSTER_NAME \
  --location GOOGLE_CLOUD_REGION \
  --PARAMETER-NAME=VALUE

Replace:

  • CLUSTER_NAME: the name of your cluster
  • GOOGLE_CLOUD_REGION: the name of the Google Cloud region to administer your cluster from
  • PARAMETER_NAME and VALUE: the parameter to update and the value to set it to as listed in the following table
Parameter-name Value Example
description Text description of the cluster. "Pre-production test cluster"
clear-description No value. Removes the current description from the cluster. In this case do not include the "=" sign. -
platform-version Attached cluster version. Updates attached cluster components only; does not update the cluster version. "1.23.0-gke.1"
annotations Comma-separated list of cluster annotations. "key1=value1,key2=value2"
admin-users Comma-separated list of users to be granted administrative privileges on the cluster. This also lets users log on to the console using their Google identity. "user1@corp.com,user2@corp.com"
clear-admin-users No value. Removes the set administrator users from the cluster. In this case don't include the "=" sign. -
admin-groups Comma-separated list of Google groups to be granted administrative privileges on the cluster. "group1@corp.com,group2@corp.com"
clear-admin-groups No value. Removes the set administrator groups from the cluster. In this case don't include the "=" sign. -
binauthz-evaluation-mode Set Binary Authorization evaluation mode for this cluster. Must be one of DISABLED, PROJECT_SINGLETON_POLICY_ENFORCE "PROJECT_SINGLETON_POLICY_ENFORCE"
logging Comma separated list of components that have logging enabled or "NONE". Valid values include NONE, SYSTEM, WORKLOAD. "SYSTEM,WORKLOAD"
enable-managed-prometheus No value. Enable managed collection for Managed Service for Prometheus. Don't include the "=" sign. -
disable-managed-prometheus No value. Disable managed collection for Managed Service for Prometheus. Don't include the "=" sign. -
proxy-secret-name Name of the Kubernetes Secret that contains the HTTP/HTTPS proxy configuration. "cluster-proxy-info"
proxy-secret-namespace Namespace of the Kubernetes Secret that contains the HTTP/HTTPS proxy configuration. "cluster-proxy-secret-ns"

Updating the platform version does not upgrade your cluster from a previous-generation cluster to the current generation. This command operates only on current-generation clusters and, when used with the parameter platform-version, updates the version of the GKE attached clusters software installed on your cluster.

For more information, see gcloud container attached clusters update.

Console

  1. In the console, go to the Anthos Clusters page.

    Go to Anthos Clusters

  2. Select the Google Cloud project that the cluster is in.

  3. In the Anthos managed clusters section, click on the name of the cluster you want to update, and then select View more details in the side panel.

  4. On the Details tab, you can update basic information about the cluster or upgrade the GKE attached clusters version.

    • To update cluster basics:

      1. Select Edit next to a field that you want to change.

      2. When you are finished making changes, select Done.

    • To upgrade the GKE attached clusters version:

      1. Select Upgrade available next to Platform version.

      2. Select the version from the list, and click Done.

    Upgrading the platform version doesn't change the Kubernetes version on the 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.