gcloud: Wed May 1 09:26:55 UTC 2024

gcloud/container/clusters/create-auto

@@ -11,6 +11,7 @@ SYNOPSIS
         [--cluster-ipv4-cidr=CLUSTER_IPV4_CIDR]
         [--cluster-secondary-range-name=NAME]
         [--cluster-version=CLUSTER_VERSION]
+        [--containerd-config-from-file=CONTAINERD_CONFIG_FROM_FILE]
         [--create-subnetwork=[KEY=VALUE,...]]
         [--database-encryption-key=DATABASE_ENCRYPTION_KEY]
         [--enable-backup-restore] [--enable-cilium-clusterwide-network-policy]
@@ -127,6 +128,10 @@ FLAGS
         within VPCs that peer with this cluster. You should specify
         --cluster-ipv4-cidr to prevent conflicts.
 
+        This field is not applicable in a Shared VPC setup where the IP address
+        range for the pods must be specified with
+        --cluster-secondary-range-name
+
      --cluster-secondary-range-name=NAME
         Set the secondary range to be used as the source for pod IPs. Alias
         ranges will be allocated from this secondary range. NAME must be the
@@ -143,6 +148,17 @@ FLAGS
 
             $ gcloud container get-server-config
 
+     --containerd-config-from-file=CONTAINERD_CONFIG_FROM_FILE
+        Path of the YAML file that contains containerd configuration entries
+        like configuring access to private image registries.
+
+        For detailed information on the configuration usage, please refer to
+        https://cloud.google.com/kubernetes-engine/docs/how-to/customize-containerd-configuration.
+
+        Note: Updating the containerd configuration of an existing cluster or
+        node pool requires recreation of the existing nodes, which might cause
+        disruptions in running workloads.
+
      --create-subnetwork=[KEY=VALUE,...]
         Create a new subnetwork for the cluster. The name and range of the
         subnetwork can be customized via optional 'name' and 'range' key-value