diff --git a/gcloud/_version b/gcloud/_version
index 003a7d7db..18e20351f 100644
--- a/gcloud/_version
+++ b/gcloud/_version
@@ -1,8 +1,8 @@
-Google Cloud SDK 443.0.0
-alpha 2023.08.11
-beta 2023.08.11
-bq 2.0.96
+Google Cloud SDK 444.0.0
+alpha 2023.08.22
+beta 2023.08.22
+bq 2.0.97
 bundled-python3-unix 3.9.16
-core 2023.08.11
+core 2023.08.22
 gcloud-crc32c 1.0.0
 gsutil 5.25
diff --git a/gcloud/active-directory/domains/backups/create b/gcloud/active-directory/domains/backups/create
index 734e7afbb..187b91e81 100644
--- a/gcloud/active-directory/domains/backups/create
+++ b/gcloud/active-directory/domains/backups/create
@@ -4,7 +4,7 @@ NAME
 
 SYNOPSIS
     gcloud active-directory domains backups create (BACKUP : --domain=DOMAIN)
-        [--async] [--labels=KEY=VALUE] [GCLOUD_WIDE_FLAG ...]
+        [--async] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     Create a new Managed Microsoft AD domain backup with the specified name
@@ -63,7 +63,7 @@ FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
 GCLOUD WIDE FLAGS
diff --git a/gcloud/active-directory/domains/create b/gcloud/active-directory/domains/create
index 20525ec56..e85cbb2f1 100644
--- a/gcloud/active-directory/domains/create
+++ b/gcloud/active-directory/domains/create
@@ -6,7 +6,7 @@ SYNOPSIS
     gcloud active-directory domains create DOMAIN --region=[REGION,...]
         --reserved-ip-range=RESERVED_IP_RANGE [--admin-name=ADMIN_NAME]
         [--async] [--authorized-networks=[AUTHORIZED_NETWORKS,...]]
-        [--enable-audit-logs] [--labels=KEY=VALUE] [GCLOUD_WIDE_FLAG ...]
+        [--enable-audit-logs] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     Create a new Managed Microsoft AD domain with the given name using Google
@@ -76,7 +76,7 @@ OPTIONAL FLAGS
         If specified, Active Directory data audit logs are enabled for the
         domain.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
 GCLOUD WIDE FLAGS
diff --git a/gcloud/alloydb/clusters/create b/gcloud/alloydb/clusters/create
index 521fb4c37..dfa9b8d8d 100644
--- a/gcloud/alloydb/clusters/create
+++ b/gcloud/alloydb/clusters/create
@@ -4,7 +4,8 @@ NAME
 
 SYNOPSIS
     gcloud alloydb clusters create CLUSTER --password=PASSWORD --region=REGION
-        [--async] [--network=NETWORK]
+        [--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME] [--async]
+        [--network=NETWORK]
         [--continuous-backup-recovery-window-days=RECOVERY_PERIOD
           --enable-continuous-backup
           [--continuous-backup-encryption-key=CONTINUOUS_BACKUP_ENCRYPTION_KEY
@@ -41,6 +42,14 @@ REQUIRED FLAGS
         regions at https://cloud.google.com/sql/docs/instance-locations.
 
 OPTIONAL FLAGS
+     --allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME
+        Name of the allocated IP range for the private IP AlloyDB cluster, for
+        example: "google-managed-services-default". If set, the instance IPs
+        for this cluster will be created in the allocated range. The range name
+        must comply with RFC 1035. Specifically, the name must be 1-63
+        characters long and match the regular expression
+        [a-z]([-a-z0-9][a-z0-9])?.
+
      --async
         Return immediately, without waiting for the operation in progress to
         complete.
diff --git a/gcloud/alloydb/clusters/create-secondary b/gcloud/alloydb/clusters/create-secondary
index e11676997..2aa18ade4 100644
--- a/gcloud/alloydb/clusters/create-secondary
+++ b/gcloud/alloydb/clusters/create-secondary
@@ -4,7 +4,8 @@ NAME
 
 SYNOPSIS
     gcloud alloydb clusters create-secondary CLUSTER
-        --primary-cluster=PRIMARY_CLUSTER --region=REGION [--async]
+        --primary-cluster=PRIMARY_CLUSTER --region=REGION
+        [--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME] [--async]
         [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING
           --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]
         [GCLOUD_WIDE_FLAG ...]
@@ -33,6 +34,14 @@ REQUIRED FLAGS
         regions at https://cloud.google.com/sql/docs/instance-locations.
 
 OPTIONAL FLAGS
+     --allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME
+        Name of the allocated IP range for the private IP AlloyDB cluster, for
+        example: "google-managed-services-default". If set, the instance IPs
+        for this cluster will be created in the allocated range. The range name
+        must comply with RFC 1035. Specifically, the name must be 1-63
+        characters long and match the regular expression
+        [a-z]([-a-z0-9][a-z0-9])?.
+
      --async
         Return immediately, without waiting for the operation in progress to
         complete.
diff --git a/gcloud/alloydb/clusters/restore b/gcloud/alloydb/clusters/restore
index 1fef89cae..4e0b195f0 100644
--- a/gcloud/alloydb/clusters/restore
+++ b/gcloud/alloydb/clusters/restore
@@ -6,7 +6,8 @@ SYNOPSIS
     gcloud alloydb clusters restore CLUSTER --region=REGION
         (--backup=BACKUP
           | --point-in-time=POINT_IN_TIME --source-cluster=SOURCE_CLUSTER)
-        [--async] [--network=NETWORK]
+        [--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME] [--async]
+        [--network=NETWORK]
         [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING
           --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]
         [GCLOUD_WIDE_FLAG ...]
@@ -59,6 +60,14 @@ REQUIRED FLAGS
             in this group are specified.
 
 OPTIONAL FLAGS
+     --allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME
+        Name of the allocated IP range for the private IP AlloyDB cluster, for
+        example: "google-managed-services-default". If set, the instance IPs
+        for this cluster will be created in the allocated range. The range name
+        must comply with RFC 1035. Specifically, the name must be 1-63
+        characters long and match the regular expression
+        [a-z]([-a-z0-9][a-z0-9])?.
+
      --async
         Return immediately, without waiting for the operation in progress to
         complete.
diff --git a/gcloud/alloydb/instances/create b/gcloud/alloydb/instances/create
index 6dc2967a1..a08d17ba1 100644
--- a/gcloud/alloydb/instances/create
+++ b/gcloud/alloydb/instances/create
@@ -11,7 +11,9 @@ SYNOPSIS
         [--insights-config-query-string-length=INSIGHTS_CONFIG_QUERY_STRING_LENGTH]
         [--[no-]insights-config-record-application-tags]
         [--[no-]insights-config-record-client-address]
-        [--read-pool-node-count=READ_POOL_NODE_COUNT] [GCLOUD_WIDE_FLAG ...]
+        [--read-pool-node-count=READ_POOL_NODE_COUNT]
+        [--[no-]require-connectors]
+        [--ssl-mode=SSL_MODE; default="ENCRYPTED_ONLY"] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     Creates a new AlloyDB instance within a given cluster.
@@ -64,13 +66,16 @@ OPTIONAL FLAGS
         complete.
 
      --availability-type=AVAILABILITY_TYPE
-        Specifies level of availability. AVAILABILITY_TYPE must be (only one
-        value is supported):
+        Specifies level of availability. AVAILABILITY_TYPE must be one of:
 
          REGIONAL
-            Provides high availability and is recommended for production
-            instances; instance automatically fails over to another zone within
+            Provide high availability instances. Recommended for production
+            instances; instances automatically fail over to another zone within
             your selected region.
+         ZONAL
+            Provide zonal availability instances. Not recommended for
+            production instances; instance does not automatically fail over to
+            another zone.
 
      --database-flags=FLAG=VALUE,[FLAG=VALUE,...]
         Comma-separated list of database flags to set on the instance. Use an
@@ -104,6 +109,20 @@ OPTIONAL FLAGS
      --read-pool-node-count=READ_POOL_NODE_COUNT
         Read capacity, i.e. number of nodes in a read pool instance.
 
+     --[no-]require-connectors
+        Enable or disable enforcing connectors only (ex: AuthProxy)connections
+        to the database. Use --require-connectors to enable and
+        --no-require-connectors to disable.
+
+     --ssl-mode=SSL_MODE; default="ENCRYPTED_ONLY"
+        Specify the SSL mode to use when the instance connects to the database.
+        Default SSL mode is ENCRYPTED_ONLY. SSL_MODE must be one of:
+
+         ALLOW_UNENCRYPTED_AND_ENCRYPTED
+            SSL connections are optional. CA verification is not enforced.
+         ENCRYPTED_ONLY
+            SSL connections are required. CA verification is not enforced.
+
 GCLOUD WIDE FLAGS
     These flags are available to all commands: --access-token-file, --account,
     --billing-project, --configuration, --flags-file, --flatten, --format,
diff --git a/gcloud/alloydb/instances/create-secondary b/gcloud/alloydb/instances/create-secondary
index 91a706a6d..bde6c986d 100644
--- a/gcloud/alloydb/instances/create-secondary
+++ b/gcloud/alloydb/instances/create-secondary
@@ -4,7 +4,8 @@ NAME
 
 SYNOPSIS
     gcloud alloydb instances create-secondary INSTANCE --cluster=CLUSTER
-        --region=REGION [--async] [GCLOUD_WIDE_FLAG ...]
+        --region=REGION [--async] [--availability-type=AVAILABILITY_TYPE]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     Creates a new AlloyDB SECONDARY instance within a given cluster.
@@ -32,6 +33,18 @@ OPTIONAL FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
+     --availability-type=AVAILABILITY_TYPE
+        Specifies level of availability. AVAILABILITY_TYPE must be one of:
+
+         REGIONAL
+            Provide high availability instances. Recommended for production
+            instances; instances automatically fail over to another zone within
+            your selected region.
+         ZONAL
+            Provide zonal availability instances. Not recommended for
+            production instances; instance does not automatically fail over to
+            another zone.
+
 GCLOUD WIDE FLAGS
     These flags are available to all commands: --access-token-file, --account,
     --billing-project, --configuration, --flags-file, --flatten, --format,
diff --git a/gcloud/alloydb/instances/update b/gcloud/alloydb/instances/update
index 541b3d187..02973c700 100644
--- a/gcloud/alloydb/instances/update
+++ b/gcloud/alloydb/instances/update
@@ -10,7 +10,9 @@ SYNOPSIS
         [--insights-config-query-string-length=INSIGHTS_CONFIG_QUERY_STRING_LENGTH]
         [--[no-]insights-config-record-application-tags]
         [--[no-]insights-config-record-client-address]
-        [--read-pool-node-count=READ_POOL_NODE_COUNT] [GCLOUD_WIDE_FLAG ...]
+        [--read-pool-node-count=READ_POOL_NODE_COUNT]
+        [--[no-]require-connectors] [--ssl-mode=SSL_MODE]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     Updates an AlloyDB instance within a given cluster.
@@ -40,13 +42,16 @@ OPTIONAL FLAGS
         complete.
 
      --availability-type=AVAILABILITY_TYPE
-        Specifies level of availability. AVAILABILITY_TYPE must be (only one
-        value is supported):
+        Specifies level of availability. AVAILABILITY_TYPE must be one of:
 
          REGIONAL
-            Provides high availability and is recommended for production
-            instances; instance automatically fails over to another zone within
+            Provide high availability instances. Recommended for production
+            instances; instances automatically fail over to another zone within
             your selected region.
+         ZONAL
+            Provide zonal availability instances. Not recommended for
+            production instances; instance does not automatically fail over to
+            another zone.
 
      --cpu-count=CPU_COUNT
         Whole number value indicating how many vCPUs the machine should
@@ -86,6 +91,20 @@ OPTIONAL FLAGS
      --read-pool-node-count=READ_POOL_NODE_COUNT
         Read capacity, i.e. number of nodes in a read pool instance.
 
+     --[no-]require-connectors
+        Enable or disable enforcing connectors only (ex: AuthProxy)connections
+        to the database. Use --require-connectors to enable and
+        --no-require-connectors to disable.
+
+     --ssl-mode=SSL_MODE
+        Specify the SSL mode to use when the instance connects to the database.
+        SSL_MODE must be one of:
+
+         ALLOW_UNENCRYPTED_AND_ENCRYPTED
+            SSL connections are optional. CA verification is not enforced.
+         ENCRYPTED_ONLY
+            SSL connections are required. CA verification is not enforced.
+
 GCLOUD WIDE FLAGS
     These flags are available to all commands: --access-token-file, --account,
     --billing-project, --configuration, --flags-file, --flatten, --format,
diff --git a/gcloud/alpha/active-directory/domains/backups/create b/gcloud/alpha/active-directory/domains/backups/create
index cd9b0eadd..a6b543457 100644
--- a/gcloud/alpha/active-directory/domains/backups/create
+++ b/gcloud/alpha/active-directory/domains/backups/create
@@ -4,7 +4,7 @@ NAME
 
 SYNOPSIS
     gcloud alpha active-directory domains backups create
-        (BACKUP : --domain=DOMAIN) [--async] [--labels=KEY=VALUE]
+        (BACKUP : --domain=DOMAIN) [--async] [--labels=[KEY=VALUE,...]]
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -64,7 +64,7 @@ FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
 GCLOUD WIDE FLAGS
diff --git a/gcloud/alpha/active-directory/domains/create b/gcloud/alpha/active-directory/domains/create
index ae4022ba6..a3b66bc83 100644
--- a/gcloud/alpha/active-directory/domains/create
+++ b/gcloud/alpha/active-directory/domains/create
@@ -6,7 +6,7 @@ SYNOPSIS
     gcloud alpha active-directory domains create DOMAIN --region=[REGION,...]
         --reserved-ip-range=RESERVED_IP_RANGE [--admin-name=ADMIN_NAME]
         [--async] [--authorized-networks=[AUTHORIZED_NETWORKS,...]]
-        [--enable-audit-logs] [--labels=KEY=VALUE] [GCLOUD_WIDE_FLAG ...]
+        [--enable-audit-logs] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (ALPHA) Create a new Managed Microsoft AD domain with the given name using
@@ -76,7 +76,7 @@ OPTIONAL FLAGS
         If specified, Active Directory data audit logs are enabled for the
         domain.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
 GCLOUD WIDE FLAGS
diff --git a/gcloud/alpha/alloydb/clusters/create b/gcloud/alpha/alloydb/clusters/create
index 97df9d160..9da5b7bd6 100644
--- a/gcloud/alpha/alloydb/clusters/create
+++ b/gcloud/alpha/alloydb/clusters/create
@@ -43,10 +43,10 @@ REQUIRED FLAGS
 
 OPTIONAL FLAGS
      --allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME
-        The name of the allocated IP range for the private IP AlloyDB cluster.
-        For example: "google-managed-services-default". If set, the instance
-        IPs for this cluster will be created in the allocated range. The range
-        name must comply with RFC 1035. Specifically, the name must be 1-63
+        Name of the allocated IP range for the private IP AlloyDB cluster, for
+        example: "google-managed-services-default". If set, the instance IPs
+        for this cluster will be created in the allocated range. The range name
+        must comply with RFC 1035. Specifically, the name must be 1-63
         characters long and match the regular expression
         [a-z]([-a-z0-9][a-z0-9])?.
 
diff --git a/gcloud/alpha/alloydb/clusters/create-secondary b/gcloud/alpha/alloydb/clusters/create-secondary
index 62d77ec4d..beb1bce0b 100644
--- a/gcloud/alpha/alloydb/clusters/create-secondary
+++ b/gcloud/alpha/alloydb/clusters/create-secondary
@@ -4,7 +4,8 @@ NAME
 
 SYNOPSIS
     gcloud alpha alloydb clusters create-secondary CLUSTER
-        --primary-cluster=PRIMARY_CLUSTER --region=REGION [--async]
+        --primary-cluster=PRIMARY_CLUSTER --region=REGION
+        [--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME] [--async]
         [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING
           --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]
         [GCLOUD_WIDE_FLAG ...]
@@ -33,6 +34,14 @@ REQUIRED FLAGS
         regions at https://cloud.google.com/sql/docs/instance-locations.
 
 OPTIONAL FLAGS
+     --allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME
+        Name of the allocated IP range for the private IP AlloyDB cluster, for
+        example: "google-managed-services-default". If set, the instance IPs
+        for this cluster will be created in the allocated range. The range name
+        must comply with RFC 1035. Specifically, the name must be 1-63
+        characters long and match the regular expression
+        [a-z]([-a-z0-9][a-z0-9])?.
+
      --async
         Return immediately, without waiting for the operation in progress to
         complete.
diff --git a/gcloud/alpha/alloydb/clusters/restore b/gcloud/alpha/alloydb/clusters/restore
index ce4e463cf..5f1e1f9cf 100644
--- a/gcloud/alpha/alloydb/clusters/restore
+++ b/gcloud/alpha/alloydb/clusters/restore
@@ -6,7 +6,8 @@ SYNOPSIS
     gcloud alpha alloydb clusters restore CLUSTER --region=REGION
         (--backup=BACKUP
           | --point-in-time=POINT_IN_TIME --source-cluster=SOURCE_CLUSTER)
-        [--async] [--network=NETWORK]
+        [--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME] [--async]
+        [--network=NETWORK]
         [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING
           --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]
         [GCLOUD_WIDE_FLAG ...]
@@ -59,6 +60,14 @@ REQUIRED FLAGS
             in this group are specified.
 
 OPTIONAL FLAGS
+     --allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME
+        Name of the allocated IP range for the private IP AlloyDB cluster, for
+        example: "google-managed-services-default". If set, the instance IPs
+        for this cluster will be created in the allocated range. The range name
+        must comply with RFC 1035. Specifically, the name must be 1-63
+        characters long and match the regular expression
+        [a-z]([-a-z0-9][a-z0-9])?.
+
      --async
         Return immediately, without waiting for the operation in progress to
         complete.
diff --git a/gcloud/alpha/alloydb/instances/create b/gcloud/alpha/alloydb/instances/create
index 3fb18d3f7..88cdb6668 100644
--- a/gcloud/alpha/alloydb/instances/create
+++ b/gcloud/alpha/alloydb/instances/create
@@ -11,7 +11,9 @@ SYNOPSIS
         [--insights-config-query-string-length=INSIGHTS_CONFIG_QUERY_STRING_LENGTH]
         [--[no-]insights-config-record-application-tags]
         [--[no-]insights-config-record-client-address]
-        [--read-pool-node-count=READ_POOL_NODE_COUNT] [GCLOUD_WIDE_FLAG ...]
+        [--read-pool-node-count=READ_POOL_NODE_COUNT]
+        [--[no-]require-connectors]
+        [--ssl-mode=SSL_MODE; default="ENCRYPTED_ONLY"] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (ALPHA) Creates a new AlloyDB instance within a given cluster.
@@ -68,11 +70,11 @@ OPTIONAL FLAGS
         Specifies level of availability. AVAILABILITY_TYPE must be one of:
 
          REGIONAL
-            Provides high availability and is recommended for production
-            instances; instance automatically fails over to another zone within
+            Provide high availability instances. Recommended for production
+            instances; instances automatically fail over to another zone within
             your selected region.
          ZONAL
-            Provides zonal availability instances and is not recommended for
+            Provide zonal availability instances. Not recommended for
             production instances; instance does not automatically fail over to
             another zone.
 
@@ -108,6 +110,20 @@ OPTIONAL FLAGS
      --read-pool-node-count=READ_POOL_NODE_COUNT
         Read capacity, i.e. number of nodes in a read pool instance.
 
+     --[no-]require-connectors
+        Enable or disable enforcing connectors only (ex: AuthProxy)connections
+        to the database. Use --require-connectors to enable and
+        --no-require-connectors to disable.
+
+     --ssl-mode=SSL_MODE; default="ENCRYPTED_ONLY"
+        Specify the SSL mode to use when the instance connects to the database.
+        Default SSL mode is ENCRYPTED_ONLY. SSL_MODE must be one of:
+
+         ALLOW_UNENCRYPTED_AND_ENCRYPTED
+            SSL connections are optional. CA verification is not enforced.
+         ENCRYPTED_ONLY
+            SSL connections are required. CA verification is not enforced.
+
 GCLOUD WIDE FLAGS
     These flags are available to all commands: --access-token-file, --account,
     --billing-project, --configuration, --flags-file, --flatten, --format,
diff --git a/gcloud/alpha/alloydb/instances/create-secondary b/gcloud/alpha/alloydb/instances/create-secondary
index 10fe47e43..37d590dff 100644
--- a/gcloud/alpha/alloydb/instances/create-secondary
+++ b/gcloud/alpha/alloydb/instances/create-secondary
@@ -4,7 +4,8 @@ NAME
 
 SYNOPSIS
     gcloud alpha alloydb instances create-secondary INSTANCE --cluster=CLUSTER
-        --region=REGION [--async] [GCLOUD_WIDE_FLAG ...]
+        --region=REGION [--async] [--availability-type=AVAILABILITY_TYPE]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (ALPHA) Creates a new AlloyDB SECONDARY instance within a given cluster.
@@ -32,6 +33,18 @@ OPTIONAL FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
+     --availability-type=AVAILABILITY_TYPE
+        Specifies level of availability. AVAILABILITY_TYPE must be one of:
+
+         REGIONAL
+            Provide high availability instances. Recommended for production
+            instances; instances automatically fail over to another zone within
+            your selected region.
+         ZONAL
+            Provide zonal availability instances. Not recommended for
+            production instances; instance does not automatically fail over to
+            another zone.
+
 GCLOUD WIDE FLAGS
     These flags are available to all commands: --access-token-file, --account,
     --billing-project, --configuration, --flags-file, --flatten, --format,
diff --git a/gcloud/alpha/alloydb/instances/update b/gcloud/alpha/alloydb/instances/update
index 8b3c9134e..963bd518f 100644
--- a/gcloud/alpha/alloydb/instances/update
+++ b/gcloud/alpha/alloydb/instances/update
@@ -11,6 +11,7 @@ SYNOPSIS
         [--[no-]insights-config-record-application-tags]
         [--[no-]insights-config-record-client-address]
         [--read-pool-node-count=READ_POOL_NODE_COUNT]
+        [--[no-]require-connectors] [--ssl-mode=SSL_MODE]
         [--update-mode=UPDATE_MODE] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -44,11 +45,11 @@ OPTIONAL FLAGS
         Specifies level of availability. AVAILABILITY_TYPE must be one of:
 
          REGIONAL
-            Provides high availability and is recommended for production
-            instances; instance automatically fails over to another zone within
+            Provide high availability instances. Recommended for production
+            instances; instances automatically fail over to another zone within
             your selected region.
          ZONAL
-            Provides zonal availability instances and is not recommended for
+            Provide zonal availability instances. Not recommended for
             production instances; instance does not automatically fail over to
             another zone.
 
@@ -90,6 +91,20 @@ OPTIONAL FLAGS
      --read-pool-node-count=READ_POOL_NODE_COUNT
         Read capacity, i.e. number of nodes in a read pool instance.
 
+     --[no-]require-connectors
+        Enable or disable enforcing connectors only (ex: AuthProxy)connections
+        to the database. Use --require-connectors to enable and
+        --no-require-connectors to disable.
+
+     --ssl-mode=SSL_MODE
+        Specify the SSL mode to use when the instance connects to the database.
+        SSL_MODE must be one of:
+
+         ALLOW_UNENCRYPTED_AND_ENCRYPTED
+            SSL connections are optional. CA verification is not enforced.
+         ENCRYPTED_ONLY
+            SSL connections are required. CA verification is not enforced.
+
      --update-mode=UPDATE_MODE
         Specify the mode for updating the instance. If unspecified, the update
         would follow a least disruptive approach. UPDATE_MODE must be (only one
diff --git a/gcloud/alpha/billing/accounts/add-iam-policy-binding b/gcloud/alpha/billing/accounts/add-iam-policy-binding
index df1f0817b..cac3e337f 100644
--- a/gcloud/alpha/billing/accounts/add-iam-policy-binding
+++ b/gcloud/alpha/billing/accounts/add-iam-policy-binding
@@ -67,7 +67,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud billing accounts add-iam-policy-binding
 
         $ gcloud beta billing accounts add-iam-policy-binding
 
diff --git a/gcloud/alpha/billing/accounts/describe b/gcloud/alpha/billing/accounts/describe
index 02671b695..46bf24eb9 100644
--- a/gcloud/alpha/billing/accounts/describe
+++ b/gcloud/alpha/billing/accounts/describe
@@ -21,7 +21,7 @@ EXAMPLES
 POSITIONAL ARGUMENTS
      ACCOUNT_ID
         Specify a billing account ID. Billing account IDs are of the form
-        0X0X0X-0X0X0X-0X0X0X. To see available IDs, run $ gcloud alpha billing
+        0X0X0X-0X0X0X-0X0X0X. To see available IDs, run $ gcloud billing
         accounts list.
 
 GCLOUD WIDE FLAGS
@@ -40,7 +40,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud billing accounts describe
 
         $ gcloud beta billing accounts describe
 
diff --git a/gcloud/alpha/billing/accounts/get-iam-policy b/gcloud/alpha/billing/accounts/get-iam-policy
index 3c3111178..d6ba2afc3 100644
--- a/gcloud/alpha/billing/accounts/get-iam-policy
+++ b/gcloud/alpha/billing/accounts/get-iam-policy
@@ -74,7 +74,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud billing accounts get-iam-policy
 
         $ gcloud beta billing accounts get-iam-policy
 
diff --git a/gcloud/alpha/billing/accounts/help b/gcloud/alpha/billing/accounts/help
index dd008d137..6c30e85a7 100644
--- a/gcloud/alpha/billing/accounts/help
+++ b/gcloud/alpha/billing/accounts/help
@@ -44,7 +44,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud billing accounts
 
         $ gcloud beta billing accounts
 
diff --git a/gcloud/alpha/billing/accounts/list b/gcloud/alpha/billing/accounts/list
index 2fd1185e2..1329f8793 100644
--- a/gcloud/alpha/billing/accounts/list
+++ b/gcloud/alpha/billing/accounts/list
@@ -64,7 +64,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud billing accounts list
 
         $ gcloud beta billing accounts list
 
diff --git a/gcloud/alpha/billing/accounts/projects/describe b/gcloud/alpha/billing/accounts/projects/describe
index e85cb69cb..a5c10689d 100644
--- a/gcloud/alpha/billing/accounts/projects/describe
+++ b/gcloud/alpha/billing/accounts/projects/describe
@@ -7,9 +7,9 @@ SYNOPSIS
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (ALPHA) (DEPRECATED) The gcloud <alpha|beta> billing accounts projects
-    groups have been moved to gcloud beta billing projects. Please use the new,
-    shorter commands instead.
+    (ALPHA) (DEPRECATED) The gcloud alpha billing accounts projects group has
+    been moved to gcloud billing projects. Please use the new, shorter commands
+    instead.
 
     This command shows billing info for a project, given its ID.
 
diff --git a/gcloud/alpha/billing/accounts/projects/help b/gcloud/alpha/billing/accounts/projects/help
index f77cbeff4..d652db97c 100644
--- a/gcloud/alpha/billing/accounts/projects/help
+++ b/gcloud/alpha/billing/accounts/projects/help
@@ -9,8 +9,8 @@ DESCRIPTION
     (ALPHA) (DEPRECATED) Manage the billing account configuration of your
     projects.
 
-    The gcloud <alpha|beta> billing accounts projects groups have been moved to
-    gcloud beta billing projects. Please use the new, shorter commands instead.
+    The gcloud alpha billing accounts projects group has been moved to gcloud
+    billing projects. Please use the new, shorter commands instead.
 
 GCLOUD WIDE FLAGS
     These flags are available to all commands: --help.
diff --git a/gcloud/alpha/billing/accounts/projects/link b/gcloud/alpha/billing/accounts/projects/link
index be46f585c..9a35982bb 100644
--- a/gcloud/alpha/billing/accounts/projects/link
+++ b/gcloud/alpha/billing/accounts/projects/link
@@ -8,9 +8,9 @@ SYNOPSIS
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (ALPHA) (DEPRECATED) The gcloud <alpha|beta> billing accounts projects
-    groups have been moved to gcloud beta billing projects. Please use the new,
-    shorter commands instead.
+    (ALPHA) (DEPRECATED) The gcloud alpha billing accounts projects group has
+    been moved to gcloud billing projects. Please use the new, shorter commands
+    instead.
 
     This command links a billing account to a project.
 
@@ -34,14 +34,14 @@ REQUIRED FLAGS
        --account-id=ACCOUNT_ID
           (DEPRECATED) Specify a billing account ID. Billing account IDs are of
           the form 0X0X0X-0X0X0X-0X0X0X. To see available IDs, run $ gcloud
-          alpha billing accounts list.
+          billing accounts list.
 
           The --account-id flag has been renamed --billing-account.
 
        --billing-account=ACCOUNT_ID
           Specify a billing account ID. Billing account IDs are of the form
-          0X0X0X-0X0X0X-0X0X0X. To see available IDs, run $ gcloud alpha
-          billing accounts list.
+          0X0X0X-0X0X0X-0X0X0X. To see available IDs, run $ gcloud billing
+          accounts list.
 
 GCLOUD WIDE FLAGS
     These flags are available to all commands: --access-token-file, --account,
diff --git a/gcloud/alpha/billing/accounts/projects/list b/gcloud/alpha/billing/accounts/projects/list
index c77843d91..2bf3b67f7 100644
--- a/gcloud/alpha/billing/accounts/projects/list
+++ b/gcloud/alpha/billing/accounts/projects/list
@@ -12,8 +12,8 @@ DESCRIPTION
     (ALPHA) (DEPRECATED) List all active projects associated with the specified
     billing account.
 
-    The gcloud <alpha|beta> billing accounts projects groups have been moved to
-    gcloud beta billing projects. Please use the new, shorter commands instead.
+    The gcloud alpha billing accounts projects group has been moved to gcloud
+    billing projects. Please use the new, shorter commands instead.
 
     gcloud alpha billing accounts projects list ACCOUNT_ID -- lists all active
     projects, for the specified billing account id.
@@ -29,14 +29,14 @@ POSITIONAL ARGUMENTS
        [ACCOUNT_ID]
           (DEPRECATED) Specify a billing account ID. Billing account IDs are of
           the form 0X0X0X-0X0X0X-0X0X0X. To see available IDs, run $ gcloud
-          alpha billing accounts list.
+          billing accounts list.
 
           The ACCOUNT_ID argument has been renamed --billing-account.
 
        --billing-account=ACCOUNT_ID
           Specify a billing account ID. Billing account IDs are of the form
-          0X0X0X-0X0X0X-0X0X0X. To see available IDs, run $ gcloud alpha
-          billing accounts list.
+          0X0X0X-0X0X0X-0X0X0X. To see available IDs, run $ gcloud billing
+          accounts list.
 
 LIST COMMAND FLAGS
      --filter=EXPRESSION
diff --git a/gcloud/alpha/billing/accounts/projects/unlink b/gcloud/alpha/billing/accounts/projects/unlink
index dbbee355a..a6980796e 100644
--- a/gcloud/alpha/billing/accounts/projects/unlink
+++ b/gcloud/alpha/billing/accounts/projects/unlink
@@ -7,9 +7,9 @@ SYNOPSIS
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (ALPHA) (DEPRECATED) The gcloud <alpha|beta> billing accounts projects
-    groups have been moved to gcloud beta billing projects. Please use the new,
-    shorter commands instead.
+    (ALPHA) (DEPRECATED) The gcloud alpha billing accounts projects group has
+    been moved to gcloud billing projects. Please use the new, shorter commands
+    instead.
 
     This command unlinks a project from its linked billing account. This
     disables billing on the project.
diff --git a/gcloud/alpha/billing/accounts/remove-iam-policy-binding b/gcloud/alpha/billing/accounts/remove-iam-policy-binding
index 88c8b881d..34cecc264 100644
--- a/gcloud/alpha/billing/accounts/remove-iam-policy-binding
+++ b/gcloud/alpha/billing/accounts/remove-iam-policy-binding
@@ -68,7 +68,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud billing accounts remove-iam-policy-binding
 
         $ gcloud beta billing accounts remove-iam-policy-binding
 
diff --git a/gcloud/alpha/billing/accounts/set-iam-policy b/gcloud/alpha/billing/accounts/set-iam-policy
index d3f9900b7..ad3a43ca1 100644
--- a/gcloud/alpha/billing/accounts/set-iam-policy
+++ b/gcloud/alpha/billing/accounts/set-iam-policy
@@ -59,7 +59,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud billing accounts set-iam-policy
 
         $ gcloud beta billing accounts set-iam-policy
 
diff --git a/gcloud/alpha/billing/budgets/create b/gcloud/alpha/billing/budgets/create
index 5a7b27cce..4046874ba 100644
--- a/gcloud/alpha/billing/budgets/create
+++ b/gcloud/alpha/billing/budgets/create
@@ -10,11 +10,11 @@ SYNOPSIS
         [--credit-types-treatment=CREDIT_TYPES_TREATMENT]
         [--disable-default-iam-recipients]
         [--filter-credit-types=[FILTER_CREDIT_TYPES,...]]
-        [--filter-labels=FILTER_LABELS]
+        [--filter-labels=[KEY=VALUE,...]]
         [--filter-projects=[FILTER_PROJECTS,...]]
         [--filter-services=[FILTER_SERVICES,...]]
         [--filter-subaccounts=[FILTER_SUBACCOUNTS,...]]
-        [--threshold-rule=THRESHOLD_RULE]
+        [--threshold-rule=[basis=BASIS],[percent=PERCENT]]
         [--calendar-period=CALENDAR_PERIOD
           | [--start-date=START_DATE : --end-date=END_DATE]]
         [GCLOUD_WIDE_FLAG ...]
@@ -97,7 +97,7 @@ OPTIONAL FLAGS
         specified, then --credit-types-treatment must be
         include-specified-credits.
 
-     --filter-labels=FILTER_LABELS
+     --filter-labels=[KEY=VALUE,...]
         Single label and value pair specifying that usage from only this set of
         labeled resources should be included in the budget. Currently, multiple
         entries or multiple values per entry are not allowed. If omitted, the
@@ -123,7 +123,7 @@ OPTIONAL FLAGS
         include usage from the parent account and all subaccounts, if they
         exist.
 
-     --threshold-rule=THRESHOLD_RULE
+     --threshold-rule=[basis=BASIS],[percent=PERCENT]
         Rule that triggers alerts (notifications of thresholds being crossed)
         when spend exceeds the specified percentages of the budget. This flag
         can be repeated to provide multiple thresholds above which an alert is
diff --git a/gcloud/alpha/billing/budgets/update b/gcloud/alpha/billing/budgets/update
index ce33fc900..16734f8ed 100644
--- a/gcloud/alpha/billing/budgets/update
+++ b/gcloud/alpha/billing/budgets/update
@@ -9,7 +9,7 @@ SYNOPSIS
         [--credit-types-treatment=CREDIT_TYPES_TREATMENT]
         [--disable-default-iam-recipients] [--display-name=DISPLAY_NAME]
         [--filter-credit-types=[FILTER_CREDIT_TYPES,...]]
-        [--filter-labels=FILTER_LABELS]
+        [--filter-labels=[KEY=VALUE,...]]
         [--filter-projects=[FILTER_PROJECTS,...]]
         [--filter-services=[FILTER_SERVICES,...]]
         [--filter-subaccounts=[FILTER_SUBACCOUNTS,...]]
@@ -17,8 +17,8 @@ SYNOPSIS
         [--calendar-period=CALENDAR_PERIOD
           | [--start-date=START_DATE : --end-date=END_DATE]]
         [--threshold-rules-from-file=THRESHOLD_RULES_FROM_FILE
-          | --add-threshold-rule=ADD_THRESHOLD_RULE --clear-threshold-rules]
-        [GCLOUD_WIDE_FLAG ...]
+          | --add-threshold-rule=[basis=BASIS],[percent=PERCENT]
+          --clear-threshold-rules] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (ALPHA) Update a budget.
@@ -98,7 +98,7 @@ FLAGS
         specified, then --credit-types-treatment must be
         include-specified-credits.
 
-     --filter-labels=FILTER_LABELS
+     --filter-labels=[KEY=VALUE,...]
         Single label and value pair specifying that usage from only this set of
         labeled resources should be included in the budget. Currently, multiple
         entries or multiple values per entry are not allowed. If omitted, the
@@ -160,7 +160,7 @@ FLAGS
           in the file will replace the rules in the budget. This can be used to
           add or remove specific threshold rules.
 
-       --add-threshold-rule=ADD_THRESHOLD_RULE
+       --add-threshold-rule=[basis=BASIS],[percent=PERCENT]
           Rule that triggers alerts (notifications of thresholds being crossed)
           when spend exceeds the specified percentages of the budget. This flag
           can be repeated to provide multiple thresholds above which an alert
diff --git a/gcloud/alpha/billing/help b/gcloud/alpha/billing/help
index 4673e9a5c..18ddd5f3d 100644
--- a/gcloud/alpha/billing/help
+++ b/gcloud/alpha/billing/help
@@ -11,12 +11,12 @@ DESCRIPTION
 EXAMPLES
     To list billing accounts associated with the current user, run:
 
-        $ gcloud beta billing accounts list
+        $ gcloud alpha billing accounts list
 
     To link one of the billing accounts 0X0X0X-0X0X0X-0X0X0X with a project
     my-project, run:
 
-        $ gcloud beta billing projects link my-project \
+        $ gcloud alpha billing projects link my-project \
             --billing-account 0X0X0X-0X0X0X-0X0X0X
 
 GCLOUD WIDE FLAGS
diff --git a/gcloud/alpha/billing/projects/describe b/gcloud/alpha/billing/projects/describe
index 523e1747b..2077a6a8a 100644
--- a/gcloud/alpha/billing/projects/describe
+++ b/gcloud/alpha/billing/projects/describe
@@ -38,7 +38,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud billing projects describe
 
         $ gcloud beta billing projects describe
 
diff --git a/gcloud/alpha/billing/projects/help b/gcloud/alpha/billing/projects/help
index a8f1005d1..21a05fa6d 100644
--- a/gcloud/alpha/billing/projects/help
+++ b/gcloud/alpha/billing/projects/help
@@ -33,7 +33,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud billing projects
 
         $ gcloud beta billing projects
 
diff --git a/gcloud/alpha/billing/projects/link b/gcloud/alpha/billing/projects/link
index ed6e43c13..c89d48747 100644
--- a/gcloud/alpha/billing/projects/link
+++ b/gcloud/alpha/billing/projects/link
@@ -42,14 +42,14 @@ REQUIRED FLAGS
        --account-id=ACCOUNT_ID
           (DEPRECATED) Specify a billing account ID. Billing account IDs are of
           the form 0X0X0X-0X0X0X-0X0X0X. To see available IDs, run $ gcloud
-          alpha billing accounts list.
+          billing accounts list.
 
           The --account-id flag has been renamed --billing-account.
 
        --billing-account=ACCOUNT_ID
           Specify a billing account ID. Billing account IDs are of the form
-          0X0X0X-0X0X0X-0X0X0X. To see available IDs, run $ gcloud alpha
-          billing accounts list.
+          0X0X0X-0X0X0X-0X0X0X. To see available IDs, run $ gcloud billing
+          accounts list.
 
 GCLOUD WIDE FLAGS
     These flags are available to all commands: --access-token-file, --account,
@@ -67,7 +67,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud billing projects link
 
         $ gcloud beta billing projects link
 
diff --git a/gcloud/alpha/billing/projects/list b/gcloud/alpha/billing/projects/list
index 7e2ec1a8c..76f0d303e 100644
--- a/gcloud/alpha/billing/projects/list
+++ b/gcloud/alpha/billing/projects/list
@@ -23,14 +23,14 @@ POSITIONAL ARGUMENTS
        [ACCOUNT_ID]
           (DEPRECATED) Specify a billing account ID. Billing account IDs are of
           the form 0X0X0X-0X0X0X-0X0X0X. To see available IDs, run $ gcloud
-          alpha billing accounts list.
+          billing accounts list.
 
           The ACCOUNT_ID argument has been renamed --billing-account.
 
        --billing-account=ACCOUNT_ID
           Specify a billing account ID. Billing account IDs are of the form
-          0X0X0X-0X0X0X-0X0X0X. To see available IDs, run $ gcloud alpha
-          billing accounts list.
+          0X0X0X-0X0X0X-0X0X0X. To see available IDs, run $ gcloud billing
+          accounts list.
 
 LIST COMMAND FLAGS
      --filter=EXPRESSION
@@ -74,7 +74,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud billing projects list
 
         $ gcloud beta billing projects list
 
diff --git a/gcloud/alpha/billing/projects/unlink b/gcloud/alpha/billing/projects/unlink
index 0cfe19f78..61cb64182 100644
--- a/gcloud/alpha/billing/projects/unlink
+++ b/gcloud/alpha/billing/projects/unlink
@@ -40,7 +40,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud billing projects unlink
 
         $ gcloud beta billing projects unlink
 
diff --git a/gcloud/alpha/bq/tables/create b/gcloud/alpha/bq/tables/create
index 3089d64d2..92b4d6fed 100644
--- a/gcloud/alpha/bq/tables/create
+++ b/gcloud/alpha/bq/tables/create
@@ -4,7 +4,7 @@ NAME
 SYNOPSIS
     gcloud alpha bq tables create (TABLE : --dataset=DATASET)
         [--description=DESCRIPTION] [--expiration=EXPIRATION] [--overwrite]
-        [--schema=FIELD_NAME=FIELD_TYPE | --schema-file=SCHEMA_FILE
+        [--schema=[FIELD_NAME=FIELD_TYPE,...] | --schema-file=SCHEMA_FILE
           | [--view=VIEW : --use-legacy-sql]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -77,7 +77,7 @@ FLAGS
 
      At most one of these can be specified:
 
-       --schema=FIELD_NAME=FIELD_TYPE
+       --schema=[FIELD_NAME=FIELD_TYPE,...]
           A comma-separated list of entries of the form FIELD_NAME[=FIELD_TYPE]
           specifying field names and types for the table being created.
           FIELD_TYPE defaults to string if not present. Possible FIELD_TYPES
diff --git a/gcloud/alpha/bq/tables/update b/gcloud/alpha/bq/tables/update
index 71ec601a5..a39f0da2c 100644
--- a/gcloud/alpha/bq/tables/update
+++ b/gcloud/alpha/bq/tables/update
@@ -5,7 +5,7 @@ SYNOPSIS
     gcloud alpha bq tables update (TABLE : --dataset=DATASET)
         [--description=DESCRIPTION] [--expiration=EXPIRATION]
         [--relax-columns=[FIELD_NAME,...]]
-        [--add-columns=FIELD_NAME=FIELD_TYPE
+        [--add-columns=[FIELD_NAME=FIELD_TYPE,...]
           | --add-columns-file=ADD_COLUMNS_FILE] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -79,7 +79,7 @@ FLAGS
 
      At most one of these can be specified:
 
-       --add-columns=FIELD_NAME=FIELD_TYPE
+       --add-columns=[FIELD_NAME=FIELD_TYPE,...]
           A comma-separated list of entries of the form FIELD_NAME[=FIELD_TYPE]
           specifying field names and types for the columns being added to the
           table. FIELD_TYPE defaults to string if not present. Possible
diff --git a/gcloud/alpha/compute/future-reservations/cancel b/gcloud/alpha/compute/future-reservations/cancel
index f97ad2f6f..e44d9be49 100644
--- a/gcloud/alpha/compute/future-reservations/cancel
+++ b/gcloud/alpha/compute/future-reservations/cancel
@@ -7,7 +7,7 @@ SYNOPSIS
         (FUTURE_RESERVATION : --zone=ZONE) [--async] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (ALPHA) Canel a Compute Engine future reservation.
+    (ALPHA) Cancel a Compute Engine future reservation.
 
 EXAMPLES
     To cancel a given Compute Engine future reservation, run:
@@ -69,5 +69,7 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist.
+    access allowlist. This variant is also available:
+
+        $ gcloud beta compute future-reservations cancel
 
diff --git a/gcloud/alpha/compute/future-reservations/create b/gcloud/alpha/compute/future-reservations/create
index 8612ca3fc..1cff3c732 100644
--- a/gcloud/alpha/compute/future-reservations/create
+++ b/gcloud/alpha/compute/future-reservations/create
@@ -59,7 +59,7 @@ REQUIRED FLAGS
         The total number of instances for which capacity assurance is requested
         at a future time period.
 
-     Manage the instance properties for the Specific SKU reservation. You must
+     Manage the instance properties for the auto-created reservations. You must
      either provide a source instance template or define the instance
      properties.
 
@@ -163,11 +163,12 @@ REQUIRED FLAGS
 
 OPTIONAL FLAGS
      --description=DESCRIPTION
-        An optional description of the reservation to create.
+        An optional description of the future reservation to create.
 
      --name-prefix=NAME_PREFIX
-        User provided name prefix for system generated reservations when
-        capacity is delivered at start time.
+        A name prefix for the auto-created reservations when capacity is
+        delivered at the start time. Each auto-created reservation name starts
+        with the name prefix.
 
      --planning-status=PLANNING_STATUS
         The planning status of the future reservation. The default value is
@@ -226,14 +227,13 @@ OPTIONAL FLAGS
 
        --share-setting=SHARE_SETTING
           Specify if this future reservation is shared, and if so, the type of
-          sharing. If you omit this flag, this value is local (not shared) by
-          default. SHARE_SETTING must be one of: local, projects.
+          sharing. If you omit this flag, this value is local by default.
+          SHARE_SETTING must be one of: local, projects.
 
        --share-with=PROJECT,[PROJECT,...]
-          If this future reservation is shared (--share-setting is not local),
-          provide a list of all of the specific projects that this future
-          reservation is shared with. List must contain project IDs or project
-          numbers.
+          If this future reservation is shared, provide a comma-separated list
+          of projects that this future reservation is shared with. The list
+          must contain project IDs or project numbers.
 
 GCLOUD WIDE FLAGS
     These flags are available to all commands: --access-token-file, --account,
@@ -247,5 +247,7 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist.
+    access allowlist. This variant is also available:
+
+        $ gcloud beta compute future-reservations create
 
diff --git a/gcloud/alpha/compute/future-reservations/delete b/gcloud/alpha/compute/future-reservations/delete
index 9710a661d..108d3fa6d 100644
--- a/gcloud/alpha/compute/future-reservations/delete
+++ b/gcloud/alpha/compute/future-reservations/delete
@@ -69,5 +69,7 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist.
+    access allowlist. This variant is also available:
+
+        $ gcloud beta compute future-reservations delete
 
diff --git a/gcloud/alpha/compute/future-reservations/describe b/gcloud/alpha/compute/future-reservations/describe
index d936a90a5..40039dda2 100644
--- a/gcloud/alpha/compute/future-reservations/describe
+++ b/gcloud/alpha/compute/future-reservations/describe
@@ -64,5 +64,7 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist.
+    access allowlist. This variant is also available:
+
+        $ gcloud beta compute future-reservations describe
 
diff --git a/gcloud/alpha/compute/future-reservations/help b/gcloud/alpha/compute/future-reservations/help
index e5bef4cc1..072f719be 100644
--- a/gcloud/alpha/compute/future-reservations/help
+++ b/gcloud/alpha/compute/future-reservations/help
@@ -38,5 +38,7 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist.
+    access allowlist. This variant is also available:
+
+        $ gcloud beta compute future-reservations
 
diff --git a/gcloud/alpha/compute/future-reservations/list b/gcloud/alpha/compute/future-reservations/list
index 26084cf7a..53e4cf08e 100644
--- a/gcloud/alpha/compute/future-reservations/list
+++ b/gcloud/alpha/compute/future-reservations/list
@@ -59,5 +59,7 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist.
+    access allowlist. This variant is also available:
+
+        $ gcloud beta compute future-reservations list
 
diff --git a/gcloud/alpha/compute/future-reservations/update b/gcloud/alpha/compute/future-reservations/update
index f297b6fdc..dd4db935e 100644
--- a/gcloud/alpha/compute/future-reservations/update
+++ b/gcloud/alpha/compute/future-reservations/update
@@ -44,7 +44,7 @@ FLAGS
         --no-auto-delete-auto-created-reservations to disable.
 
      --description=DESCRIPTION
-        An optional description of the reservation to create.
+        An optional description of the future reservation to create.
 
      --planning-status=PLANNING_STATUS
         The planning status of the future reservation. The default value is
@@ -111,8 +111,9 @@ FLAGS
           Clears the name prefix for the system generated reservations.
 
        --name-prefix=NAME_PREFIX
-          User provided name prefix for system generated reservations when
-          capacity is delivered at start time.
+          A name prefix for the auto-created reservations when capacity is
+          delivered at the start time. Each auto-created reservation name
+          starts with the name prefix.
 
      Manage the properties of a shared future reservation.
 
@@ -126,14 +127,13 @@ FLAGS
 
          --share-setting=SHARE_SETTING
             Specify if this future reservation is shared, and if so, the type
-            of sharing. If you omit this flag, this value is local (not shared)
-            by default. SHARE_SETTING must be one of: local, projects.
+            of sharing. If you omit this flag, this value is local by default.
+            SHARE_SETTING must be one of: local, projects.
 
          --share-with=PROJECT,[PROJECT,...]
-            If this future reservation is shared (--share-setting is not
-            local), provide a list of all of the specific projects that this
-            future reservation is shared with. List must contain project IDs or
-            project numbers.
+            If this future reservation is shared, provide a comma-separated
+            list of projects that this future reservation is shared with. The
+            list must contain project IDs or project numbers.
 
      Manage the specific SKU reservation properties.
 
@@ -238,5 +238,7 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist.
+    access allowlist. This variant is also available:
+
+        $ gcloud beta compute future-reservations update
 
diff --git a/gcloud/alpha/compute/instance-groups/managed/create b/gcloud/alpha/compute/instance-groups/managed/create
index 8b278dfeb..84dd7fa46 100644
--- a/gcloud/alpha/compute/instance-groups/managed/create
+++ b/gcloud/alpha/compute/instance-groups/managed/create
@@ -9,6 +9,8 @@ SYNOPSIS
         [--description=DESCRIPTION] [--[no-]force-update-on-repair]
         [--initial-delay=INITIAL_DELAY] [--instance-redistribution-type=TYPE]
         [--list-managed-instances-results=MODE]
+        [--standby-pool-initial-delay=STANDBY_POOL_INITIAL_DELAY]
+        [--standby-pool-mode=STANDBY_POOL_MODE]
         [--stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME]]
         [--stateful-external-ip=[enabled],
           [auto-delete=AUTO-DELETE],[interface-name=INTERFACE-NAME]]
@@ -140,6 +142,19 @@ OPTIONAL FLAGS
             Pagination is enabled for the group's listManagedInstances API
             method. maxResults and pageToken query parameters are respected.
 
+     --standby-pool-initial-delay=STANDBY_POOL_INITIAL_DELAY
+        Specifies the initialization delay for stopping/suspending instances.
+
+     --standby-pool-mode=STANDBY_POOL_MODE
+        Defines behaviour of using instances from standby pool to resize MIG.
+        STANDBY_POOL_MODE must be one of:
+
+         MANUAL
+            MIG does not automatically stop/start or suspend/resume VMs.
+         SCALE_OUT_POOL
+            MIG automatically resumes and starts VMs when it scales out, and
+            replenishes the standby pool afterwards.
+
      --stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME]
         Disks considered stateful by the instance group. Managed instance
         groups preserve and reattach stateful disks on VM autohealing, update,
diff --git a/gcloud/alpha/compute/instance-groups/managed/update b/gcloud/alpha/compute/instance-groups/managed/update
index 0ba6bffb2..626129781 100644
--- a/gcloud/alpha/compute/instance-groups/managed/update
+++ b/gcloud/alpha/compute/instance-groups/managed/update
@@ -11,6 +11,8 @@ SYNOPSIS
         [--remove-stateful-disks=DEVICE_NAME,[DEVICE_NAME,...]]
         [--remove-stateful-external-ips=INTERFACE_NAME,[...]]
         [--remove-stateful-internal-ips=INTERFACE_NAME,[...]]
+        [--standby-pool-initial-delay=STANDBY_POOL_INITIAL_DELAY]
+        [--standby-pool-mode=STANDBY_POOL_MODE]
         [--stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME]]
         [--stateful-external-ip=[enabled],
           [auto-delete=AUTO-DELETE],[interface-name=INTERFACE-NAME]]
@@ -130,6 +132,19 @@ FLAGS
         Remove stateful configuration for the specified interfaces for internal
         IPs.
 
+     --standby-pool-initial-delay=STANDBY_POOL_INITIAL_DELAY
+        Specifies the initialization delay for stopping/suspending instances.
+
+     --standby-pool-mode=STANDBY_POOL_MODE
+        Defines behaviour of using instances from standby pool to resize MIG.
+        STANDBY_POOL_MODE must be one of:
+
+         MANUAL
+            MIG does not automatically stop/start or suspend/resume VMs.
+         SCALE_OUT_POOL
+            MIG automatically resumes and starts VMs when it scales out, and
+            replenishes the standby pool afterwards.
+
      --stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME]
         Disks considered stateful by the instance group. Managed instance
         groups preserve and reattach stateful disks on VM autohealing, update,
diff --git a/gcloud/alpha/compute/routers/get-nat-ip-info b/gcloud/alpha/compute/routers/get-nat-ip-info
index f0c02fccb..868b284e4 100644
--- a/gcloud/alpha/compute/routers/get-nat-ip-info
+++ b/gcloud/alpha/compute/routers/get-nat-ip-info
@@ -65,5 +65,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist.
+    access allowlist. These variants are also available:
+
+        $ gcloud compute routers get-nat-ip-info
+
+        $ gcloud beta compute routers get-nat-ip-info
 
diff --git a/gcloud/alpha/compute/tpus/queued-resources/create b/gcloud/alpha/compute/tpus/queued-resources/create
index 2f22db0c6..481c2484b 100644
--- a/gcloud/alpha/compute/tpus/queued-resources/create
+++ b/gcloud/alpha/compute/tpus/queued-resources/create
@@ -8,10 +8,10 @@ SYNOPSIS
         (--accelerator-type=ACCELERATOR_TYPE | --topology=TOPOLOGY --type=TYPE)
         (--node-id=NODE_ID
           | [--node-count=NODE_COUNT : --node-prefix=NODE_PREFIX]) [--async]
-        [--best-effort] [--data-disk=DATA_DISK] [--description=DESCRIPTION]
-        [--guaranteed] [--internal-ips] [--labels=[LABELS,...]]
-        [--metadata=[METADATA,...]]
-        [--metadata-from-file=[METADATA_FROM_FILE,...]]
+        [--best-effort] [--data-disk=[mode=MODE],[source=SOURCE]]
+        [--description=DESCRIPTION] [--guaranteed] [--internal-ips]
+        [--labels=[KEY=VALUE,...]] [--metadata=[KEY=VALUE,...]]
+        [--metadata-from-file=[KEY=VALUE,...]]
         [--network=NETWORK; default="default"] [--range=RANGE]
         [--reservation-host-folder=RESERVATION_HOST_FOLDER]
         [--reservation-host-organization=RESERVATION_HOST_ORGANIZATION]
@@ -145,7 +145,7 @@ OPTIONAL FLAGS
         If provided, the Node requested here may be scheduled at the 'best
         effort' tier.
 
-     --data-disk=DATA_DISK
+     --data-disk=[mode=MODE],[source=SOURCE]
         Additional data disks for the TPU VM.
 
         This flag must be repeated to provide multiple data disks. For example:
@@ -178,15 +178,15 @@ OPTIONAL FLAGS
         default is that external IP addresses will be associated with the TPU
         workers.
 
-     --labels=[LABELS,...]
+     --labels=[KEY=VALUE,...]
         Resource labels to represent user-provided metadata. See
         https://cloud.google.com/compute/docs/labeling-resources for details.
 
-     --metadata=[METADATA,...]
+     --metadata=[KEY=VALUE,...]
         List of comma-separated metadata key-value pairs for the Cloud TPU VM
         node. Example: --metadata='key1=value1,key2=value2'
 
-     --metadata-from-file=[METADATA_FROM_FILE,...]
+     --metadata-from-file=[KEY=VALUE,...]
         Same as --metadata except the value for the entry will be read from a
         local file. Example: --metadata-from-file='key1=value1.txt'
 
diff --git a/gcloud/alpha/compute/tpus/tpu-vm/create b/gcloud/alpha/compute/tpus/tpu-vm/create
index 2f82c5cd9..c17b97330 100644
--- a/gcloud/alpha/compute/tpus/tpu-vm/create
+++ b/gcloud/alpha/compute/tpus/tpu-vm/create
@@ -3,10 +3,10 @@ NAME
 
 SYNOPSIS
     gcloud alpha compute tpus tpu-vm create (TPU : --zone=ZONE)
-        --version=VERSION [--async] [--boot-disk=[BOOT_DISK,...]]
-        [--data-disk=DATA_DISK] [--description=DESCRIPTION] [--internal-ips]
-        [--labels=[LABELS,...]] [--metadata=[METADATA,...]]
-        [--metadata-from-file=[METADATA_FROM_FILE,...]]
+        --version=VERSION [--async] [--boot-disk=[KEY=VALUE,...]]
+        [--data-disk=[mode=MODE],[source=SOURCE]] [--description=DESCRIPTION]
+        [--internal-ips] [--labels=[KEY=VALUE,...]]
+        [--metadata=[KEY=VALUE,...]] [--metadata-from-file=[KEY=VALUE,...]]
         [--network=NETWORK; default="default"] [--preemptible] [--range=RANGE]
         [--reserved] [--scopes=[SCOPES,...]]
         [--service-account=SERVICE_ACCOUNT] [--shielded-secure-boot] [--spot]
@@ -82,7 +82,7 @@ OPTIONAL FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
-     --boot-disk=[BOOT_DISK,...]
+     --boot-disk=[KEY=VALUE,...]
         Specifies if the boot disk should be created in confidential-compute
         mode.
 
@@ -100,7 +100,7 @@ OPTIONAL FLAGS
             used to protect the disk. KMS cryptokey name format:
             projects/<kms-project>/locations/<kms-location>/keyRings/<kms-keyring>/cryptoKeys/<key-name>
 
-     --data-disk=DATA_DISK
+     --data-disk=[mode=MODE],[source=SOURCE]
         Additional data disks for the TPU VM.
 
         This flag must be repeated to provide multiple data disks. For example:
@@ -129,15 +129,15 @@ OPTIONAL FLAGS
         default is that external IP addresses will be associated with the TPU
         workers.
 
-     --labels=[LABELS,...]
+     --labels=[KEY=VALUE,...]
         Resource labels to represent user-provided metadata. See
         https://cloud.google.com/compute/docs/labeling-resources for details.
 
-     --metadata=[METADATA,...]
+     --metadata=[KEY=VALUE,...]
         List of comma-separated metadata key-value pairs for the Cloud TPU VM
         node. Example: --metadata='key1=value1,key2=value2'
 
-     --metadata-from-file=[METADATA_FROM_FILE,...]
+     --metadata-from-file=[KEY=VALUE,...]
         Same as --metadata except the value for the entry will be read from a
         local file. Example: --metadata-from-file='key1=value1.txt'
 
diff --git a/gcloud/alpha/compute/tpus/tpu-vm/update b/gcloud/alpha/compute/tpus/tpu-vm/update
index ee9b67550..4ba9fc397 100644
--- a/gcloud/alpha/compute/tpus/tpu-vm/update
+++ b/gcloud/alpha/compute/tpus/tpu-vm/update
@@ -8,7 +8,7 @@ SYNOPSIS
         [--attach-disk=[SOURCE=DATA_DISK,...] | --detach-disk=DATA_DISK]
         [--clear-labels | --remove-labels=[KEY,...]]
         [--clear-tags | --remove-tags=[TAG,...]]
-        [--metadata-from-file=[METADATA_FROM_FILE,...]
+        [--metadata-from-file=[KEY=VALUE,...]
           | --update-metadata=[KEY=VALUE,...] --clear-metadata
           | --remove-metadata=[KEY,...]] [GCLOUD_WIDE_FLAG ...]
 
@@ -176,7 +176,7 @@ FLAGS
 
      At most one of these can be specified:
 
-       --metadata-from-file=[METADATA_FROM_FILE,...]
+       --metadata-from-file=[KEY=VALUE,...]
           Same as --metadata except the value for the entry will be read from a
           local file. Example: --metadata-from-file='key1=value1.txt'
 
diff --git a/gcloud/alpha/container/aws/node-pools/create b/gcloud/alpha/container/aws/node-pools/create
index e0f5de283..d1bf012d0 100644
--- a/gcloud/alpha/container/aws/node-pools/create
+++ b/gcloud/alpha/container/aws/node-pools/create
@@ -142,7 +142,7 @@ OPTIONAL FLAGS
         default, host.
 
      --node-labels=NODE_LABEL,[NODE_LABEL,...]
-        Labels assigned to nodes of the node pool.
+        Labels assigned to the node pool's nodes.
 
      --node-taints=NODE_TAINT,[NODE_TAINT,...]
         Taints assigned to nodes of the node pool. Node taint is of format
diff --git a/gcloud/alpha/container/aws/node-pools/update b/gcloud/alpha/container/aws/node-pools/update
index 33eca3e8c..b611ce25d 100644
--- a/gcloud/alpha/container/aws/node-pools/update
+++ b/gcloud/alpha/container/aws/node-pools/update
@@ -16,6 +16,7 @@ SYNOPSIS
         [--clear-autoscaling-metrics
           | --autoscaling-metrics=[AUTOSCALING_METRIC,...]
           --autoscaling-metrics-granularity=AUTOSCALING_METRICS_GRANULARITY]
+        [--clear-node-labels | --node-labels=NODE_LABEL,[NODE_LABEL,...]]
         [--clear-proxy-config | --proxy-secret-arn=PROXY_SECRET_ARN
           --proxy-secret-version-id=PROXY_SECRET_VERSION_ID]
         [--clear-security-group-ids
@@ -148,6 +149,16 @@ FLAGS
             Frequency at which EC2 Auto Scaling sends aggregated data to AWS
             CloudWatch. The only valid value is "1Minute".
 
+     Node labels
+
+     At most one of these can be specified:
+
+       --clear-node-labels
+          Clear the labels assigned to the node pool's nodes.
+
+       --node-labels=NODE_LABEL,[NODE_LABEL,...]
+          Labels assigned to the node pool's nodes.
+
      Proxy config
 
      At most one of these can be specified:
diff --git a/gcloud/alpha/container/azure/node-pools/create b/gcloud/alpha/container/azure/node-pools/create
index 304784db4..34f82a5bc 100644
--- a/gcloud/alpha/container/azure/node-pools/create
+++ b/gcloud/alpha/container/azure/node-pools/create
@@ -136,7 +136,7 @@ OPTIONAL FLAGS
             $ gcloud alpha container azure node-pools create --image-type=ubuntu
 
      --node-labels=NODE_LABEL,[NODE_LABEL,...]
-        Labels assigned to nodes of the node pool.
+        Labels assigned to the node pool's nodes.
 
      --node-taints=NODE_TAINT,[NODE_TAINT,...]
         Taints assigned to nodes of the node pool. Node taint is of format
diff --git a/gcloud/alpha/container/bare-metal/admin-clusters/create b/gcloud/alpha/container/bare-metal/admin-clusters/create
index 0d6fbf10c..036f381fd 100644
--- a/gcloud/alpha/container/bare-metal/admin-clusters/create
+++ b/gcloud/alpha/container/bare-metal/admin-clusters/create
@@ -16,6 +16,7 @@ SYNOPSIS
         ((--lvp-node-mounts-config-path=LVP_NODE_MOUNTS_CONFIG_PATH
           --lvp-node-mounts-config-storage-class=LVP_NODE_MOUNTS_CONFIG_STORAGE_CLASS) ((--lvp-share-path=LVP_SHARE_PATH --lvp-share-storage-class=LVP_SHARE_STORAGE_CLASS) : --shared-path-pv-count=SHARED_PATH_PV_COUNT))
         [--admin-users=ADMIN_USERS] [--annotations=[KEY=VALUE,...]] [--async]
+        [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE]
         [--description=DESCRIPTION] [--enable-application-logs]
         [--login-user=LOGIN_USER]
         [--maintenance-address-cidr-blocks=[MAINTENANCE_ADDRESS_CIDR_BLOCKS,
@@ -200,6 +201,11 @@ OPTIONAL FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
+     --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE
+        Set Binary Authorization evaluation mode for this cluster.
+        BINAUTHZ_EVALUATION_MODE must be one of: DISABLED,
+        PROJECT_SINGLETON_POLICY_ENFORCE.
+
      --description=DESCRIPTION
         Description for the resource.
 
diff --git a/gcloud/alpha/container/bare-metal/admin-clusters/update b/gcloud/alpha/container/bare-metal/admin-clusters/update
index 660f01889..f1e9aba40 100644
--- a/gcloud/alpha/container/bare-metal/admin-clusters/update
+++ b/gcloud/alpha/container/bare-metal/admin-clusters/update
@@ -5,6 +5,7 @@ NAME
 SYNOPSIS
     gcloud alpha container bare-metal admin-clusters update
         (ADMIN_CLUSTER : --location=LOCATION) [--async]
+        [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE]
         [--description=DESCRIPTION] [--enable-application-logs]
         [--island-mode-service-address-cidr-blocks=SERVICE_ADDRESS,[...]]
         [--login-user=LOGIN_USER]
@@ -64,6 +65,11 @@ FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
+     --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE
+        Set Binary Authorization evaluation mode for this cluster.
+        BINAUTHZ_EVALUATION_MODE must be one of: DISABLED,
+        PROJECT_SINGLETON_POLICY_ENFORCE.
+
      --description=DESCRIPTION
         Description for the resource.
 
diff --git a/gcloud/alpha/container/bare-metal/clusters/create b/gcloud/alpha/container/bare-metal/clusters/create
index ffe8d3087..6fd5e7a71 100644
--- a/gcloud/alpha/container/bare-metal/clusters/create
+++ b/gcloud/alpha/container/bare-metal/clusters/create
@@ -39,6 +39,7 @@ SYNOPSIS
         ((--lvp-node-mounts-config-path=LVP_NODE_MOUNTS_CONFIG_PATH
           --lvp-node-mounts-config-storage-class=LVP_NODE_MOUNTS_CONFIG_STORAGE_CLASS) ((--lvp-share-path=LVP_SHARE_PATH --lvp-share-storage-class=LVP_SHARE_STORAGE_CLASS) : --shared-path-pv-count=SHARED_PATH_PV_COUNT))
         [--admin-users=ADMIN_USERS] [--annotations=[KEY=VALUE,...]] [--async]
+        [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE]
         [--description=DESCRIPTION] [--enable-application-logs]
         [--login-user=LOGIN_USER]
         [--maintenance-address-cidr-blocks=[MAINTENANCE_ADDRESS_CIDR_BLOCKS,
@@ -420,6 +421,11 @@ OPTIONAL FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
+     --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE
+        Set Binary Authorization evaluation mode for this cluster.
+        BINAUTHZ_EVALUATION_MODE must be one of: DISABLED,
+        PROJECT_SINGLETON_POLICY_ENFORCE.
+
      --description=DESCRIPTION
         Description for the resource.
 
diff --git a/gcloud/alpha/container/bare-metal/clusters/update b/gcloud/alpha/container/bare-metal/clusters/update
index 8f9c9841a..2198b0fae 100644
--- a/gcloud/alpha/container/bare-metal/clusters/update
+++ b/gcloud/alpha/container/bare-metal/clusters/update
@@ -5,8 +5,10 @@ NAME
 SYNOPSIS
     gcloud alpha container bare-metal clusters update
         (CLUSTER : --location=LOCATION) [--admin-users=ADMIN_USERS]
-        [--allow-missing] [--async] [--description=DESCRIPTION]
-        [--enable-application-logs] [--login-user=LOGIN_USER]
+        [--allow-missing] [--async]
+        [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE]
+        [--description=DESCRIPTION] [--enable-application-logs]
+        [--login-user=LOGIN_USER]
         [--maintenance-address-cidr-blocks=[MAINTENANCE_ADDRESS_CIDR_BLOCKS,
           ...]] [--upgrade-control-plane=UPGRADE_CONTROL_PLANE]
         [--validate-only] [--version=VERSION]
@@ -101,6 +103,11 @@ FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
+     --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE
+        Set Binary Authorization evaluation mode for this cluster.
+        BINAUTHZ_EVALUATION_MODE must be one of: DISABLED,
+        PROJECT_SINGLETON_POLICY_ENFORCE.
+
      --description=DESCRIPTION
         Description for the resource.
 
diff --git a/gcloud/alpha/container/bare-metal/standalone-clusters/update b/gcloud/alpha/container/bare-metal/standalone-clusters/update
index e23ff13ed..103cecd5f 100644
--- a/gcloud/alpha/container/bare-metal/standalone-clusters/update
+++ b/gcloud/alpha/container/bare-metal/standalone-clusters/update
@@ -5,8 +5,10 @@ NAME
 SYNOPSIS
     gcloud alpha container bare-metal standalone-clusters update
         (STANDALONE_CLUSTER : --location=LOCATION) [--admin-users=ADMIN_USERS]
-        [--allow-missing] [--async] [--description=DESCRIPTION]
-        [--enable-application-logs] [--login-user=LOGIN_USER]
+        [--allow-missing] [--async]
+        [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE]
+        [--description=DESCRIPTION] [--enable-application-logs]
+        [--login-user=LOGIN_USER]
         [--maintenance-address-cidr-blocks=[MAINTENANCE_ADDRESS_CIDR_BLOCKS,
           ...]] [--validate-only] [--version=VERSION]
         [--add-annotations=[KEY1=VALUE1,KEY2=VALUE2,...]
@@ -96,6 +98,11 @@ FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
+     --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE
+        Set Binary Authorization evaluation mode for this cluster.
+        BINAUTHZ_EVALUATION_MODE must be one of: DISABLED,
+        PROJECT_SINGLETON_POLICY_ENFORCE.
+
      --description=DESCRIPTION
         Description for the resource.
 
diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create
index b24b335e7..15c1c10cb 100644
--- a/gcloud/alpha/container/clusters/create
+++ b/gcloud/alpha/container/clusters/create
@@ -848,7 +848,8 @@ FLAGS
      --monitoring=[COMPONENT,...]
         Set the components that have monitoring enabled. Valid component values
         are: SYSTEM, WORKLOAD (Deprecated), NONE, API_SERVER,
-        CONTROLLER_MANAGER, SCHEDULER
+        CONTROLLER_MANAGER, SCHEDULER, DAEMONSET, DEPLOYMENT, HPA, POD,
+        STATEFULSET, STORAGE
 
         For more information, see
         https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics
@@ -856,7 +857,7 @@ FLAGS
         Examples:
 
             $ gcloud alpha container clusters create \
-                --monitoring=SYSTEM,API_SERVER
+                --monitoring=SYSTEM,API_SERVER,POD
             $ gcloud alpha container clusters create --monitoring=NONE
 
      --network=NETWORK
diff --git a/gcloud/alpha/container/clusters/create-auto b/gcloud/alpha/container/clusters/create-auto
index 63b6522da..d4dd754b2 100644
--- a/gcloud/alpha/container/clusters/create-auto
+++ b/gcloud/alpha/container/clusters/create-auto
@@ -231,7 +231,8 @@ FLAGS
      --monitoring=[COMPONENT,...]
         Set the components that have monitoring enabled. Valid component values
         are: SYSTEM, WORKLOAD (Deprecated), NONE, API_SERVER,
-        CONTROLLER_MANAGER, SCHEDULER
+        CONTROLLER_MANAGER, SCHEDULER, DAEMONSET, DEPLOYMENT, HPA, POD,
+        STATEFULSET, STORAGE
 
         For more information, see
         https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics
@@ -239,7 +240,7 @@ FLAGS
         Examples:
 
             $ gcloud alpha container clusters create-auto \
-                --monitoring=SYSTEM,API_SERVER
+                --monitoring=SYSTEM,API_SERVER,POD
             $ gcloud alpha container clusters create-auto --monitoring=NONE
 
      --network=NETWORK
diff --git a/gcloud/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update
index 84e0c3173..79e5a4d04 100644
--- a/gcloud/alpha/container/clusters/update
+++ b/gcloud/alpha/container/clusters/update
@@ -1219,7 +1219,8 @@ REQUIRED FLAGS
        --monitoring=[COMPONENT,...]
           Set the components that have monitoring enabled. Valid component
           values are: SYSTEM, WORKLOAD (Deprecated), NONE, API_SERVER,
-          CONTROLLER_MANAGER, SCHEDULER
+          CONTROLLER_MANAGER, SCHEDULER, DAEMONSET, DEPLOYMENT, HPA, POD,
+          STATEFULSET, STORAGE
 
           For more information, see
           https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics
@@ -1227,7 +1228,7 @@ REQUIRED FLAGS
           Examples:
 
               $ gcloud alpha container clusters update \
-                  --monitoring=SYSTEM,API_SERVER
+                  --monitoring=SYSTEM,API_SERVER,POD
               $ gcloud alpha container clusters update --monitoring=NONE
 
        At most one of these can be specified:
diff --git a/gcloud/alpha/container/fleet/clusterupgrade/create b/gcloud/alpha/container/fleet/clusterupgrade/create
new file mode 100644
index 000000000..555683682
--- /dev/null
+++ b/gcloud/alpha/container/fleet/clusterupgrade/create
@@ -0,0 +1,87 @@
+NAME
+    gcloud alpha container fleet clusterupgrade create - create the
+        clusterupgrade feature for a fleet within a given project
+
+SYNOPSIS
+    gcloud alpha container fleet clusterupgrade create
+        [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING]
+        [--upstream-fleet=UPSTREAM_FLEET]
+        [--add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE
+          --upgrade-selector=[name=NAME],[version=VERSION]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) Create the clusterupgrade feature for a fleet within a given
+    project.
+
+FLAGS
+     --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING
+        Configures the default soaking duration for each upgrade propagating
+        through the current fleet to become "COMPLETE". Soaking begins after
+        all clusters in the fleet are on the target version, or after 30 days
+        if all cluster upgrades are not complete. Once an upgrade state becomes
+        "COMPLETE", it will automatically be propagated to the downstream
+        fleet. Max is 30 days.
+
+        To configure Rollout Sequencing for a fleet, this attribute must be
+        set. To do this while specifying a default soaking duration of 7 days,
+        run:
+
+            $ gcloud alpha container fleet clusterupgrade create \
+                --default-upgrade-soaking=7d
+
+     --upstream-fleet=UPSTREAM_FLEET
+        The upstream fleet. GKE will finish upgrades on the upstream fleet
+        before applying the same upgrades to the current fleet.
+
+        To configure the upstream fleet, run:
+
+            $ gcloud alpha container fleet clusterupgrade create             \
+                --upstream-fleet={upstream_fleet}
+
+     Upgrade soaking override.
+
+         Defines a specific soaking time override for a particular upgrade
+         propagating through the current fleet that supercedes the default
+         soaking duration configured by `--default-upgrade-soaking`.
+
+         To set an upgrade soaking override of 12 hours for the upgrade with
+         name, `k8s_control_plane`, and version, `1.23.1-gke.1000`, run:
+
+         $ gcloud alpha container fleet clusterupgrade create               \
+         --add-upgrade-soaking-override=12h               \
+         --upgrade-selector=name="k8s_control_plane",\
+         version="1.23.1-gke.1000"
+
+       --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE
+          Overrides the soaking time for a particular upgrade name and version
+          propagating through the current fleet. Set soaking to 0 days to
+          bypass soaking and fast-forward the upgrade to the downstream fleet.
+
+          See $ gcloud topic datetimes for information on duration formats.
+
+          This flag argument must be specified if any of the other arguments in
+          this group are specified.
+
+       --upgrade-selector=[name=NAME],[version=VERSION]
+          Name and version of the upgrade to be overridden where version is a
+          full GKE version. Currently, name can be either k8s_control_plane or
+          k8s_node.
+
+          This flag argument must be specified if any of the other arguments in
+          this group are specified.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist.
+
diff --git a/gcloud/alpha/container/fleet/clusterupgrade/describe b/gcloud/alpha/container/fleet/clusterupgrade/describe
new file mode 100644
index 000000000..32774b007
--- /dev/null
+++ b/gcloud/alpha/container/fleet/clusterupgrade/describe
@@ -0,0 +1,46 @@
+NAME
+    gcloud alpha container fleet clusterupgrade describe - describe the
+        clusterupgrade feature for a fleet within a given project
+
+SYNOPSIS
+    gcloud alpha container fleet clusterupgrade describe
+        [--show-linked-cluster-upgrade] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) Describe the Fleet clusterupgrade feature used for configuring
+    fleet-based rollout sequencing.
+
+EXAMPLES
+    To view the cluster upgrade feature information for the current fleet, run:
+
+        $ gcloud alpha container fleet clusterupgrade describe
+
+FLAGS
+     --show-linked-cluster-upgrade
+        Shows the cluster upgrade feature information for the current fleet as
+        well as information for all other fleets linked in the same rollout
+        sequence (provided that the caller has permission to view the upstream
+        and downstream fleets). This displays cluster upgrade information for
+        fleets in the current fleet's rollout sequence in order of furthest
+        upstream to downstream.
+
+        To view the cluster upgrade feature information for the rollout
+        sequence containing the current fleet, run:
+
+            $ gcloud alpha container fleet clusterupgrade describe \
+                --show-linked-cluster-upgrade
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist.
+
diff --git a/gcloud/alpha/container/fleet/clusterupgrade/help b/gcloud/alpha/container/fleet/clusterupgrade/help
new file mode 100644
index 000000000..cbaea02e7
--- /dev/null
+++ b/gcloud/alpha/container/fleet/clusterupgrade/help
@@ -0,0 +1,37 @@
+NAME
+    gcloud alpha container fleet clusterupgrade - configure the Fleet
+        clusterupgrade feature
+
+SYNOPSIS
+    gcloud alpha container fleet clusterupgrade COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This fleet feature is used to configure fleet-based rollout
+    sequencing.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        (ALPHA) Create the clusterupgrade feature for a fleet within a given
+        project.
+
+     describe
+        (ALPHA) Describe the clusterupgrade feature for a fleet within a given
+        project.
+
+     update
+        (ALPHA) Update the clusterupgrade feature for a fleet within a given
+        project.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist.
+
diff --git a/gcloud/alpha/container/fleet/clusterupgrade/update b/gcloud/alpha/container/fleet/clusterupgrade/update
new file mode 100644
index 000000000..38af93cdf
--- /dev/null
+++ b/gcloud/alpha/container/fleet/clusterupgrade/update
@@ -0,0 +1,115 @@
+NAME
+    gcloud alpha container fleet clusterupgrade update - update the
+        clusterupgrade feature for a fleet within a given project
+
+SYNOPSIS
+    gcloud alpha container fleet clusterupgrade update
+        [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING]
+        [--remove-upgrade-soaking-overrides
+          | --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE
+          --upgrade-selector=[name=NAME],[version=VERSION]]
+        [--reset-upstream-fleet | --upstream-fleet=UPSTREAM_FLEET]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) Update the clusterupgrade feature for a fleet within a given
+    project.
+
+FLAGS
+     --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING
+        Configures the default soaking duration for each upgrade propagating
+        through the current fleet to become "COMPLETE". Soaking begins after
+        all clusters in the fleet are on the target version, or after 30 days
+        if all cluster upgrades are not complete. Once an upgrade state becomes
+        "COMPLETE", it will automatically be propagated to the downstream
+        fleet. Max is 30 days.
+
+        To configure Rollout Sequencing for a fleet, this attribute must be
+        set. To do this while specifying a default soaking duration of 7 days,
+        run:
+
+            $ gcloud alpha container fleet clusterupgrade update \
+                --default-upgrade-soaking=7d
+
+     At most one of these can be specified:
+
+       --remove-upgrade-soaking-overrides
+          Removes soaking time overrides for all upgrades propagating through
+          the current fleet. Consequently, all upgrades will follow the soak
+          time configured by --default-upgrade-soaking until new overrides are
+          configured with --add_upgrade_soaking_override and
+          --upgrade_selector.
+
+          To remove all configured soaking time overrides, run:
+
+              $ gcloud alpha container fleet clusterupgrade update \
+                  --remove-upgrade-soaking-overrides
+
+       Upgrade soaking override.
+
+           Defines a specific soaking time override for a particular upgrade
+           propagating through the current fleet that supercedes the default
+           soaking duration configured by `--default-upgrade-soaking`.
+
+           To set an upgrade soaking override of 12 hours for the upgrade with
+           name, `k8s_control_plane`, and version, `1.23.1-gke.1000`, run:
+
+           $ gcloud alpha container fleet clusterupgrade update               \
+           --add-upgrade-soaking-override=12h               \
+           --upgrade-selector=name="k8s_control_plane",\
+           version="1.23.1-gke.1000"
+
+         --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE
+            Overrides the soaking time for a particular upgrade name and
+            version propagating through the current fleet. Set soaking to 0
+            days to bypass soaking and fast-forward the upgrade to the
+            downstream fleet.
+
+            See $ gcloud topic datetimes for information on duration formats.
+
+            This flag argument must be specified if any of the other arguments
+            in this group are specified.
+
+         --upgrade-selector=[name=NAME],[version=VERSION]
+            Name and version of the upgrade to be overridden where version is a
+            full GKE version. Currently, name can be either k8s_control_plane
+            or k8s_node.
+
+            This flag argument must be specified if any of the other arguments
+            in this group are specified.
+
+     At most one of these can be specified:
+
+       --reset-upstream-fleet
+          Clears the relationship between the current fleet and its upstream
+          fleet in the rollout sequence.
+
+          To remove the link between the current fleet and its upstream fleet,
+          run:
+
+              $ gcloud alpha container fleet clusterupgrade update \
+                  --reset-upstream-fleet
+
+       --upstream-fleet=UPSTREAM_FLEET
+          The upstream fleet. GKE will finish upgrades on the upstream fleet
+          before applying the same upgrades to the current fleet.
+
+          To configure the upstream fleet, run:
+
+              $ gcloud alpha container fleet clusterupgrade update             \
+                  --upstream-fleet={upstream_fleet}
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist.
+
diff --git a/gcloud/alpha/container/fleet/create b/gcloud/alpha/container/fleet/create
new file mode 100644
index 000000000..cad03a207
--- /dev/null
+++ b/gcloud/alpha/container/fleet/create
@@ -0,0 +1,79 @@
+NAME
+    gcloud alpha container fleet create - create a fleet
+
+SYNOPSIS
+    gcloud alpha container fleet create [--async] [--display-name=DISPLAY_NAME]
+        [--labels=[KEY=VALUE,...]]
+        [--security-posture=SECURITY_POSTURE
+          --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project specified already has a fleet.
+      ▪ The active account does not have permission to access the given
+        project.
+
+EXAMPLES
+    To create a fleet in project example-foo-bar-1 with display name my-fleet,
+    run:
+
+        $ gcloud alpha container fleet create --display-name=my-fleet \
+            --project=example-foo-bar-1
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --display-name=DISPLAY_NAME
+        Display name of the fleet to be created (optional). 4-30 characters,
+        alphanumeric and [ '"!-] only.
+
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     Default cluster configurations to apply across the fleet.
+
+       Security posture config.
+
+         --security-posture=SECURITY_POSTURE
+            To apply basic security posture to the clusters of the fleet,
+
+                $ gcloud alpha container fleet create --security-posture=basic
+
+            SECURITY_POSTURE must be one of: disabled, basic, enterprise.
+
+         --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING
+            To apply basic vulnerability scanning to the clusters of the fleet,
+
+                $ gcloud alpha container fleet create \
+                    --workload-vulnerability-scanning=disabled
+
+            WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, basic,
+            enterprise.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet create
+
+        $ gcloud beta container fleet create
+
diff --git a/gcloud/alpha/container/fleet/delete b/gcloud/alpha/container/fleet/delete
new file mode 100644
index 000000000..940bc6486
--- /dev/null
+++ b/gcloud/alpha/container/fleet/delete
@@ -0,0 +1,41 @@
+NAME
+    gcloud alpha container fleet delete - delete a fleet
+
+SYNOPSIS
+    gcloud alpha container fleet delete [--async] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project specified already has a fleet.
+      ▪ The active account does not have permission to access the given
+        project.
+
+EXAMPLES
+    To delete a fleet in project example-foo-bar-1, run:
+
+        $ gcloud alpha container fleet delete --project=example-foo-bar-1
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet delete
+
+        $ gcloud beta container fleet delete
+
diff --git a/gcloud/alpha/container/fleet/describe b/gcloud/alpha/container/fleet/describe
new file mode 100644
index 000000000..fc816c2b3
--- /dev/null
+++ b/gcloud/alpha/container/fleet/describe
@@ -0,0 +1,36 @@
+NAME
+    gcloud alpha container fleet describe - show fleet info
+
+SYNOPSIS
+    gcloud alpha container fleet describe [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project specified does not have a fleet.
+      ▪ The active account does not have permission to access the given
+        project.
+
+EXAMPLES
+    To print metadata for the fleet in project example-foo-bar-1, run:
+
+        $ gcloud alpha container fleet describe --project=example-foo-bar-1
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet describe
+
+        $ gcloud beta container fleet describe
+
diff --git a/gcloud/alpha/container/fleet/help b/gcloud/alpha/container/fleet/help
index 49a6222a7..15474f385 100644
--- a/gcloud/alpha/container/fleet/help
+++ b/gcloud/alpha/container/fleet/help
@@ -48,6 +48,9 @@ GROUPS
      cloudrun
         (ALPHA) Manage the CloudRun feature.
 
+     clusterupgrade
+        (ALPHA) Configure the Fleet clusterupgrade feature.
+
      config-management
         (ALPHA) Manage Config Management Feature.
 
@@ -89,6 +92,24 @@ GROUPS
      service-directory
         (ALPHA) Manage the Service Directory Feature.
 
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        (ALPHA) Create a fleet.
+
+     delete
+        (ALPHA) Delete a fleet.
+
+     describe
+        (ALPHA) Show fleet info.
+
+     list
+        (ALPHA) List fleets visible to the user in an organization.
+
+     update
+        (ALPHA) Update a fleet.
+
 NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
diff --git a/gcloud/alpha/container/fleet/list b/gcloud/alpha/container/fleet/list
new file mode 100644
index 000000000..b14c6efb2
--- /dev/null
+++ b/gcloud/alpha/container/fleet/list
@@ -0,0 +1,75 @@
+NAME
+    gcloud alpha container fleet list - list fleets visible to the user in an
+        organization
+
+SYNOPSIS
+    gcloud alpha container fleet list [--organization=ORGANIZATION_ID]
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The org or project specified does not exist.
+      ▪ The user does not have access to the project specified.
+
+EXAMPLES
+    The following command lists fleets in organization 12345:
+
+        $ gcloud alpha container fleet list --organization=12345
+
+COMMONLY USED FLAGS
+     --organization=ORGANIZATION_ID
+        ID (number) for the organization to list fleets from. If neither
+        --organization nor --project are provided, defaults to the organization
+        of the active project.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet list
+
+        $ gcloud beta container fleet list
+
diff --git a/gcloud/alpha/container/fleet/memberships/bindings/create b/gcloud/alpha/container/fleet/memberships/bindings/create
index a04c41426..d188a6803 100644
--- a/gcloud/alpha/container/fleet/memberships/bindings/create
+++ b/gcloud/alpha/container/fleet/memberships/bindings/create
@@ -99,7 +99,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet memberships bindings create
 
         $ gcloud beta container fleet memberships bindings create
 
diff --git a/gcloud/alpha/container/fleet/memberships/bindings/delete b/gcloud/alpha/container/fleet/memberships/bindings/delete
index 061617ab3..b3bc9c44c 100644
--- a/gcloud/alpha/container/fleet/memberships/bindings/delete
+++ b/gcloud/alpha/container/fleet/memberships/bindings/delete
@@ -82,7 +82,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet memberships bindings delete
 
         $ gcloud beta container fleet memberships bindings delete
 
diff --git a/gcloud/alpha/container/fleet/memberships/bindings/describe b/gcloud/alpha/container/fleet/memberships/bindings/describe
index 8e085bfbf..16c936c65 100644
--- a/gcloud/alpha/container/fleet/memberships/bindings/describe
+++ b/gcloud/alpha/container/fleet/memberships/bindings/describe
@@ -82,7 +82,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet memberships bindings describe
 
         $ gcloud beta container fleet memberships bindings describe
 
diff --git a/gcloud/alpha/container/fleet/memberships/bindings/help b/gcloud/alpha/container/fleet/memberships/bindings/help
index 7704da74f..957f5938d 100644
--- a/gcloud/alpha/container/fleet/memberships/bindings/help
+++ b/gcloud/alpha/container/fleet/memberships/bindings/help
@@ -42,7 +42,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet memberships bindings
 
         $ gcloud beta container fleet memberships bindings
 
diff --git a/gcloud/alpha/container/fleet/memberships/bindings/list b/gcloud/alpha/container/fleet/memberships/bindings/list
index 90934cfaf..0a4febe1c 100644
--- a/gcloud/alpha/container/fleet/memberships/bindings/list
+++ b/gcloud/alpha/container/fleet/memberships/bindings/list
@@ -81,7 +81,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet memberships bindings list
 
         $ gcloud beta container fleet memberships bindings list
 
diff --git a/gcloud/alpha/container/fleet/memberships/bindings/update b/gcloud/alpha/container/fleet/memberships/bindings/update
index bf8f52824..8d7b7a02d 100644
--- a/gcloud/alpha/container/fleet/memberships/bindings/update
+++ b/gcloud/alpha/container/fleet/memberships/bindings/update
@@ -123,7 +123,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet memberships bindings update
 
         $ gcloud beta container fleet memberships bindings update
 
diff --git a/gcloud/alpha/container/fleet/scopes/add-iam-policy-binding b/gcloud/alpha/container/fleet/scopes/add-iam-policy-binding
new file mode 100644
index 000000000..d4f44de2f
--- /dev/null
+++ b/gcloud/alpha/container/fleet/scopes/add-iam-policy-binding
@@ -0,0 +1,91 @@
+NAME
+    gcloud alpha container fleet scopes add-iam-policy-binding - add IAM policy
+        binding to a Fleet Scope
+
+SYNOPSIS
+    gcloud alpha container fleet scopes add-iam-policy-binding SCOPE
+        --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) Add an IAM policy binding to the IAM policy of a Fleet Scope. One
+    binding consists of a member, and a role.
+
+EXAMPLES
+    To add an IAM policy binding for the role of 'roles/gkehub.scopeUser' for
+    the user 'test-user@gmail.com' with scope 'my-scope', run:
+
+        $ gcloud alpha container fleet scopes add-iam-policy-binding \
+            my-scope --member='user:test-user@gmail.com' \
+            --role='roles/gkehub.scopeUser'
+
+    See https://cloud.google.com/iam/docs/managing-policies for details of
+    policy role and member types.
+
+POSITIONAL ARGUMENTS
+     Scope resource - The scope for which to add IAM policy binding to. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     To set the location attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+REQUIRED FLAGS
+     --member=PRINCIPAL
+        The principal to add the binding for. Should be of the form
+        user|group|serviceAccount:email or domain:domain.
+
+        Examples: user:test-user@gmail.com, group:admins@example.com,
+        serviceAccount:test123@example.domain.com, or
+        domain:example.domain.com.
+
+        Some resources also accept the following special values:
+        ◆ allUsers - Special identifier that represents anyone who is on the
+          internet, with or without a Google account.
+        ◆ allAuthenticatedUsers - Special identifier that represents anyone
+          who is authenticated with a Google account or a service account.
+
+     --role=ROLE
+        Role name to assign to the principal. The role name is the complete
+        path of a predefined role, such as roles/logging.viewer, or the role ID
+        for a custom role, such as
+        organizations/{ORGANIZATION_ID}/roles/logging.viewer.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1alpha API. The full documentation for this
+    API can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet scopes add-iam-policy-binding
+
+        $ gcloud beta container fleet scopes add-iam-policy-binding
+
diff --git a/gcloud/alpha/container/fleet/scopes/create b/gcloud/alpha/container/fleet/scopes/create
index b5bba14b4..735f4cbd1 100644
--- a/gcloud/alpha/container/fleet/scopes/create
+++ b/gcloud/alpha/container/fleet/scopes/create
@@ -7,7 +7,8 @@ SYNOPSIS
         [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING
           --upstream-scope=UPSTREAM_SCOPE
           --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE
-          --upgrade-selector=[UPGRADE_SELECTOR,...]] [GCLOUD_WIDE_FLAG ...]
+          --upgrade-selector=[name=NAME],[version=VERSION]]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (ALPHA) Create a Fleet Scope resource.
@@ -113,7 +114,7 @@ FLAGS
             This flag argument must be specified if any of the other arguments
             in this group are specified.
 
-         --upgrade-selector=[UPGRADE_SELECTOR,...]
+         --upgrade-selector=[name=NAME],[version=VERSION]
             Name and version of the upgrade to be overridden where version is a
             full GKE version. Currently, name can be either k8s_control_plane
             or k8s_node.
@@ -138,7 +139,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet scopes create
 
         $ gcloud beta container fleet scopes create
 
diff --git a/gcloud/alpha/container/fleet/scopes/delete b/gcloud/alpha/container/fleet/scopes/delete
index d63c11437..6f11a46cf 100644
--- a/gcloud/alpha/container/fleet/scopes/delete
+++ b/gcloud/alpha/container/fleet/scopes/delete
@@ -73,7 +73,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet scopes delete
 
         $ gcloud beta container fleet scopes delete
 
diff --git a/gcloud/alpha/container/fleet/scopes/describe b/gcloud/alpha/container/fleet/scopes/describe
index 0f0b3fd9b..c088626be 100644
--- a/gcloud/alpha/container/fleet/scopes/describe
+++ b/gcloud/alpha/container/fleet/scopes/describe
@@ -95,7 +95,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet scopes describe
 
         $ gcloud beta container fleet scopes describe
 
diff --git a/gcloud/alpha/container/fleet/scopes/get-iam-policy b/gcloud/alpha/container/fleet/scopes/get-iam-policy
new file mode 100644
index 000000000..8f08be6f4
--- /dev/null
+++ b/gcloud/alpha/container/fleet/scopes/get-iam-policy
@@ -0,0 +1,90 @@
+NAME
+    gcloud alpha container fleet scopes get-iam-policy - get the IAM policy for
+        a Fleet Scope
+
+SYNOPSIS
+    gcloud alpha container fleet scopes get-iam-policy SCOPE
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command gets the IAM policy for a scope.
+
+EXAMPLES
+    To print the IAM policy for a given scope, run:
+
+        $ gcloud alpha container fleet scopes get-iam-policy my-scope
+
+POSITIONAL ARGUMENTS
+     Scope resource - The scope for which to display the IAM policy. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     To set the location attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1alpha API. The full documentation for this
+    API can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet scopes get-iam-policy
+
+        $ gcloud beta container fleet scopes get-iam-policy
+
diff --git a/gcloud/alpha/container/fleet/scopes/help b/gcloud/alpha/container/fleet/scopes/help
index a8e3f82bf..9c5339793 100644
--- a/gcloud/alpha/container/fleet/scopes/help
+++ b/gcloud/alpha/container/fleet/scopes/help
@@ -12,9 +12,22 @@ GCLOUD WIDE FLAGS
 
     Run $ gcloud help for details.
 
+GROUPS
+    GROUP is one of the following:
+
+     namespaces
+        (ALPHA) Fleet namespaces are the fleet equivalent of k8s cluster
+        namespaces.
+
+     rbacrolebindings
+        (ALPHA) Fleet scope RBAC RoleBindings for permissions.
+
 COMMANDS
     COMMAND is one of the following:
 
+     add-iam-policy-binding
+        (ALPHA) Add IAM policy binding to a Fleet Scope.
+
      create
         (ALPHA) Create a new fleet scope.
 
@@ -24,9 +37,15 @@ COMMANDS
      describe
         (ALPHA) Describe a fleet scope.
 
+     get-iam-policy
+        (ALPHA) Get the IAM policy for a Fleet Scope.
+
      list
         (ALPHA) List fleet scopes.
 
+     remove-iam-policy-binding
+        (ALPHA) Remove IAM policy binding of a Fleet Scope.
+
      update
         (ALPHA) Update a scope.
 
@@ -34,7 +53,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet scopes
 
         $ gcloud beta container fleet scopes
 
diff --git a/gcloud/alpha/container/fleet/scopes/list b/gcloud/alpha/container/fleet/scopes/list
index b8e269edc..c598de3f7 100644
--- a/gcloud/alpha/container/fleet/scopes/list
+++ b/gcloud/alpha/container/fleet/scopes/list
@@ -63,7 +63,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet scopes list
 
         $ gcloud beta container fleet scopes list
 
diff --git a/gcloud/alpha/container/fleet/scopes/namespaces/create b/gcloud/alpha/container/fleet/scopes/namespaces/create
new file mode 100644
index 000000000..88a4a8822
--- /dev/null
+++ b/gcloud/alpha/container/fleet/scopes/namespaces/create
@@ -0,0 +1,92 @@
+NAME
+    gcloud alpha container fleet scopes namespaces create - create a fleet
+        namespace
+
+SYNOPSIS
+    gcloud alpha container fleet scopes namespaces create
+        (NAMESPACE : --scope=SCOPE) [--labels=[KEY=VALUE,...]]
+        [--namespace-labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project has a fleet namespace with the same name.
+      ▪ The caller does not have permission to access the given project.
+
+EXAMPLES
+    To create a fleet namespace with name NAMESPACE in the active project, run:
+
+        $ gcloud alpha container fleet scopes namespaces create NAMESPACE
+
+    To create a fleet namespace in fleet scope SCOPE in project PROJECT_ID with
+    name NAMESPACE, run:
+
+        $ gcloud alpha container fleet scopes namespaces create NAMESPACE \
+            --scope=SCOPE --project=PROJECT_ID
+
+POSITIONAL ARGUMENTS
+     Namespace resource - The group of arguments defining the Fleet Namespace.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       NAMESPACE
+          ID of the namespace or fully qualified identifier for the namespace.
+
+          To set the namespace attribute:
+          ▸ provide the argument NAMESPACE on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --scope=SCOPE
+          the
+
+          To set the scope attribute:
+          ▸ provide the argument NAMESPACE on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+FLAGS
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     --namespace-labels=[KEY=VALUE,...]
+        List of namespace-level label KEY=VALUE pairs to add.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet scopes namespaces create
+
+        $ gcloud beta container fleet scopes namespaces create
+
diff --git a/gcloud/alpha/container/fleet/scopes/namespaces/delete b/gcloud/alpha/container/fleet/scopes/namespaces/delete
new file mode 100644
index 000000000..111ee928a
--- /dev/null
+++ b/gcloud/alpha/container/fleet/scopes/namespaces/delete
@@ -0,0 +1,79 @@
+NAME
+    gcloud alpha container fleet scopes namespaces delete - delete a fleet
+        namespace
+
+SYNOPSIS
+    gcloud alpha container fleet scopes namespaces delete
+        (NAMESPACE : --scope=SCOPE) [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The namespace specified does not exist.
+      ▪ The caller does not have permission to access the given project or
+        namespace.
+
+EXAMPLES
+    To delete fleet namespace NAMESPACE in the active project:
+
+        $ gcloud alpha container fleet scopes namespaces delete NAMESPACE
+
+    To delete fleet namespace NAMESPACE in project PROJECT_ID:
+
+        $ gcloud alpha container fleet scopes namespaces delete NAMESPACE \
+            --project=PROJECT_ID
+
+POSITIONAL ARGUMENTS
+     Namespace resource - The group of arguments defining the Fleet Namespace.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       NAMESPACE
+          ID of the namespace or fully qualified identifier for the namespace.
+
+          To set the namespace attribute:
+          ▸ provide the argument NAMESPACE on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --scope=SCOPE
+          the
+
+          To set the scope attribute:
+          ▸ provide the argument NAMESPACE on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet scopes namespaces delete
+
+        $ gcloud beta container fleet scopes namespaces delete
+
diff --git a/gcloud/alpha/container/fleet/scopes/namespaces/describe b/gcloud/alpha/container/fleet/scopes/namespaces/describe
new file mode 100644
index 000000000..6dd7dda3c
--- /dev/null
+++ b/gcloud/alpha/container/fleet/scopes/namespaces/describe
@@ -0,0 +1,79 @@
+NAME
+    gcloud alpha container fleet scopes namespaces describe - show fleet
+        namespace info
+
+SYNOPSIS
+    gcloud alpha container fleet scopes namespaces describe
+        (NAMESPACE : --scope=SCOPE) [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The namespace specified does not exist in the project.
+      ▪ The caller does not have permission to access the project or
+        namespace.
+
+EXAMPLES
+    To print metadata for the namespace NAMESPACE in the active project, run:
+
+        $ gcloud alpha container fleet scopes namespaces describe NAMESPACE
+
+    To print metadata for the namespace NAMESPACE in project PROJECT_ID, run:
+
+        $ gcloud alpha container fleet scopes namespaces describe \
+            NAMESPACE --project=PROJECT_ID
+
+POSITIONAL ARGUMENTS
+     Namespace resource - The group of arguments defining the Fleet Namespace.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       NAMESPACE
+          ID of the namespace or fully qualified identifier for the namespace.
+
+          To set the namespace attribute:
+          ▸ provide the argument NAMESPACE on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --scope=SCOPE
+          the
+
+          To set the scope attribute:
+          ▸ provide the argument NAMESPACE on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet scopes namespaces describe
+
+        $ gcloud beta container fleet scopes namespaces describe
+
diff --git a/gcloud/alpha/container/fleet/scopes/namespaces/get-credentials b/gcloud/alpha/container/fleet/scopes/namespaces/get-credentials
new file mode 100644
index 000000000..c8538a385
--- /dev/null
+++ b/gcloud/alpha/container/fleet/scopes/namespaces/get-credentials
@@ -0,0 +1,62 @@
+NAME
+    gcloud alpha container fleet scopes namespaces get-credentials - fetch
+        credentials for a membership with a particular namespace
+
+SYNOPSIS
+    gcloud alpha container fleet scopes namespaces get-credentials NAMESPACE
+        [--membership=MEMBERSHIP] [--membership-location=MEMBERSHIP_LOCATION]
+        [--set-namespace-in-config=SET_NAMESPACE_IN_CONFIG]
+        [GCLOUD_WIDE_FLAG ...]
+
+EXAMPLES
+    Get the Connect Gateway kubeconfig for global membership MEMBERSHIP, using
+    namespace NAMESPACE in the config:
+
+        $ gcloud alpha container fleet scopes namespaces get-credentials \
+            NAMESPACE --membership=MEMBERSHIP --membership-location=global \
+            --set-namespace-in-config=true
+
+    Get the Connect Gateway kubeconfig for global membership MEMBERSHIP:
+
+        $ gcloud alpha container fleet scopes namespaces get-credentials \
+            NAMESPACE --membership=MEMBERSHIP --membership-location=global
+
+POSITIONAL ARGUMENTS
+     NAMESPACE
+        Name of the namespace for which to get access to memberships.
+
+FLAGS
+     --membership=MEMBERSHIP
+        Membership ID to get credentials from. If not provided, a prompt will
+        offer a list of memberships in the fleet.
+
+     --membership-location=MEMBERSHIP_LOCATION
+        The location of the membership resource, e.g. us-central1. If not
+        specified, defaults to global.
+
+     --set-namespace-in-config=SET_NAMESPACE_IN_CONFIG
+        If true, the default namespace for the context in the generated
+        kubeconfig will be set to the Fleet namespace (i.e. the name given as
+        the positional argument in this command).
+
+        Otherwise, no default namespace will be set, functioning the same as
+        gcloud container fleet memberships get-credentials.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet scopes namespaces get-credentials
+
+        $ gcloud beta container fleet scopes namespaces get-credentials
+
diff --git a/gcloud/alpha/container/fleet/scopes/namespaces/help b/gcloud/alpha/container/fleet/scopes/namespaces/help
new file mode 100644
index 000000000..76cfedc9f
--- /dev/null
+++ b/gcloud/alpha/container/fleet/scopes/namespaces/help
@@ -0,0 +1,57 @@
+NAME
+    gcloud alpha container fleet scopes namespaces - fleet namespaces are the
+        fleet equivalent of k8s cluster namespaces
+
+SYNOPSIS
+    gcloud alpha container fleet scopes namespaces COMMAND
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command group allows for manipulation of fleet namespaces.
+
+EXAMPLES
+    Manage fleet namespaces:
+
+        $ gcloud alpha container fleet scopes namespaces --help
+
+    Manage RBAC RoleBindings in a fleet namespace:
+
+        $ gcloud alpha container fleet scopes namespaces rbacrolebindings \
+            --help
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        (ALPHA) Create a fleet namespace.
+
+     delete
+        (ALPHA) Delete a fleet namespace.
+
+     describe
+        (ALPHA) Show fleet namespace info.
+
+     get-credentials
+        (ALPHA) Fetch credentials for a membership with a particular namespace.
+
+     list
+        (ALPHA) List fleet namespaces in a project.
+
+     update
+        (ALPHA) Update a fleet namespace.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet scopes namespaces
+
+        $ gcloud beta container fleet scopes namespaces
+
diff --git a/gcloud/alpha/container/fleet/scopes/namespaces/list b/gcloud/alpha/container/fleet/scopes/namespaces/list
new file mode 100644
index 000000000..28281abdd
--- /dev/null
+++ b/gcloud/alpha/container/fleet/scopes/namespaces/list
@@ -0,0 +1,98 @@
+NAME
+    gcloud alpha container fleet scopes namespaces list - list fleet namespaces
+        in a project
+
+SYNOPSIS
+    gcloud alpha container fleet scopes namespaces list --scope=SCOPE
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The user does not have access to the project specified.
+
+EXAMPLES
+    The following command lists namespaces in the active project:
+
+        $ gcloud alpha container fleet scopes namespaces list
+
+    The following command lists namespaces in project PROJECT_ID:
+
+        $ gcloud alpha container fleet scopes namespaces list \
+            --project=PROJECT_ID
+
+REQUIRED FLAGS
+     Scope resource - The group of arguments defining the Fleet Scope. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --scope on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --scope on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       --scope=SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument --scope on the command line.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet scopes namespaces list
+
+        $ gcloud beta container fleet scopes namespaces list
+
diff --git a/gcloud/alpha/container/fleet/scopes/namespaces/update b/gcloud/alpha/container/fleet/scopes/namespaces/update
new file mode 100644
index 000000000..bb40c5d31
--- /dev/null
+++ b/gcloud/alpha/container/fleet/scopes/namespaces/update
@@ -0,0 +1,144 @@
+NAME
+    gcloud alpha container fleet scopes namespaces update - update a fleet
+        namespace
+
+SYNOPSIS
+    gcloud alpha container fleet scopes namespaces update
+        (NAMESPACE : --scope=SCOPE) [--update-labels=[KEY=VALUE,...]]
+        [--update-namespace-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]]
+        [--clear-namespace-labels | --remove-namespace-labels=[KEY,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The fleet namespace does not exist in the project.
+      ▪ The caller does not have permission to access the project or
+        namespace.
+
+EXAMPLES
+    To update the namespace NAMESPACE in the active project:
+
+        $ gcloud alpha container fleet scopes namespaces update NAMESPACE
+
+    To update the namespace NAMESPACE in project PROJECT_ID:
+
+        $ gcloud alpha container fleet scopes namespaces update NAMESPACE \
+            --project=PROJECT_ID
+
+POSITIONAL ARGUMENTS
+     Namespace resource - The group of arguments defining the Fleet Namespace.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       NAMESPACE
+          ID of the namespace or fully qualified identifier for the namespace.
+
+          To set the namespace attribute:
+          ▸ provide the argument NAMESPACE on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --scope=SCOPE
+          the
+
+          To set the scope attribute:
+          ▸ provide the argument NAMESPACE on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+FLAGS
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     --update-namespace-labels=[KEY=VALUE,...]
+        List of namespace-level label KEY=VALUE pairs to update in the cluster
+        namespace. If a label exists, its value is modified. Otherwise, a new
+        label is' created.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud alpha container fleet scopes namespaces update \
+                --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud alpha container fleet scopes namespaces update \
+                --clear-labels --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+     At most one of these can be specified:
+
+       --clear-namespace-labels
+          Remove all namespace-level labels from the cluster namespace. If
+          --update-namespace-labels is also specified then
+          --clear-namespace-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud alpha container fleet scopes namespaces update \
+                namespace_name --clear-namespace-labels
+
+          To remove all existing namespace-level labels and create two new
+          labels, foo and baz:
+
+              $ gcloud alpha container fleet scopes namespaces update \
+                namespace_name --clear-namespace-labels \
+                --update-namespace-labels foo=bar,baz=qux
+
+       --remove-namespace-labels=[KEY,...]
+          List of namespace-level label keys to remove in the cluster
+          namespace. If a label does not exist it is silently ignored. If
+          --update-namespace-labels is also specified then
+          --update-namespace-labels is applied first.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet scopes namespaces update
+
+        $ gcloud beta container fleet scopes namespaces update
+
diff --git a/gcloud/alpha/container/fleet/scopes/rbacrolebindings/create b/gcloud/alpha/container/fleet/scopes/rbacrolebindings/create
new file mode 100644
index 000000000..90496bc0a
--- /dev/null
+++ b/gcloud/alpha/container/fleet/scopes/rbacrolebindings/create
@@ -0,0 +1,108 @@
+NAME
+    gcloud alpha container fleet scopes rbacrolebindings create - create an
+        RBAC RoleBinding
+
+SYNOPSIS
+    gcloud alpha container fleet scopes rbacrolebindings create
+        (NAME : --location=LOCATION --scope=SCOPE) --role=ROLE
+        (--group=GROUP | --user=USER) [--labels=[KEY=VALUE,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The RBAC RoleBinding already exists.
+      ▪ The caller does not have permission to access the given scope.
+
+EXAMPLES
+    To create an admin RBAC RoleBinding RBRB in scope SCOPE for user
+    person@google.com, run:
+
+        $ gcloud alpha container fleet scopes rbacrolebindings create RBRB \
+            --scope=SCOPE --role=admin --user=person@google.com
+
+    To create a viewer RBAC RoleBinding RBRB in scope SCOPE for group
+    people@google.com, run:
+
+        $ gcloud alpha container fleet scopes rbacrolebindings create RBRB \
+            --scope=SCOPE --role=viewer --group=people@google.com
+
+POSITIONAL ARGUMENTS
+     Rbacrolebinding resource - The group of arguments defining an
+     RBACRoleBinding. The arguments in this group can be used to specify the
+     attributes of this resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAME on the command line with a fully specified
+        name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       NAME
+          ID of the rbacrolebinding or fully qualified identifier for the
+          rbacrolebinding.
+
+          To set the rbacrolebinding attribute:
+          ▸ provide the argument NAME on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the rbacrolebinding.
+
+          To set the location attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --scope=SCOPE
+          Name of the rbacrolebinding.
+
+          To set the scope attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+REQUIRED FLAGS
+     --role=ROLE
+        Role to assign. ROLE must be one of: admin, edit, view.
+
+     Exactly one of these must be specified:
+
+       --group=GROUP
+          Group for the RoleBinding.
+
+       --user=USER
+          User for the RoleBinding.
+
+OPTIONAL FLAGS
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet scopes rbacrolebindings create
+
+        $ gcloud beta container fleet scopes rbacrolebindings create
+
diff --git a/gcloud/alpha/container/fleet/scopes/rbacrolebindings/delete b/gcloud/alpha/container/fleet/scopes/rbacrolebindings/delete
new file mode 100644
index 000000000..3fc2efa96
--- /dev/null
+++ b/gcloud/alpha/container/fleet/scopes/rbacrolebindings/delete
@@ -0,0 +1,78 @@
+NAME
+    gcloud alpha container fleet scopes rbacrolebindings delete - delete a
+        fleet scope RBAC RoleBinding
+
+SYNOPSIS
+    gcloud alpha container fleet scopes rbacrolebindings delete
+        (NAME : --location=LOCATION --scope=SCOPE) [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The RoleBinding specified does not exist.
+      ▪ The caller does not have permission to access the given RoleBinding.
+
+EXAMPLES
+    To delete RBAC RoleBinding RBRB in scope SCOPE in the active project:
+
+        $ gcloud alpha container fleet scopes rbacrolebindings delete RBRB \
+            --scope=SCOPE
+
+POSITIONAL ARGUMENTS
+     Rbacrolebinding resource - The group of arguments defining an
+     RBACRoleBinding. The arguments in this group can be used to specify the
+     attributes of this resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAME on the command line with a fully specified
+        name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       NAME
+          ID of the rbacrolebinding or fully qualified identifier for the
+          rbacrolebinding.
+
+          To set the rbacrolebinding attribute:
+          ▸ provide the argument NAME on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the rbacrolebinding.
+
+          To set the location attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --scope=SCOPE
+          Name of the rbacrolebinding.
+
+          To set the scope attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet scopes rbacrolebindings delete
+
+        $ gcloud beta container fleet scopes rbacrolebindings delete
+
diff --git a/gcloud/alpha/container/fleet/scopes/rbacrolebindings/describe b/gcloud/alpha/container/fleet/scopes/rbacrolebindings/describe
new file mode 100644
index 000000000..284fb52f2
--- /dev/null
+++ b/gcloud/alpha/container/fleet/scopes/rbacrolebindings/describe
@@ -0,0 +1,78 @@
+NAME
+    gcloud alpha container fleet scopes rbacrolebindings describe - show fleet
+        scope RBAC RoleBinding information
+
+SYNOPSIS
+    gcloud alpha container fleet scopes rbacrolebindings describe
+        (NAME : --location=LOCATION --scope=SCOPE) [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The RoleBinding specified does not exist in the project.
+      ▪ The caller does not have permission to access the RoleBinding.
+
+EXAMPLES
+    To print metadata for RBAC RoleBinding RBRB in the scope SCOPE, run:
+
+        $ gcloud alpha container fleet scopes rbacrolebindings describe \
+            RBRB --scope=SCOPE
+
+POSITIONAL ARGUMENTS
+     Rbacrolebinding resource - The group of arguments defining an
+     RBACRoleBinding. The arguments in this group can be used to specify the
+     attributes of this resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAME on the command line with a fully specified
+        name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       NAME
+          ID of the rbacrolebinding or fully qualified identifier for the
+          rbacrolebinding.
+
+          To set the rbacrolebinding attribute:
+          ▸ provide the argument NAME on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the rbacrolebinding.
+
+          To set the location attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --scope=SCOPE
+          Name of the rbacrolebinding.
+
+          To set the scope attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet scopes rbacrolebindings describe
+
+        $ gcloud beta container fleet scopes rbacrolebindings describe
+
diff --git a/gcloud/alpha/container/fleet/scopes/rbacrolebindings/help b/gcloud/alpha/container/fleet/scopes/rbacrolebindings/help
new file mode 100644
index 000000000..70601c649
--- /dev/null
+++ b/gcloud/alpha/container/fleet/scopes/rbacrolebindings/help
@@ -0,0 +1,50 @@
+NAME
+    gcloud alpha container fleet scopes rbacrolebindings - fleet scope RBAC
+        RoleBindings for permissions
+
+SYNOPSIS
+    gcloud alpha container fleet scopes rbacrolebindings COMMAND
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command group allows for manipulation of fleet namespace RBAC
+    RoleBindings.
+
+EXAMPLES
+    Manage RBAC RoleBindings:
+
+        $ gcloud alpha container fleet scopes rbacrolebindings --help
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        (ALPHA) Create an RBAC RoleBinding.
+
+     delete
+        (ALPHA) Delete a fleet scope RBAC RoleBinding.
+
+     describe
+        (ALPHA) Show fleet scope RBAC RoleBinding information.
+
+     list
+        (ALPHA) List RBAC RoleBindings in a fleet scope.
+
+     update
+        (ALPHA) Update a fleet scope RBAC RoleBinding.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet scopes rbacrolebindings
+
+        $ gcloud beta container fleet scopes rbacrolebindings
+
diff --git a/gcloud/alpha/container/fleet/scopes/rbacrolebindings/list b/gcloud/alpha/container/fleet/scopes/rbacrolebindings/list
new file mode 100644
index 000000000..d33097739
--- /dev/null
+++ b/gcloud/alpha/container/fleet/scopes/rbacrolebindings/list
@@ -0,0 +1,75 @@
+NAME
+    gcloud alpha container fleet scopes rbacrolebindings list - list RBAC
+        RoleBindings in a fleet scope
+
+SYNOPSIS
+    gcloud alpha container fleet scopes rbacrolebindings list --scope=SCOPE
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The scope specified does not exist.
+      ▪ The user does not have access to the specified scope.
+
+EXAMPLES
+    The following command lists RBAC RoleBindings in scope SCOPE in project
+    PROJECT_ID:
+
+        $ gcloud alpha container fleet scopes rbacrolebindings list \
+            --scope=SCOPE --project=PROJECT_ID
+
+REQUIRED FLAGS
+     --scope=SCOPE
+        Name of the fleet scope to list RBAC RoleBindings from.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet scopes rbacrolebindings list
+
+        $ gcloud beta container fleet scopes rbacrolebindings list
+
diff --git a/gcloud/alpha/container/fleet/scopes/rbacrolebindings/update b/gcloud/alpha/container/fleet/scopes/rbacrolebindings/update
new file mode 100644
index 000000000..3d4c394b8
--- /dev/null
+++ b/gcloud/alpha/container/fleet/scopes/rbacrolebindings/update
@@ -0,0 +1,131 @@
+NAME
+    gcloud alpha container fleet scopes rbacrolebindings update - update a
+        fleet scope RBAC RoleBinding
+
+SYNOPSIS
+    gcloud alpha container fleet scopes rbacrolebindings update
+        (NAME : --location=LOCATION --scope=SCOPE) [--role=ROLE]
+        [--update-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]]
+        [--group=GROUP | --user=USER] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The RoleBinding does not exist in the project.
+      ▪ The caller does not have permission to access the RoleBinding.
+
+EXAMPLES
+    To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to
+    the viewer role:
+
+        $ gcloud alpha container fleet scopes rbacrolebindings update RBRB \
+            --scope=SCOPE --role=viewer
+
+    To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to
+    the user someone@google.com:
+
+        $ gcloud alpha container fleet scopes rbacrolebindings update RBRB \
+            --scope=SCOPE --user=someone@google.com
+
+POSITIONAL ARGUMENTS
+     Rbacrolebinding resource - The group of arguments defining an
+     RBACRoleBinding. The arguments in this group can be used to specify the
+     attributes of this resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAME on the command line with a fully specified
+        name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       NAME
+          ID of the rbacrolebinding or fully qualified identifier for the
+          rbacrolebinding.
+
+          To set the rbacrolebinding attribute:
+          ▸ provide the argument NAME on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the rbacrolebinding.
+
+          To set the location attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --scope=SCOPE
+          Name of the rbacrolebinding.
+
+          To set the scope attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+FLAGS
+     --role=ROLE
+        Role for the RBACRoleBinding to update to. ROLE must be one of: admin,
+        edit, view.
+
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud alpha container fleet scopes rbacrolebindings update \
+                --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud alpha container fleet scopes rbacrolebindings update \
+                --clear-labels --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+     At most one of these can be specified:
+
+       --group=GROUP
+          Group for the RBACRoleBinding to update to.
+
+       --user=USER
+          User for the RBACRoleBinding to update to.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet scopes rbacrolebindings update
+
+        $ gcloud beta container fleet scopes rbacrolebindings update
+
diff --git a/gcloud/alpha/container/fleet/scopes/remove-iam-policy-binding b/gcloud/alpha/container/fleet/scopes/remove-iam-policy-binding
new file mode 100644
index 000000000..d18cd60de
--- /dev/null
+++ b/gcloud/alpha/container/fleet/scopes/remove-iam-policy-binding
@@ -0,0 +1,92 @@
+NAME
+    gcloud alpha container fleet scopes remove-iam-policy-binding - remove IAM
+        policy binding of a Fleet Scope
+
+SYNOPSIS
+    gcloud alpha container fleet scopes remove-iam-policy-binding SCOPE
+        --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) Remove an IAM policy binding from the IAM policy of a scope. One
+    binding consists of a member, and a role.
+
+EXAMPLES
+    To remove an IAM policy binding for the role of 'roles/gkehub.scopeUser'
+    for the user 'test-user@gmail.com' with scope 'my-scope', run:
+
+        $ gcloud alpha container fleet scopes remove-iam-policy-binding \
+            my-scope --member='user:test-user@gmail.com' \
+            --role='roles/gkehub.scopeUser'
+
+    See https://cloud.google.com/iam/docs/managing-policies for details of
+    policy role and member types.
+
+POSITIONAL ARGUMENTS
+     Scope resource - The scope for which to remove IAM policy binding from.
+     This represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     To set the location attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+REQUIRED FLAGS
+     --member=PRINCIPAL
+        The principal to remove the binding for. Should be of the form
+        user|group|serviceAccount:email or domain:domain.
+
+        Examples: user:test-user@gmail.com, group:admins@example.com,
+        serviceAccount:test123@example.domain.com, or
+        domain:example.domain.com.
+
+        Deleted principals have an additional deleted: prefix and a ?uid=UID
+        suffix, where UID is a unique identifier for the principal. Example:
+        deleted:user:test-user@gmail.com?uid=123456789012345678901.
+
+        Some resources also accept the following special values:
+        ◆ allUsers - Special identifier that represents anyone who is on the
+          internet, with or without a Google account.
+        ◆ allAuthenticatedUsers - Special identifier that represents anyone
+          who is authenticated with a Google account or a service account.
+
+     --role=ROLE
+        The role to remove the principal from.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1alpha API. The full documentation for this
+    API can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet scopes remove-iam-policy-binding
+
+        $ gcloud beta container fleet scopes remove-iam-policy-binding
+
diff --git a/gcloud/alpha/container/fleet/scopes/update b/gcloud/alpha/container/fleet/scopes/update
index f51d2a598..9f8014086 100644
--- a/gcloud/alpha/container/fleet/scopes/update
+++ b/gcloud/alpha/container/fleet/scopes/update
@@ -10,8 +10,9 @@ SYNOPSIS
         [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING
           --remove-upgrade-soaking-overrides
           | --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE
-          --upgrade-selector=[UPGRADE_SELECTOR,...] --reset-upstream-scope
-          | --upstream-scope=UPSTREAM_SCOPE] [GCLOUD_WIDE_FLAG ...]
+          --upgrade-selector=[name=NAME],[version=VERSION]
+          --reset-upstream-scope | --upstream-scope=UPSTREAM_SCOPE]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (ALPHA) Update an existing Fleet Scope.
@@ -174,7 +175,7 @@ FLAGS
               This flag argument must be specified if any of the other
               arguments in this group are specified.
 
-           --upgrade-selector=[UPGRADE_SELECTOR,...]
+           --upgrade-selector=[name=NAME],[version=VERSION]
               Name and version of the upgrade to be overridden where version is
               a full GKE version. Currently, name can be either
               k8s_control_plane or k8s_node.
@@ -221,7 +222,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet scopes update
 
         $ gcloud beta container fleet scopes update
 
diff --git a/gcloud/alpha/container/fleet/update b/gcloud/alpha/container/fleet/update
new file mode 100644
index 000000000..03989c65c
--- /dev/null
+++ b/gcloud/alpha/container/fleet/update
@@ -0,0 +1,101 @@
+NAME
+    gcloud alpha container fleet update - update a fleet
+
+SYNOPSIS
+    gcloud alpha container fleet update [--async] [--display-name=DISPLAY_NAME]
+        [--update-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]]
+        [--security-posture=SECURITY_POSTURE
+          --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project specified already has a fleet.
+      ▪ The active account does not have permission to access the given
+        project.
+
+EXAMPLES
+    To update the display name of the fleet in project example-foo-bar-1 to
+    updated-name, run:
+
+        $ gcloud alpha container fleet update --display-name=updated-name \
+            --project=example-foo-bar-1
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --display-name=DISPLAY_NAME
+        Display name of the fleet to be created (optional). 4-30 characters,
+        alphanumeric and [ '"!-] only.
+
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud alpha container fleet update --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud alpha container fleet update --clear-labels \
+                --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+     Default cluster configurations to apply across the fleet.
+
+       Security posture config.
+
+         --security-posture=SECURITY_POSTURE
+            To apply basic security posture to the clusters of the fleet,
+
+                $ gcloud alpha container fleet update --security-posture=basic
+
+            SECURITY_POSTURE must be one of: disabled, basic, enterprise.
+
+         --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING
+            To apply basic vulnerability scanning to the clusters of the fleet,
+
+                $ gcloud alpha container fleet update \
+                    --workload-vulnerability-scanning=disabled
+
+            WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, basic,
+            enterprise.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container fleet update
+
+        $ gcloud beta container fleet update
+
diff --git a/gcloud/alpha/container/hub/clusterupgrade/create b/gcloud/alpha/container/hub/clusterupgrade/create
new file mode 100644
index 000000000..ed3f79b0d
--- /dev/null
+++ b/gcloud/alpha/container/hub/clusterupgrade/create
@@ -0,0 +1,87 @@
+NAME
+    gcloud alpha container hub clusterupgrade create - create the
+        clusterupgrade feature for a fleet within a given project
+
+SYNOPSIS
+    gcloud alpha container hub clusterupgrade create
+        [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING]
+        [--upstream-fleet=UPSTREAM_FLEET]
+        [--add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE
+          --upgrade-selector=[name=NAME],[version=VERSION]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) Create the clusterupgrade feature for a fleet within a given
+    project.
+
+FLAGS
+     --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING
+        Configures the default soaking duration for each upgrade propagating
+        through the current fleet to become "COMPLETE". Soaking begins after
+        all clusters in the fleet are on the target version, or after 30 days
+        if all cluster upgrades are not complete. Once an upgrade state becomes
+        "COMPLETE", it will automatically be propagated to the downstream
+        fleet. Max is 30 days.
+
+        To configure Rollout Sequencing for a fleet, this attribute must be
+        set. To do this while specifying a default soaking duration of 7 days,
+        run:
+
+            $ gcloud alpha container hub clusterupgrade create \
+                --default-upgrade-soaking=7d
+
+     --upstream-fleet=UPSTREAM_FLEET
+        The upstream fleet. GKE will finish upgrades on the upstream fleet
+        before applying the same upgrades to the current fleet.
+
+        To configure the upstream fleet, run:
+
+            $ gcloud alpha container hub clusterupgrade create             \
+                --upstream-fleet={upstream_fleet}
+
+     Upgrade soaking override.
+
+         Defines a specific soaking time override for a particular upgrade
+         propagating through the current fleet that supercedes the default
+         soaking duration configured by `--default-upgrade-soaking`.
+
+         To set an upgrade soaking override of 12 hours for the upgrade with
+         name, `k8s_control_plane`, and version, `1.23.1-gke.1000`, run:
+
+         $ gcloud alpha container hub clusterupgrade create               \
+         --add-upgrade-soaking-override=12h               \
+         --upgrade-selector=name="k8s_control_plane",\
+         version="1.23.1-gke.1000"
+
+       --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE
+          Overrides the soaking time for a particular upgrade name and version
+          propagating through the current fleet. Set soaking to 0 days to
+          bypass soaking and fast-forward the upgrade to the downstream fleet.
+
+          See $ gcloud topic datetimes for information on duration formats.
+
+          This flag argument must be specified if any of the other arguments in
+          this group are specified.
+
+       --upgrade-selector=[name=NAME],[version=VERSION]
+          Name and version of the upgrade to be overridden where version is a
+          full GKE version. Currently, name can be either k8s_control_plane or
+          k8s_node.
+
+          This flag argument must be specified if any of the other arguments in
+          this group are specified.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist.
+
diff --git a/gcloud/alpha/container/hub/clusterupgrade/describe b/gcloud/alpha/container/hub/clusterupgrade/describe
new file mode 100644
index 000000000..3d2699d72
--- /dev/null
+++ b/gcloud/alpha/container/hub/clusterupgrade/describe
@@ -0,0 +1,46 @@
+NAME
+    gcloud alpha container hub clusterupgrade describe - describe the
+        clusterupgrade feature for a fleet within a given project
+
+SYNOPSIS
+    gcloud alpha container hub clusterupgrade describe
+        [--show-linked-cluster-upgrade] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) Describe the Fleet clusterupgrade feature used for configuring
+    fleet-based rollout sequencing.
+
+EXAMPLES
+    To view the cluster upgrade feature information for the current fleet, run:
+
+        $ gcloud alpha container hub clusterupgrade describe
+
+FLAGS
+     --show-linked-cluster-upgrade
+        Shows the cluster upgrade feature information for the current fleet as
+        well as information for all other fleets linked in the same rollout
+        sequence (provided that the caller has permission to view the upstream
+        and downstream fleets). This displays cluster upgrade information for
+        fleets in the current fleet's rollout sequence in order of furthest
+        upstream to downstream.
+
+        To view the cluster upgrade feature information for the rollout
+        sequence containing the current fleet, run:
+
+            $ gcloud alpha container hub clusterupgrade describe \
+                --show-linked-cluster-upgrade
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist.
+
diff --git a/gcloud/alpha/container/hub/clusterupgrade/help b/gcloud/alpha/container/hub/clusterupgrade/help
new file mode 100644
index 000000000..581adcd42
--- /dev/null
+++ b/gcloud/alpha/container/hub/clusterupgrade/help
@@ -0,0 +1,37 @@
+NAME
+    gcloud alpha container hub clusterupgrade - configure the Fleet
+        clusterupgrade feature
+
+SYNOPSIS
+    gcloud alpha container hub clusterupgrade COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This fleet feature is used to configure fleet-based rollout
+    sequencing.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        (ALPHA) Create the clusterupgrade feature for a fleet within a given
+        project.
+
+     describe
+        (ALPHA) Describe the clusterupgrade feature for a fleet within a given
+        project.
+
+     update
+        (ALPHA) Update the clusterupgrade feature for a fleet within a given
+        project.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist.
+
diff --git a/gcloud/alpha/container/hub/clusterupgrade/update b/gcloud/alpha/container/hub/clusterupgrade/update
new file mode 100644
index 000000000..0ccf5d1a0
--- /dev/null
+++ b/gcloud/alpha/container/hub/clusterupgrade/update
@@ -0,0 +1,115 @@
+NAME
+    gcloud alpha container hub clusterupgrade update - update the
+        clusterupgrade feature for a fleet within a given project
+
+SYNOPSIS
+    gcloud alpha container hub clusterupgrade update
+        [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING]
+        [--remove-upgrade-soaking-overrides
+          | --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE
+          --upgrade-selector=[name=NAME],[version=VERSION]]
+        [--reset-upstream-fleet | --upstream-fleet=UPSTREAM_FLEET]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) Update the clusterupgrade feature for a fleet within a given
+    project.
+
+FLAGS
+     --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING
+        Configures the default soaking duration for each upgrade propagating
+        through the current fleet to become "COMPLETE". Soaking begins after
+        all clusters in the fleet are on the target version, or after 30 days
+        if all cluster upgrades are not complete. Once an upgrade state becomes
+        "COMPLETE", it will automatically be propagated to the downstream
+        fleet. Max is 30 days.
+
+        To configure Rollout Sequencing for a fleet, this attribute must be
+        set. To do this while specifying a default soaking duration of 7 days,
+        run:
+
+            $ gcloud alpha container hub clusterupgrade update \
+                --default-upgrade-soaking=7d
+
+     At most one of these can be specified:
+
+       --remove-upgrade-soaking-overrides
+          Removes soaking time overrides for all upgrades propagating through
+          the current fleet. Consequently, all upgrades will follow the soak
+          time configured by --default-upgrade-soaking until new overrides are
+          configured with --add_upgrade_soaking_override and
+          --upgrade_selector.
+
+          To remove all configured soaking time overrides, run:
+
+              $ gcloud alpha container hub clusterupgrade update \
+                  --remove-upgrade-soaking-overrides
+
+       Upgrade soaking override.
+
+           Defines a specific soaking time override for a particular upgrade
+           propagating through the current fleet that supercedes the default
+           soaking duration configured by `--default-upgrade-soaking`.
+
+           To set an upgrade soaking override of 12 hours for the upgrade with
+           name, `k8s_control_plane`, and version, `1.23.1-gke.1000`, run:
+
+           $ gcloud alpha container hub clusterupgrade update               \
+           --add-upgrade-soaking-override=12h               \
+           --upgrade-selector=name="k8s_control_plane",\
+           version="1.23.1-gke.1000"
+
+         --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE
+            Overrides the soaking time for a particular upgrade name and
+            version propagating through the current fleet. Set soaking to 0
+            days to bypass soaking and fast-forward the upgrade to the
+            downstream fleet.
+
+            See $ gcloud topic datetimes for information on duration formats.
+
+            This flag argument must be specified if any of the other arguments
+            in this group are specified.
+
+         --upgrade-selector=[name=NAME],[version=VERSION]
+            Name and version of the upgrade to be overridden where version is a
+            full GKE version. Currently, name can be either k8s_control_plane
+            or k8s_node.
+
+            This flag argument must be specified if any of the other arguments
+            in this group are specified.
+
+     At most one of these can be specified:
+
+       --reset-upstream-fleet
+          Clears the relationship between the current fleet and its upstream
+          fleet in the rollout sequence.
+
+          To remove the link between the current fleet and its upstream fleet,
+          run:
+
+              $ gcloud alpha container hub clusterupgrade update \
+                  --reset-upstream-fleet
+
+       --upstream-fleet=UPSTREAM_FLEET
+          The upstream fleet. GKE will finish upgrades on the upstream fleet
+          before applying the same upgrades to the current fleet.
+
+          To configure the upstream fleet, run:
+
+              $ gcloud alpha container hub clusterupgrade update             \
+                  --upstream-fleet={upstream_fleet}
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist.
+
diff --git a/gcloud/alpha/container/hub/create b/gcloud/alpha/container/hub/create
new file mode 100644
index 000000000..85eb5503e
--- /dev/null
+++ b/gcloud/alpha/container/hub/create
@@ -0,0 +1,79 @@
+NAME
+    gcloud alpha container hub create - create a fleet
+
+SYNOPSIS
+    gcloud alpha container hub create [--async] [--display-name=DISPLAY_NAME]
+        [--labels=[KEY=VALUE,...]]
+        [--security-posture=SECURITY_POSTURE
+          --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project specified already has a fleet.
+      ▪ The active account does not have permission to access the given
+        project.
+
+EXAMPLES
+    To create a fleet in project example-foo-bar-1 with display name my-fleet,
+    run:
+
+        $ gcloud alpha container hub create --display-name=my-fleet \
+            --project=example-foo-bar-1
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --display-name=DISPLAY_NAME
+        Display name of the fleet to be created (optional). 4-30 characters,
+        alphanumeric and [ '"!-] only.
+
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     Default cluster configurations to apply across the fleet.
+
+       Security posture config.
+
+         --security-posture=SECURITY_POSTURE
+            To apply basic security posture to the clusters of the fleet,
+
+                $ gcloud alpha container hub create --security-posture=basic
+
+            SECURITY_POSTURE must be one of: disabled, basic, enterprise.
+
+         --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING
+            To apply basic vulnerability scanning to the clusters of the fleet,
+
+                $ gcloud alpha container hub create \
+                    --workload-vulnerability-scanning=disabled
+
+            WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, basic,
+            enterprise.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub create
+
+        $ gcloud beta container hub create
+
diff --git a/gcloud/alpha/container/hub/delete b/gcloud/alpha/container/hub/delete
new file mode 100644
index 000000000..4a27145b9
--- /dev/null
+++ b/gcloud/alpha/container/hub/delete
@@ -0,0 +1,41 @@
+NAME
+    gcloud alpha container hub delete - delete a fleet
+
+SYNOPSIS
+    gcloud alpha container hub delete [--async] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project specified already has a fleet.
+      ▪ The active account does not have permission to access the given
+        project.
+
+EXAMPLES
+    To delete a fleet in project example-foo-bar-1, run:
+
+        $ gcloud alpha container hub delete --project=example-foo-bar-1
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub delete
+
+        $ gcloud beta container hub delete
+
diff --git a/gcloud/alpha/container/hub/describe b/gcloud/alpha/container/hub/describe
new file mode 100644
index 000000000..5eb89bb11
--- /dev/null
+++ b/gcloud/alpha/container/hub/describe
@@ -0,0 +1,36 @@
+NAME
+    gcloud alpha container hub describe - show fleet info
+
+SYNOPSIS
+    gcloud alpha container hub describe [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project specified does not have a fleet.
+      ▪ The active account does not have permission to access the given
+        project.
+
+EXAMPLES
+    To print metadata for the fleet in project example-foo-bar-1, run:
+
+        $ gcloud alpha container hub describe --project=example-foo-bar-1
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub describe
+
+        $ gcloud beta container hub describe
+
diff --git a/gcloud/alpha/container/hub/help b/gcloud/alpha/container/hub/help
index 44b36d45f..8546cf144 100644
--- a/gcloud/alpha/container/hub/help
+++ b/gcloud/alpha/container/hub/help
@@ -48,6 +48,9 @@ GROUPS
      cloudrun
         (ALPHA) Manage the CloudRun feature.
 
+     clusterupgrade
+        (ALPHA) Configure the Fleet clusterupgrade feature.
+
      config-management
         (ALPHA) Manage Config Management Feature.
 
@@ -89,6 +92,24 @@ GROUPS
      service-directory
         (ALPHA) Manage the Service Directory Feature.
 
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        (ALPHA) Create a fleet.
+
+     delete
+        (ALPHA) Delete a fleet.
+
+     describe
+        (ALPHA) Show fleet info.
+
+     list
+        (ALPHA) List fleets visible to the user in an organization.
+
+     update
+        (ALPHA) Update a fleet.
+
 NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
diff --git a/gcloud/alpha/container/hub/list b/gcloud/alpha/container/hub/list
new file mode 100644
index 000000000..9ec262e9b
--- /dev/null
+++ b/gcloud/alpha/container/hub/list
@@ -0,0 +1,75 @@
+NAME
+    gcloud alpha container hub list - list fleets visible to the user in an
+        organization
+
+SYNOPSIS
+    gcloud alpha container hub list [--organization=ORGANIZATION_ID]
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The org or project specified does not exist.
+      ▪ The user does not have access to the project specified.
+
+EXAMPLES
+    The following command lists fleets in organization 12345:
+
+        $ gcloud alpha container hub list --organization=12345
+
+COMMONLY USED FLAGS
+     --organization=ORGANIZATION_ID
+        ID (number) for the organization to list fleets from. If neither
+        --organization nor --project are provided, defaults to the organization
+        of the active project.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub list
+
+        $ gcloud beta container hub list
+
diff --git a/gcloud/alpha/container/hub/memberships/bindings/create b/gcloud/alpha/container/hub/memberships/bindings/create
index 754177485..d25ce4914 100644
--- a/gcloud/alpha/container/hub/memberships/bindings/create
+++ b/gcloud/alpha/container/hub/memberships/bindings/create
@@ -99,7 +99,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub memberships bindings create
 
         $ gcloud beta container hub memberships bindings create
 
diff --git a/gcloud/alpha/container/hub/memberships/bindings/delete b/gcloud/alpha/container/hub/memberships/bindings/delete
index e75575f09..a08520aaf 100644
--- a/gcloud/alpha/container/hub/memberships/bindings/delete
+++ b/gcloud/alpha/container/hub/memberships/bindings/delete
@@ -82,7 +82,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub memberships bindings delete
 
         $ gcloud beta container hub memberships bindings delete
 
diff --git a/gcloud/alpha/container/hub/memberships/bindings/describe b/gcloud/alpha/container/hub/memberships/bindings/describe
index 03a8916bf..704eb9f76 100644
--- a/gcloud/alpha/container/hub/memberships/bindings/describe
+++ b/gcloud/alpha/container/hub/memberships/bindings/describe
@@ -82,7 +82,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub memberships bindings describe
 
         $ gcloud beta container hub memberships bindings describe
 
diff --git a/gcloud/alpha/container/hub/memberships/bindings/help b/gcloud/alpha/container/hub/memberships/bindings/help
index 0e0d312c8..cec858516 100644
--- a/gcloud/alpha/container/hub/memberships/bindings/help
+++ b/gcloud/alpha/container/hub/memberships/bindings/help
@@ -42,7 +42,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub memberships bindings
 
         $ gcloud beta container hub memberships bindings
 
diff --git a/gcloud/alpha/container/hub/memberships/bindings/list b/gcloud/alpha/container/hub/memberships/bindings/list
index 9017aa69d..467b7a742 100644
--- a/gcloud/alpha/container/hub/memberships/bindings/list
+++ b/gcloud/alpha/container/hub/memberships/bindings/list
@@ -81,7 +81,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub memberships bindings list
 
         $ gcloud beta container hub memberships bindings list
 
diff --git a/gcloud/alpha/container/hub/memberships/bindings/update b/gcloud/alpha/container/hub/memberships/bindings/update
index 76367d8f7..fbe0f6a41 100644
--- a/gcloud/alpha/container/hub/memberships/bindings/update
+++ b/gcloud/alpha/container/hub/memberships/bindings/update
@@ -123,7 +123,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub memberships bindings update
 
         $ gcloud beta container hub memberships bindings update
 
diff --git a/gcloud/alpha/container/hub/scopes/add-iam-policy-binding b/gcloud/alpha/container/hub/scopes/add-iam-policy-binding
new file mode 100644
index 000000000..ad6d133c0
--- /dev/null
+++ b/gcloud/alpha/container/hub/scopes/add-iam-policy-binding
@@ -0,0 +1,91 @@
+NAME
+    gcloud alpha container hub scopes add-iam-policy-binding - add IAM policy
+        binding to a Fleet Scope
+
+SYNOPSIS
+    gcloud alpha container hub scopes add-iam-policy-binding SCOPE
+        --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) Add an IAM policy binding to the IAM policy of a Fleet Scope. One
+    binding consists of a member, and a role.
+
+EXAMPLES
+    To add an IAM policy binding for the role of 'roles/gkehub.scopeUser' for
+    the user 'test-user@gmail.com' with scope 'my-scope', run:
+
+        $ gcloud alpha container hub scopes add-iam-policy-binding \
+            my-scope --member='user:test-user@gmail.com' \
+            --role='roles/gkehub.scopeUser'
+
+    See https://cloud.google.com/iam/docs/managing-policies for details of
+    policy role and member types.
+
+POSITIONAL ARGUMENTS
+     Scope resource - The scope for which to add IAM policy binding to. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     To set the location attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+REQUIRED FLAGS
+     --member=PRINCIPAL
+        The principal to add the binding for. Should be of the form
+        user|group|serviceAccount:email or domain:domain.
+
+        Examples: user:test-user@gmail.com, group:admins@example.com,
+        serviceAccount:test123@example.domain.com, or
+        domain:example.domain.com.
+
+        Some resources also accept the following special values:
+        ◆ allUsers - Special identifier that represents anyone who is on the
+          internet, with or without a Google account.
+        ◆ allAuthenticatedUsers - Special identifier that represents anyone
+          who is authenticated with a Google account or a service account.
+
+     --role=ROLE
+        Role name to assign to the principal. The role name is the complete
+        path of a predefined role, such as roles/logging.viewer, or the role ID
+        for a custom role, such as
+        organizations/{ORGANIZATION_ID}/roles/logging.viewer.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1alpha API. The full documentation for this
+    API can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub scopes add-iam-policy-binding
+
+        $ gcloud beta container hub scopes add-iam-policy-binding
+
diff --git a/gcloud/alpha/container/hub/scopes/create b/gcloud/alpha/container/hub/scopes/create
index 696c88cce..45e1e167f 100644
--- a/gcloud/alpha/container/hub/scopes/create
+++ b/gcloud/alpha/container/hub/scopes/create
@@ -7,7 +7,8 @@ SYNOPSIS
         [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING
           --upstream-scope=UPSTREAM_SCOPE
           --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE
-          --upgrade-selector=[UPGRADE_SELECTOR,...]] [GCLOUD_WIDE_FLAG ...]
+          --upgrade-selector=[name=NAME],[version=VERSION]]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (ALPHA) Create a Fleet Scope resource.
@@ -113,7 +114,7 @@ FLAGS
             This flag argument must be specified if any of the other arguments
             in this group are specified.
 
-         --upgrade-selector=[UPGRADE_SELECTOR,...]
+         --upgrade-selector=[name=NAME],[version=VERSION]
             Name and version of the upgrade to be overridden where version is a
             full GKE version. Currently, name can be either k8s_control_plane
             or k8s_node.
@@ -138,7 +139,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub scopes create
 
         $ gcloud beta container hub scopes create
 
diff --git a/gcloud/alpha/container/hub/scopes/delete b/gcloud/alpha/container/hub/scopes/delete
index c7ee3a4f0..4dd5a2a1a 100644
--- a/gcloud/alpha/container/hub/scopes/delete
+++ b/gcloud/alpha/container/hub/scopes/delete
@@ -73,7 +73,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub scopes delete
 
         $ gcloud beta container hub scopes delete
 
diff --git a/gcloud/alpha/container/hub/scopes/describe b/gcloud/alpha/container/hub/scopes/describe
index 58945d151..91775c298 100644
--- a/gcloud/alpha/container/hub/scopes/describe
+++ b/gcloud/alpha/container/hub/scopes/describe
@@ -95,7 +95,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub scopes describe
 
         $ gcloud beta container hub scopes describe
 
diff --git a/gcloud/alpha/container/hub/scopes/get-iam-policy b/gcloud/alpha/container/hub/scopes/get-iam-policy
new file mode 100644
index 000000000..17685f99c
--- /dev/null
+++ b/gcloud/alpha/container/hub/scopes/get-iam-policy
@@ -0,0 +1,90 @@
+NAME
+    gcloud alpha container hub scopes get-iam-policy - get the IAM policy for a
+        Fleet Scope
+
+SYNOPSIS
+    gcloud alpha container hub scopes get-iam-policy SCOPE
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command gets the IAM policy for a scope.
+
+EXAMPLES
+    To print the IAM policy for a given scope, run:
+
+        $ gcloud alpha container hub scopes get-iam-policy my-scope
+
+POSITIONAL ARGUMENTS
+     Scope resource - The scope for which to display the IAM policy. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     To set the location attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1alpha API. The full documentation for this
+    API can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub scopes get-iam-policy
+
+        $ gcloud beta container hub scopes get-iam-policy
+
diff --git a/gcloud/alpha/container/hub/scopes/help b/gcloud/alpha/container/hub/scopes/help
index 055e382b4..b655b759c 100644
--- a/gcloud/alpha/container/hub/scopes/help
+++ b/gcloud/alpha/container/hub/scopes/help
@@ -12,9 +12,22 @@ GCLOUD WIDE FLAGS
 
     Run $ gcloud help for details.
 
+GROUPS
+    GROUP is one of the following:
+
+     namespaces
+        (ALPHA) Fleet namespaces are the fleet equivalent of k8s cluster
+        namespaces.
+
+     rbacrolebindings
+        (ALPHA) Fleet scope RBAC RoleBindings for permissions.
+
 COMMANDS
     COMMAND is one of the following:
 
+     add-iam-policy-binding
+        (ALPHA) Add IAM policy binding to a Fleet Scope.
+
      create
         (ALPHA) Create a new fleet scope.
 
@@ -24,9 +37,15 @@ COMMANDS
      describe
         (ALPHA) Describe a fleet scope.
 
+     get-iam-policy
+        (ALPHA) Get the IAM policy for a Fleet Scope.
+
      list
         (ALPHA) List fleet scopes.
 
+     remove-iam-policy-binding
+        (ALPHA) Remove IAM policy binding of a Fleet Scope.
+
      update
         (ALPHA) Update a scope.
 
@@ -34,7 +53,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub scopes
 
         $ gcloud beta container hub scopes
 
diff --git a/gcloud/alpha/container/hub/scopes/list b/gcloud/alpha/container/hub/scopes/list
index 9be85c93f..634786bb8 100644
--- a/gcloud/alpha/container/hub/scopes/list
+++ b/gcloud/alpha/container/hub/scopes/list
@@ -63,7 +63,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub scopes list
 
         $ gcloud beta container hub scopes list
 
diff --git a/gcloud/alpha/container/hub/scopes/namespaces/create b/gcloud/alpha/container/hub/scopes/namespaces/create
new file mode 100644
index 000000000..0ee6c3137
--- /dev/null
+++ b/gcloud/alpha/container/hub/scopes/namespaces/create
@@ -0,0 +1,92 @@
+NAME
+    gcloud alpha container hub scopes namespaces create - create a fleet
+        namespace
+
+SYNOPSIS
+    gcloud alpha container hub scopes namespaces create
+        (NAMESPACE : --scope=SCOPE) [--labels=[KEY=VALUE,...]]
+        [--namespace-labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project has a fleet namespace with the same name.
+      ▪ The caller does not have permission to access the given project.
+
+EXAMPLES
+    To create a fleet namespace with name NAMESPACE in the active project, run:
+
+        $ gcloud alpha container hub scopes namespaces create NAMESPACE
+
+    To create a fleet namespace in fleet scope SCOPE in project PROJECT_ID with
+    name NAMESPACE, run:
+
+        $ gcloud alpha container hub scopes namespaces create NAMESPACE \
+            --scope=SCOPE --project=PROJECT_ID
+
+POSITIONAL ARGUMENTS
+     Namespace resource - The group of arguments defining the Fleet Namespace.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       NAMESPACE
+          ID of the namespace or fully qualified identifier for the namespace.
+
+          To set the namespace attribute:
+          ▸ provide the argument NAMESPACE on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --scope=SCOPE
+          the
+
+          To set the scope attribute:
+          ▸ provide the argument NAMESPACE on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+FLAGS
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     --namespace-labels=[KEY=VALUE,...]
+        List of namespace-level label KEY=VALUE pairs to add.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub scopes namespaces create
+
+        $ gcloud beta container hub scopes namespaces create
+
diff --git a/gcloud/alpha/container/hub/scopes/namespaces/delete b/gcloud/alpha/container/hub/scopes/namespaces/delete
new file mode 100644
index 000000000..4f2e426c0
--- /dev/null
+++ b/gcloud/alpha/container/hub/scopes/namespaces/delete
@@ -0,0 +1,79 @@
+NAME
+    gcloud alpha container hub scopes namespaces delete - delete a fleet
+        namespace
+
+SYNOPSIS
+    gcloud alpha container hub scopes namespaces delete
+        (NAMESPACE : --scope=SCOPE) [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The namespace specified does not exist.
+      ▪ The caller does not have permission to access the given project or
+        namespace.
+
+EXAMPLES
+    To delete fleet namespace NAMESPACE in the active project:
+
+        $ gcloud alpha container hub scopes namespaces delete NAMESPACE
+
+    To delete fleet namespace NAMESPACE in project PROJECT_ID:
+
+        $ gcloud alpha container hub scopes namespaces delete NAMESPACE \
+            --project=PROJECT_ID
+
+POSITIONAL ARGUMENTS
+     Namespace resource - The group of arguments defining the Fleet Namespace.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       NAMESPACE
+          ID of the namespace or fully qualified identifier for the namespace.
+
+          To set the namespace attribute:
+          ▸ provide the argument NAMESPACE on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --scope=SCOPE
+          the
+
+          To set the scope attribute:
+          ▸ provide the argument NAMESPACE on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub scopes namespaces delete
+
+        $ gcloud beta container hub scopes namespaces delete
+
diff --git a/gcloud/alpha/container/hub/scopes/namespaces/describe b/gcloud/alpha/container/hub/scopes/namespaces/describe
new file mode 100644
index 000000000..6455eb135
--- /dev/null
+++ b/gcloud/alpha/container/hub/scopes/namespaces/describe
@@ -0,0 +1,79 @@
+NAME
+    gcloud alpha container hub scopes namespaces describe - show fleet
+        namespace info
+
+SYNOPSIS
+    gcloud alpha container hub scopes namespaces describe
+        (NAMESPACE : --scope=SCOPE) [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The namespace specified does not exist in the project.
+      ▪ The caller does not have permission to access the project or
+        namespace.
+
+EXAMPLES
+    To print metadata for the namespace NAMESPACE in the active project, run:
+
+        $ gcloud alpha container hub scopes namespaces describe NAMESPACE
+
+    To print metadata for the namespace NAMESPACE in project PROJECT_ID, run:
+
+        $ gcloud alpha container hub scopes namespaces describe NAMESPACE \
+            --project=PROJECT_ID
+
+POSITIONAL ARGUMENTS
+     Namespace resource - The group of arguments defining the Fleet Namespace.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       NAMESPACE
+          ID of the namespace or fully qualified identifier for the namespace.
+
+          To set the namespace attribute:
+          ▸ provide the argument NAMESPACE on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --scope=SCOPE
+          the
+
+          To set the scope attribute:
+          ▸ provide the argument NAMESPACE on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub scopes namespaces describe
+
+        $ gcloud beta container hub scopes namespaces describe
+
diff --git a/gcloud/alpha/container/hub/scopes/namespaces/get-credentials b/gcloud/alpha/container/hub/scopes/namespaces/get-credentials
new file mode 100644
index 000000000..875724eed
--- /dev/null
+++ b/gcloud/alpha/container/hub/scopes/namespaces/get-credentials
@@ -0,0 +1,62 @@
+NAME
+    gcloud alpha container hub scopes namespaces get-credentials - fetch
+        credentials for a membership with a particular namespace
+
+SYNOPSIS
+    gcloud alpha container hub scopes namespaces get-credentials NAMESPACE
+        [--membership=MEMBERSHIP] [--membership-location=MEMBERSHIP_LOCATION]
+        [--set-namespace-in-config=SET_NAMESPACE_IN_CONFIG]
+        [GCLOUD_WIDE_FLAG ...]
+
+EXAMPLES
+    Get the Connect Gateway kubeconfig for global membership MEMBERSHIP, using
+    namespace NAMESPACE in the config:
+
+        $ gcloud alpha container hub scopes namespaces get-credentials \
+            NAMESPACE --membership=MEMBERSHIP --membership-location=global \
+            --set-namespace-in-config=true
+
+    Get the Connect Gateway kubeconfig for global membership MEMBERSHIP:
+
+        $ gcloud alpha container hub scopes namespaces get-credentials \
+            NAMESPACE --membership=MEMBERSHIP --membership-location=global
+
+POSITIONAL ARGUMENTS
+     NAMESPACE
+        Name of the namespace for which to get access to memberships.
+
+FLAGS
+     --membership=MEMBERSHIP
+        Membership ID to get credentials from. If not provided, a prompt will
+        offer a list of memberships in the fleet.
+
+     --membership-location=MEMBERSHIP_LOCATION
+        The location of the membership resource, e.g. us-central1. If not
+        specified, defaults to global.
+
+     --set-namespace-in-config=SET_NAMESPACE_IN_CONFIG
+        If true, the default namespace for the context in the generated
+        kubeconfig will be set to the Fleet namespace (i.e. the name given as
+        the positional argument in this command).
+
+        Otherwise, no default namespace will be set, functioning the same as
+        gcloud container fleet memberships get-credentials.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub scopes namespaces get-credentials
+
+        $ gcloud beta container hub scopes namespaces get-credentials
+
diff --git a/gcloud/alpha/container/hub/scopes/namespaces/help b/gcloud/alpha/container/hub/scopes/namespaces/help
new file mode 100644
index 000000000..785286bcb
--- /dev/null
+++ b/gcloud/alpha/container/hub/scopes/namespaces/help
@@ -0,0 +1,56 @@
+NAME
+    gcloud alpha container hub scopes namespaces - fleet namespaces are the
+        fleet equivalent of k8s cluster namespaces
+
+SYNOPSIS
+    gcloud alpha container hub scopes namespaces COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command group allows for manipulation of fleet namespaces.
+
+EXAMPLES
+    Manage fleet namespaces:
+
+        $ gcloud alpha container hub scopes namespaces --help
+
+    Manage RBAC RoleBindings in a fleet namespace:
+
+        $ gcloud alpha container hub scopes namespaces rbacrolebindings \
+            --help
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        (ALPHA) Create a fleet namespace.
+
+     delete
+        (ALPHA) Delete a fleet namespace.
+
+     describe
+        (ALPHA) Show fleet namespace info.
+
+     get-credentials
+        (ALPHA) Fetch credentials for a membership with a particular namespace.
+
+     list
+        (ALPHA) List fleet namespaces in a project.
+
+     update
+        (ALPHA) Update a fleet namespace.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub scopes namespaces
+
+        $ gcloud beta container hub scopes namespaces
+
diff --git a/gcloud/alpha/container/hub/scopes/namespaces/list b/gcloud/alpha/container/hub/scopes/namespaces/list
new file mode 100644
index 000000000..7ad4c94c2
--- /dev/null
+++ b/gcloud/alpha/container/hub/scopes/namespaces/list
@@ -0,0 +1,98 @@
+NAME
+    gcloud alpha container hub scopes namespaces list - list fleet namespaces
+        in a project
+
+SYNOPSIS
+    gcloud alpha container hub scopes namespaces list --scope=SCOPE
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The user does not have access to the project specified.
+
+EXAMPLES
+    The following command lists namespaces in the active project:
+
+        $ gcloud alpha container hub scopes namespaces list
+
+    The following command lists namespaces in project PROJECT_ID:
+
+        $ gcloud alpha container hub scopes namespaces list \
+            --project=PROJECT_ID
+
+REQUIRED FLAGS
+     Scope resource - The group of arguments defining the Fleet Scope. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --scope on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --scope on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       --scope=SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument --scope on the command line.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub scopes namespaces list
+
+        $ gcloud beta container hub scopes namespaces list
+
diff --git a/gcloud/alpha/container/hub/scopes/namespaces/update b/gcloud/alpha/container/hub/scopes/namespaces/update
new file mode 100644
index 000000000..3a3ff2ebd
--- /dev/null
+++ b/gcloud/alpha/container/hub/scopes/namespaces/update
@@ -0,0 +1,143 @@
+NAME
+    gcloud alpha container hub scopes namespaces update - update a fleet
+        namespace
+
+SYNOPSIS
+    gcloud alpha container hub scopes namespaces update
+        (NAMESPACE : --scope=SCOPE) [--update-labels=[KEY=VALUE,...]]
+        [--update-namespace-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]]
+        [--clear-namespace-labels | --remove-namespace-labels=[KEY,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The fleet namespace does not exist in the project.
+      ▪ The caller does not have permission to access the project or
+        namespace.
+
+EXAMPLES
+    To update the namespace NAMESPACE in the active project:
+
+        $ gcloud alpha container hub scopes namespaces update NAMESPACE
+
+    To update the namespace NAMESPACE in project PROJECT_ID:
+
+        $ gcloud alpha container hub scopes namespaces update NAMESPACE \
+            --project=PROJECT_ID
+
+POSITIONAL ARGUMENTS
+     Namespace resource - The group of arguments defining the Fleet Namespace.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       NAMESPACE
+          ID of the namespace or fully qualified identifier for the namespace.
+
+          To set the namespace attribute:
+          ▸ provide the argument NAMESPACE on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --scope=SCOPE
+          the
+
+          To set the scope attribute:
+          ▸ provide the argument NAMESPACE on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+FLAGS
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     --update-namespace-labels=[KEY=VALUE,...]
+        List of namespace-level label KEY=VALUE pairs to update in the cluster
+        namespace. If a label exists, its value is modified. Otherwise, a new
+        label is' created.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud alpha container hub scopes namespaces update --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud alpha container hub scopes namespaces update \
+                --clear-labels --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+     At most one of these can be specified:
+
+       --clear-namespace-labels
+          Remove all namespace-level labels from the cluster namespace. If
+          --update-namespace-labels is also specified then
+          --clear-namespace-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud alpha container hub scopes namespaces update \
+                namespace_name --clear-namespace-labels
+
+          To remove all existing namespace-level labels and create two new
+          labels, foo and baz:
+
+              $ gcloud alpha container hub scopes namespaces update \
+                namespace_name --clear-namespace-labels \
+                --update-namespace-labels foo=bar,baz=qux
+
+       --remove-namespace-labels=[KEY,...]
+          List of namespace-level label keys to remove in the cluster
+          namespace. If a label does not exist it is silently ignored. If
+          --update-namespace-labels is also specified then
+          --update-namespace-labels is applied first.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub scopes namespaces update
+
+        $ gcloud beta container hub scopes namespaces update
+
diff --git a/gcloud/alpha/container/hub/scopes/rbacrolebindings/create b/gcloud/alpha/container/hub/scopes/rbacrolebindings/create
new file mode 100644
index 000000000..9a5bf86dc
--- /dev/null
+++ b/gcloud/alpha/container/hub/scopes/rbacrolebindings/create
@@ -0,0 +1,108 @@
+NAME
+    gcloud alpha container hub scopes rbacrolebindings create - create an RBAC
+        RoleBinding
+
+SYNOPSIS
+    gcloud alpha container hub scopes rbacrolebindings create
+        (NAME : --location=LOCATION --scope=SCOPE) --role=ROLE
+        (--group=GROUP | --user=USER) [--labels=[KEY=VALUE,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The RBAC RoleBinding already exists.
+      ▪ The caller does not have permission to access the given scope.
+
+EXAMPLES
+    To create an admin RBAC RoleBinding RBRB in scope SCOPE for user
+    person@google.com, run:
+
+        $ gcloud alpha container hub scopes rbacrolebindings create RBRB \
+            --scope=SCOPE --role=admin --user=person@google.com
+
+    To create a viewer RBAC RoleBinding RBRB in scope SCOPE for group
+    people@google.com, run:
+
+        $ gcloud alpha container hub scopes rbacrolebindings create RBRB \
+            --scope=SCOPE --role=viewer --group=people@google.com
+
+POSITIONAL ARGUMENTS
+     Rbacrolebinding resource - The group of arguments defining an
+     RBACRoleBinding. The arguments in this group can be used to specify the
+     attributes of this resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAME on the command line with a fully specified
+        name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       NAME
+          ID of the rbacrolebinding or fully qualified identifier for the
+          rbacrolebinding.
+
+          To set the rbacrolebinding attribute:
+          ▸ provide the argument NAME on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the rbacrolebinding.
+
+          To set the location attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --scope=SCOPE
+          Name of the rbacrolebinding.
+
+          To set the scope attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+REQUIRED FLAGS
+     --role=ROLE
+        Role to assign. ROLE must be one of: admin, edit, view.
+
+     Exactly one of these must be specified:
+
+       --group=GROUP
+          Group for the RoleBinding.
+
+       --user=USER
+          User for the RoleBinding.
+
+OPTIONAL FLAGS
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub scopes rbacrolebindings create
+
+        $ gcloud beta container hub scopes rbacrolebindings create
+
diff --git a/gcloud/alpha/container/hub/scopes/rbacrolebindings/delete b/gcloud/alpha/container/hub/scopes/rbacrolebindings/delete
new file mode 100644
index 000000000..d77f89d98
--- /dev/null
+++ b/gcloud/alpha/container/hub/scopes/rbacrolebindings/delete
@@ -0,0 +1,78 @@
+NAME
+    gcloud alpha container hub scopes rbacrolebindings delete - delete a fleet
+        scope RBAC RoleBinding
+
+SYNOPSIS
+    gcloud alpha container hub scopes rbacrolebindings delete
+        (NAME : --location=LOCATION --scope=SCOPE) [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The RoleBinding specified does not exist.
+      ▪ The caller does not have permission to access the given RoleBinding.
+
+EXAMPLES
+    To delete RBAC RoleBinding RBRB in scope SCOPE in the active project:
+
+        $ gcloud alpha container hub scopes rbacrolebindings delete RBRB \
+            --scope=SCOPE
+
+POSITIONAL ARGUMENTS
+     Rbacrolebinding resource - The group of arguments defining an
+     RBACRoleBinding. The arguments in this group can be used to specify the
+     attributes of this resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAME on the command line with a fully specified
+        name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       NAME
+          ID of the rbacrolebinding or fully qualified identifier for the
+          rbacrolebinding.
+
+          To set the rbacrolebinding attribute:
+          ▸ provide the argument NAME on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the rbacrolebinding.
+
+          To set the location attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --scope=SCOPE
+          Name of the rbacrolebinding.
+
+          To set the scope attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub scopes rbacrolebindings delete
+
+        $ gcloud beta container hub scopes rbacrolebindings delete
+
diff --git a/gcloud/alpha/container/hub/scopes/rbacrolebindings/describe b/gcloud/alpha/container/hub/scopes/rbacrolebindings/describe
new file mode 100644
index 000000000..66fe648fa
--- /dev/null
+++ b/gcloud/alpha/container/hub/scopes/rbacrolebindings/describe
@@ -0,0 +1,78 @@
+NAME
+    gcloud alpha container hub scopes rbacrolebindings describe - show fleet
+        scope RBAC RoleBinding information
+
+SYNOPSIS
+    gcloud alpha container hub scopes rbacrolebindings describe
+        (NAME : --location=LOCATION --scope=SCOPE) [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The RoleBinding specified does not exist in the project.
+      ▪ The caller does not have permission to access the RoleBinding.
+
+EXAMPLES
+    To print metadata for RBAC RoleBinding RBRB in the scope SCOPE, run:
+
+        $ gcloud alpha container hub scopes rbacrolebindings describe RBRB \
+            --scope=SCOPE
+
+POSITIONAL ARGUMENTS
+     Rbacrolebinding resource - The group of arguments defining an
+     RBACRoleBinding. The arguments in this group can be used to specify the
+     attributes of this resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAME on the command line with a fully specified
+        name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       NAME
+          ID of the rbacrolebinding or fully qualified identifier for the
+          rbacrolebinding.
+
+          To set the rbacrolebinding attribute:
+          ▸ provide the argument NAME on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the rbacrolebinding.
+
+          To set the location attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --scope=SCOPE
+          Name of the rbacrolebinding.
+
+          To set the scope attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub scopes rbacrolebindings describe
+
+        $ gcloud beta container hub scopes rbacrolebindings describe
+
diff --git a/gcloud/alpha/container/hub/scopes/rbacrolebindings/help b/gcloud/alpha/container/hub/scopes/rbacrolebindings/help
new file mode 100644
index 000000000..8ab62d2fa
--- /dev/null
+++ b/gcloud/alpha/container/hub/scopes/rbacrolebindings/help
@@ -0,0 +1,50 @@
+NAME
+    gcloud alpha container hub scopes rbacrolebindings - fleet scope RBAC
+        RoleBindings for permissions
+
+SYNOPSIS
+    gcloud alpha container hub scopes rbacrolebindings COMMAND
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command group allows for manipulation of fleet namespace RBAC
+    RoleBindings.
+
+EXAMPLES
+    Manage RBAC RoleBindings:
+
+        $ gcloud alpha container hub scopes rbacrolebindings --help
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        (ALPHA) Create an RBAC RoleBinding.
+
+     delete
+        (ALPHA) Delete a fleet scope RBAC RoleBinding.
+
+     describe
+        (ALPHA) Show fleet scope RBAC RoleBinding information.
+
+     list
+        (ALPHA) List RBAC RoleBindings in a fleet scope.
+
+     update
+        (ALPHA) Update a fleet scope RBAC RoleBinding.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub scopes rbacrolebindings
+
+        $ gcloud beta container hub scopes rbacrolebindings
+
diff --git a/gcloud/alpha/container/hub/scopes/rbacrolebindings/list b/gcloud/alpha/container/hub/scopes/rbacrolebindings/list
new file mode 100644
index 000000000..83b1e2722
--- /dev/null
+++ b/gcloud/alpha/container/hub/scopes/rbacrolebindings/list
@@ -0,0 +1,75 @@
+NAME
+    gcloud alpha container hub scopes rbacrolebindings list - list RBAC
+        RoleBindings in a fleet scope
+
+SYNOPSIS
+    gcloud alpha container hub scopes rbacrolebindings list --scope=SCOPE
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The scope specified does not exist.
+      ▪ The user does not have access to the specified scope.
+
+EXAMPLES
+    The following command lists RBAC RoleBindings in scope SCOPE in project
+    PROJECT_ID:
+
+        $ gcloud alpha container hub scopes rbacrolebindings list \
+            --scope=SCOPE --project=PROJECT_ID
+
+REQUIRED FLAGS
+     --scope=SCOPE
+        Name of the fleet scope to list RBAC RoleBindings from.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub scopes rbacrolebindings list
+
+        $ gcloud beta container hub scopes rbacrolebindings list
+
diff --git a/gcloud/alpha/container/hub/scopes/rbacrolebindings/update b/gcloud/alpha/container/hub/scopes/rbacrolebindings/update
new file mode 100644
index 000000000..c08fcce5a
--- /dev/null
+++ b/gcloud/alpha/container/hub/scopes/rbacrolebindings/update
@@ -0,0 +1,131 @@
+NAME
+    gcloud alpha container hub scopes rbacrolebindings update - update a fleet
+        scope RBAC RoleBinding
+
+SYNOPSIS
+    gcloud alpha container hub scopes rbacrolebindings update
+        (NAME : --location=LOCATION --scope=SCOPE) [--role=ROLE]
+        [--update-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]]
+        [--group=GROUP | --user=USER] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The RoleBinding does not exist in the project.
+      ▪ The caller does not have permission to access the RoleBinding.
+
+EXAMPLES
+    To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to
+    the viewer role:
+
+        $ gcloud alpha container hub scopes rbacrolebindings update RBRB \
+            --scope=SCOPE --role=viewer
+
+    To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to
+    the user someone@google.com:
+
+        $ gcloud alpha container hub scopes rbacrolebindings update RBRB \
+            --scope=SCOPE --user=someone@google.com
+
+POSITIONAL ARGUMENTS
+     Rbacrolebinding resource - The group of arguments defining an
+     RBACRoleBinding. The arguments in this group can be used to specify the
+     attributes of this resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAME on the command line with a fully specified
+        name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       NAME
+          ID of the rbacrolebinding or fully qualified identifier for the
+          rbacrolebinding.
+
+          To set the rbacrolebinding attribute:
+          ▸ provide the argument NAME on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the rbacrolebinding.
+
+          To set the location attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --scope=SCOPE
+          Name of the rbacrolebinding.
+
+          To set the scope attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+FLAGS
+     --role=ROLE
+        Role for the RBACRoleBinding to update to. ROLE must be one of: admin,
+        edit, view.
+
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud alpha container hub scopes rbacrolebindings update \
+                --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud alpha container hub scopes rbacrolebindings update \
+                --clear-labels --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+     At most one of these can be specified:
+
+       --group=GROUP
+          Group for the RBACRoleBinding to update to.
+
+       --user=USER
+          User for the RBACRoleBinding to update to.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub scopes rbacrolebindings update
+
+        $ gcloud beta container hub scopes rbacrolebindings update
+
diff --git a/gcloud/alpha/container/hub/scopes/remove-iam-policy-binding b/gcloud/alpha/container/hub/scopes/remove-iam-policy-binding
new file mode 100644
index 000000000..670b68898
--- /dev/null
+++ b/gcloud/alpha/container/hub/scopes/remove-iam-policy-binding
@@ -0,0 +1,92 @@
+NAME
+    gcloud alpha container hub scopes remove-iam-policy-binding - remove IAM
+        policy binding of a Fleet Scope
+
+SYNOPSIS
+    gcloud alpha container hub scopes remove-iam-policy-binding SCOPE
+        --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) Remove an IAM policy binding from the IAM policy of a scope. One
+    binding consists of a member, and a role.
+
+EXAMPLES
+    To remove an IAM policy binding for the role of 'roles/gkehub.scopeUser'
+    for the user 'test-user@gmail.com' with scope 'my-scope', run:
+
+        $ gcloud alpha container hub scopes remove-iam-policy-binding \
+            my-scope --member='user:test-user@gmail.com' \
+            --role='roles/gkehub.scopeUser'
+
+    See https://cloud.google.com/iam/docs/managing-policies for details of
+    policy role and member types.
+
+POSITIONAL ARGUMENTS
+     Scope resource - The scope for which to remove IAM policy binding from.
+     This represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     To set the location attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+REQUIRED FLAGS
+     --member=PRINCIPAL
+        The principal to remove the binding for. Should be of the form
+        user|group|serviceAccount:email or domain:domain.
+
+        Examples: user:test-user@gmail.com, group:admins@example.com,
+        serviceAccount:test123@example.domain.com, or
+        domain:example.domain.com.
+
+        Deleted principals have an additional deleted: prefix and a ?uid=UID
+        suffix, where UID is a unique identifier for the principal. Example:
+        deleted:user:test-user@gmail.com?uid=123456789012345678901.
+
+        Some resources also accept the following special values:
+        ◆ allUsers - Special identifier that represents anyone who is on the
+          internet, with or without a Google account.
+        ◆ allAuthenticatedUsers - Special identifier that represents anyone
+          who is authenticated with a Google account or a service account.
+
+     --role=ROLE
+        The role to remove the principal from.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1alpha API. The full documentation for this
+    API can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub scopes remove-iam-policy-binding
+
+        $ gcloud beta container hub scopes remove-iam-policy-binding
+
diff --git a/gcloud/alpha/container/hub/scopes/update b/gcloud/alpha/container/hub/scopes/update
index a414648bb..3e28f2af5 100644
--- a/gcloud/alpha/container/hub/scopes/update
+++ b/gcloud/alpha/container/hub/scopes/update
@@ -10,8 +10,9 @@ SYNOPSIS
         [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING
           --remove-upgrade-soaking-overrides
           | --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE
-          --upgrade-selector=[UPGRADE_SELECTOR,...] --reset-upstream-scope
-          | --upstream-scope=UPSTREAM_SCOPE] [GCLOUD_WIDE_FLAG ...]
+          --upgrade-selector=[name=NAME],[version=VERSION]
+          --reset-upstream-scope | --upstream-scope=UPSTREAM_SCOPE]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (ALPHA) Update an existing Fleet Scope.
@@ -174,7 +175,7 @@ FLAGS
               This flag argument must be specified if any of the other
               arguments in this group are specified.
 
-           --upgrade-selector=[UPGRADE_SELECTOR,...]
+           --upgrade-selector=[name=NAME],[version=VERSION]
               Name and version of the upgrade to be overridden where version is
               a full GKE version. Currently, name can be either
               k8s_control_plane or k8s_node.
@@ -221,7 +222,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub scopes update
 
         $ gcloud beta container hub scopes update
 
diff --git a/gcloud/alpha/container/hub/update b/gcloud/alpha/container/hub/update
new file mode 100644
index 000000000..5e7a626d1
--- /dev/null
+++ b/gcloud/alpha/container/hub/update
@@ -0,0 +1,101 @@
+NAME
+    gcloud alpha container hub update - update a fleet
+
+SYNOPSIS
+    gcloud alpha container hub update [--async] [--display-name=DISPLAY_NAME]
+        [--update-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]]
+        [--security-posture=SECURITY_POSTURE
+          --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project specified already has a fleet.
+      ▪ The active account does not have permission to access the given
+        project.
+
+EXAMPLES
+    To update the display name of the fleet in project example-foo-bar-1 to
+    updated-name, run:
+
+        $ gcloud alpha container hub update --display-name=updated-name \
+            --project=example-foo-bar-1
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --display-name=DISPLAY_NAME
+        Display name of the fleet to be created (optional). 4-30 characters,
+        alphanumeric and [ '"!-] only.
+
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud alpha container hub update --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud alpha container hub update --clear-labels \
+                --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+     Default cluster configurations to apply across the fleet.
+
+       Security posture config.
+
+         --security-posture=SECURITY_POSTURE
+            To apply basic security posture to the clusters of the fleet,
+
+                $ gcloud alpha container hub update --security-posture=basic
+
+            SECURITY_POSTURE must be one of: disabled, basic, enterprise.
+
+         --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING
+            To apply basic vulnerability scanning to the clusters of the fleet,
+
+                $ gcloud alpha container hub update \
+                    --workload-vulnerability-scanning=disabled
+
+            WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, basic,
+            enterprise.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud container hub update
+
+        $ gcloud beta container hub update
+
diff --git a/gcloud/alpha/dataplex/datascans/create/data-profile b/gcloud/alpha/dataplex/datascans/create/data-profile
index 3c2cea8a4..c9e43e386 100644
--- a/gcloud/alpha/dataplex/datascans/create/data-profile
+++ b/gcloud/alpha/dataplex/datascans/create/data-profile
@@ -11,6 +11,7 @@ SYNOPSIS
         [--labels=[KEY=VALUE,...]] [--async | --validate-only]
         [--data-profile-spec-file=DATA_PROFILE_SPEC_FILE
           | --exclude-field-names=EXCLUDE_FIELD_NAMES
+          --export-results-table=EXPORT_RESULTS_TABLE
           --include-field-names=INCLUDE_FIELD_NAMES
           --row-filter=ROW_FILTER --sampling-percent=SAMPLING_PERCENT]
         [--incremental-field=INCREMENTAL_FIELD --on-demand=ON_DEMAND
@@ -25,7 +26,7 @@ EXAMPLES
     To create a data profile scan data-profile-datascan in project test-project
     located in us-central1, run:
 
-        $ gcloud alpha dataplex datascans create data-profile data-profile \
+        $ gcloud alpha dataplex datascans create data-profile \
             data-profile-datascan --project=test-project \
             --location=us-central1
 
@@ -119,6 +120,12 @@ OPTIONAL FLAGS
             respective fields will be excluded from data profile, regardless of
             the fields specified in the --include-field-names flag.
 
+         --export-results-table=EXPORT_RESULTS_TABLE
+            path to the resource table to export data profile scan results, of
+            the form:
+            //bigquery.googleapis.com/projects/{project_number}/datasets/{dataset_id}/tables/{table_id}.
+            The table will be created if not present.
+
          --include-field-names=INCLUDE_FIELD_NAMES
             Names of the fields to include in data profile. If not specified,
             all fields at the time of profile scan job execution are included.
diff --git a/gcloud/alpha/dataplex/datascans/create/data-quality b/gcloud/alpha/dataplex/datascans/create/data-quality
index 8bab73e5a..b0db7f039 100644
--- a/gcloud/alpha/dataplex/datascans/create/data-quality
+++ b/gcloud/alpha/dataplex/datascans/create/data-quality
@@ -22,7 +22,7 @@ EXAMPLES
     To create a data quality scan data-quality-datascan in project test-project
     located in us-central1 with data spec file data-quality-spec.json, run:
 
-        $ gcloud alpha dataplex datascans create data-quality data-quality \
+        $ gcloud alpha dataplex datascans create data-quality \
             data-quality-datascan --project=test-project \
             --location=us-central1 \
             --data-quality-spec-file="data-quality-spec.json"
diff --git a/gcloud/alpha/dataplex/datascans/update/data-profile b/gcloud/alpha/dataplex/datascans/update/data-profile
index 4b7d671f2..2f5522176 100644
--- a/gcloud/alpha/dataplex/datascans/update/data-profile
+++ b/gcloud/alpha/dataplex/datascans/update/data-profile
@@ -22,7 +22,7 @@ EXAMPLES
     To update description of a data profile scan data-profile-datascan in
     project test-project located in us-central1, run:
 
-        $ gcloud alpha dataplex datascans update data-profile data-profile \
+        $ gcloud alpha dataplex datascans update data-profile \
             data-profile-datascan --project=test-project \
             --location=us-central1 --description="Description is updated."
 
diff --git a/gcloud/alpha/dataplex/datascans/update/data-quality b/gcloud/alpha/dataplex/datascans/update/data-quality
index 7ba5df3d3..b76b6e08f 100644
--- a/gcloud/alpha/dataplex/datascans/update/data-quality
+++ b/gcloud/alpha/dataplex/datascans/update/data-quality
@@ -19,7 +19,7 @@ EXAMPLES
     To update description of a data quality scan data-quality-datascan in
     project test-project located in us-central1, run:
 
-        $ gcloud alpha dataplex datascans update data-quality data-quality \
+        $ gcloud alpha dataplex datascans update data-quality \
             data-quality-datascan --project=test-project \
             --location=us-central1 --description="Description is updated."
 
diff --git a/gcloud/alpha/dataplex/tasks/create b/gcloud/alpha/dataplex/tasks/create
index 57df4309f..5fb55a26e 100644
--- a/gcloud/alpha/dataplex/tasks/create
+++ b/gcloud/alpha/dataplex/tasks/create
@@ -4,7 +4,7 @@ NAME
 SYNOPSIS
     gcloud alpha dataplex tasks create (TASK : --lake=LAKE --location=LOCATION)
         (--execution-service-account=EXECUTION_SERVICE_ACCOUNT
-          : --execution-args=EXECUTION_ARGS
+          : --execution-args=[KEY=VALUE,...]
           --execution-project=EXECUTION_PROJECT --kms-key=KMS_KEY
           --max-job-execution-lifetime=MAX_JOB_EXECUTION_LIFETIME)
         ([--notebook=NOTEBOOK
@@ -12,9 +12,9 @@ SYNOPSIS
           --notebook-file-uris=[NOTEBOOK_FILE_URIS,...]
           --notebook-batch-executors-count=NOTEBOOK_BATCH_EXECUTORS_COUNT
           --notebook-batch-max-executors-count=NOTEBOOK_BATCH_MAX_EXECUTORS_COUNT --notebook-container-image=NOTEBOOK_CONTAINER_IMAGE --notebook-container-image-java-jars=[NOTEBOOK_CONTAINER_IMAGE_JAVA_JARS,
-          ...]
-          --notebook-container-image-properties=NOTEBOOK_CONTAINER_IMAGE_PROPERTIES --notebook-vpc-network-tags=[NOTEBOOK_VPC_NETWORK_TAGS,
-          ...] --notebook-vpc-network-name=NOTEBOOK_VPC_NETWORK_NAME
+          ...] --notebook-container-image-properties=[KEY=VALUE,...]
+          --notebook-vpc-network-tags=[NOTEBOOK_VPC_NETWORK_TAGS,...]
+          --notebook-vpc-network-name=NOTEBOOK_VPC_NETWORK_NAME
           | --notebook-vpc-sub-network-name=NOTEBOOK_VPC_SUB_NETWORK_NAME]
           | [(--spark-main-class=SPARK_MAIN_CLASS
           | --spark-main-jar-file-uri=SPARK_MAIN_JAR_FILE_URI
@@ -27,7 +27,7 @@ SYNOPSIS
           --batch-max-executors-count=BATCH_MAX_EXECUTORS_COUNT
           --container-image=CONTAINER_IMAGE
           --container-image-java-jars=[CONTAINER_IMAGE_JAVA_JARS,...]
-          --container-image-properties=CONTAINER_IMAGE_PROPERTIES
+          --container-image-properties=[KEY=VALUE,...]
           --container-image-python-packages=[CONTAINER_IMAGE_PYTHON_PACKAGES,
           ...] --vpc-network-tags=[VPC_NETWORK_TAGS,...]
           --vpc-network-name=VPC_NETWORK_NAME
@@ -127,7 +127,7 @@ REQUIRED FLAGS
           This flag argument must be specified if any of the other arguments in
           this group are specified.
 
-       --execution-args=EXECUTION_ARGS
+       --execution-args=[KEY=VALUE,...]
           The arguments to pass to the task. The args can use placeholders of
           the format ${placeholder} as part of key/value string. These will be
           interpolated before passing the args to the driver. Currently
@@ -198,7 +198,7 @@ REQUIRED FLAGS
               Cloud Storage URIs to Jar binaries. For example,
               gs://bucket-name/my/path/to/file.jar
 
-           --notebook-container-image-properties=NOTEBOOK_CONTAINER_IMAGE_PROPERTIES
+           --notebook-container-image-properties=[KEY=VALUE,...]
               The properties to set on daemon config files. Property keys are
               specified in prefix:property format, for example
               core:hadoop.tmp.dir. For more information, see Cluster properties
@@ -278,7 +278,7 @@ REQUIRED FLAGS
               Cloud Storage URIs to Jar binaries. For example,
               gs://bucket-name/my/path/to/file.jar
 
-           --container-image-properties=CONTAINER_IMAGE_PROPERTIES
+           --container-image-properties=[KEY=VALUE,...]
               The properties to set on daemon config files. Property keys are
               specified in prefix:property format, for example
               core:hadoop.tmp.dir. For more information, see Cluster properties
diff --git a/gcloud/alpha/dataplex/tasks/update b/gcloud/alpha/dataplex/tasks/update
index 1b5f0befb..cda637dd0 100644
--- a/gcloud/alpha/dataplex/tasks/update
+++ b/gcloud/alpha/dataplex/tasks/update
@@ -6,7 +6,7 @@ SYNOPSIS
         [--async] [--description=DESCRIPTION] [--display-name=DISPLAY_NAME]
         [--update-labels=[KEY=VALUE,...]]
         [--clear-labels | --remove-labels=[KEY,...]]
-        [--execution-args=EXECUTION_ARGS --execution-project=EXECUTION_PROJECT
+        [--execution-args=[KEY=VALUE,...] --execution-project=EXECUTION_PROJECT
           --execution-service-account=EXECUTION_SERVICE_ACCOUNT
           --kms-key=KMS_KEY
           --max-job-execution-lifetime=MAX_JOB_EXECUTION_LIFETIME]
@@ -15,9 +15,9 @@ SYNOPSIS
           --notebook-file-uris=[NOTEBOOK_FILE_URIS,...]
           --notebook-batch-executors-count=NOTEBOOK_BATCH_EXECUTORS_COUNT
           --notebook-batch-max-executors-count=NOTEBOOK_BATCH_MAX_EXECUTORS_COUNT --notebook-container-image=NOTEBOOK_CONTAINER_IMAGE --notebook-container-image-java-jars=[NOTEBOOK_CONTAINER_IMAGE_JAVA_JARS,
-          ...]
-          --notebook-container-image-properties=NOTEBOOK_CONTAINER_IMAGE_PROPERTIES --notebook-vpc-network-tags=[NOTEBOOK_VPC_NETWORK_TAGS,
-          ...] --notebook-vpc-network-name=NOTEBOOK_VPC_NETWORK_NAME
+          ...] --notebook-container-image-properties=[KEY=VALUE,...]
+          --notebook-vpc-network-tags=[NOTEBOOK_VPC_NETWORK_TAGS,...]
+          --notebook-vpc-network-name=NOTEBOOK_VPC_NETWORK_NAME
           | --notebook-vpc-sub-network-name=NOTEBOOK_VPC_SUB_NETWORK_NAME
           | --spark-archive-uris=[SPARK_ARCHIVE_URIS,...]
           --spark-file-uris=[SPARK_FILE_URIS,...]
@@ -25,7 +25,7 @@ SYNOPSIS
           --batch-max-executors-count=BATCH_MAX_EXECUTORS_COUNT
           --container-image=CONTAINER_IMAGE
           --container-image-java-jars=[CONTAINER_IMAGE_JAVA_JARS,...]
-          --container-image-properties=CONTAINER_IMAGE_PROPERTIES
+          --container-image-properties=[KEY=VALUE,...]
           --container-image-python-packages=[CONTAINER_IMAGE_PYTHON_PACKAGES,
           ...] --vpc-network-tags=[VPC_NETWORK_TAGS,...]
           --vpc-network-name=VPC_NETWORK_NAME
@@ -132,7 +132,7 @@ FLAGS
 
      Spec related to how a task is executed.
 
-       --execution-args=EXECUTION_ARGS
+       --execution-args=[KEY=VALUE,...]
           The arguments to pass to the task. The args can use placeholders of
           the format ${placeholder} as part of key/value string. These will be
           interpolated before passing the args to the driver. Currently
@@ -202,7 +202,7 @@ FLAGS
               Cloud Storage URIs to Jar binaries. For example,
               gs://bucket-name/my/path/to/file.jar
 
-           --notebook-container-image-properties=NOTEBOOK_CONTAINER_IMAGE_PROPERTIES
+           --notebook-container-image-properties=[KEY=VALUE,...]
               Override to common configuration of open source components
               installed on the Dataproc cluster. The properties to set on
               daemon config files. Property keys are specified in
@@ -256,7 +256,7 @@ FLAGS
               Cloud Storage URIs to Jar binaries. For example,
               gs://bucket-name/my/path/to/file.jar
 
-           --container-image-properties=CONTAINER_IMAGE_PROPERTIES
+           --container-image-properties=[KEY=VALUE,...]
               Override to common configuration of open source components
               installed on the Dataproc cluster. The properties to set on
               daemon config files. Property keys are specified in
diff --git a/gcloud/alpha/dataproc/clusters/create b/gcloud/alpha/dataproc/clusters/create
index 359745753..1a620ada7 100644
--- a/gcloud/alpha/dataproc/clusters/create
+++ b/gcloud/alpha/dataproc/clusters/create
@@ -57,7 +57,8 @@ SYNOPSIS
         [--image=IMAGE | --image-version=VERSION]
         [--kerberos-config-file=KERBEROS_CONFIG_FILE | --enable-kerberos
           --kerberos-root-principal-password-uri=KERBEROS_ROOT_PRINCIPAL_PASSWORD_URI [--kerberos-kms-key=KERBEROS_KMS_KEY : --kerberos-kms-key-keyring=KERBEROS_KMS_KEY_KEYRING --kerberos-kms-key-location=KERBEROS_KMS_KEY_LOCATION --kerberos-kms-key-project=KERBEROS_KMS_KEY_PROJECT]]
-        [--single-node | --num-secondary-workers=NUM_SECONDARY_WORKERS
+        [--single-node | --min-num-workers=MIN_NUM_WORKERS
+          --num-secondary-workers=NUM_SECONDARY_WORKERS
           --num-workers=NUM_WORKERS
           --secondary-worker-type=TYPE; default="preemptible"]
         [GCLOUD_WIDE_FLAG ...]
@@ -759,6 +760,10 @@ FLAGS
 
        Multi-node cluster flags
 
+         --min-num-workers=MIN_NUM_WORKERS
+            The minimum number of workers nodes to provision for cluster create
+            operations to succeed.
+
          --num-secondary-workers=NUM_SECONDARY_WORKERS
             The number of secondary worker nodes in the cluster.
 
diff --git a/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster b/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster
index 46c4c3af7..b023359a3 100644
--- a/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster
+++ b/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster
@@ -45,7 +45,8 @@ SYNOPSIS
           --tags=TAG,[TAG,...] --network=NETWORK | --subnet=SUBNET
           --reservation=RESERVATION
           --reservation-affinity=RESERVATION_AFFINITY; default="any"]
-        [--single-node | --num-secondary-workers=NUM_SECONDARY_WORKERS
+        [--single-node | --min-num-workers=MIN_NUM_WORKERS
+          --num-secondary-workers=NUM_SECONDARY_WORKERS
           --num-workers=NUM_WORKERS
           --secondary-worker-type=TYPE; default="preemptible"]
         [GCLOUD_WIDE_FLAG ...]
@@ -635,6 +636,10 @@ FLAGS
 
        Multi-node cluster flags
 
+         --min-num-workers=MIN_NUM_WORKERS
+            The minimum number of workers nodes to provision for cluster create
+            operations to succeed.
+
          --num-secondary-workers=NUM_SECONDARY_WORKERS
             The number of secondary worker nodes in the cluster.
 
diff --git a/gcloud/alpha/dialogflow/intents/create b/gcloud/alpha/dialogflow/intents/create
index da2d310fd..6fc8d0571 100644
--- a/gcloud/alpha/dialogflow/intents/create
+++ b/gcloud/alpha/dialogflow/intents/create
@@ -4,9 +4,8 @@ NAME
 
 SYNOPSIS
     gcloud alpha dialogflow intents create --display-name=DISPLAY_NAME
-        [--is-fallback] [--no-ml-enabled]
-        [--other-properties=[OTHER_PROPERTIES,...]] [--priority=PRIORITY]
-        [--responses=[RESPONSES,...]]
+        [--is-fallback] [--no-ml-enabled] [--other-properties=[KEY=VALUE,...]]
+        [--priority=PRIORITY] [--responses=[RESPONSES,...]]
         [--training-phrases=[TRAINING_PHRASES,...]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -32,7 +31,7 @@ OPTIONAL FLAGS
         If true, enable machine learning for the intent. Enabled by default,
         use --no-ml-enabled to disable.
 
-     --other-properties=[OTHER_PROPERTIES,...]
+     --other-properties=[KEY=VALUE,...]
         Map containing other properties to set on the intent.
 
         For more information on available properties, see:
diff --git a/gcloud/alpha/dialogflow/intents/update b/gcloud/alpha/dialogflow/intents/update
index 9f893119b..18c3903bf 100644
--- a/gcloud/alpha/dialogflow/intents/update
+++ b/gcloud/alpha/dialogflow/intents/update
@@ -4,7 +4,7 @@ NAME
 
 SYNOPSIS
     gcloud alpha dialogflow intents update INTENT [--is-fallback]
-        [--no-ml-enabled] [--other-properties=[OTHER_PROPERTIES,...]]
+        [--no-ml-enabled] [--other-properties=[KEY=VALUE,...]]
         [--priority=PRIORITY] [--responses=[RESPONSES,...]]
         [--training-phrases=[TRAINING_PHRASES,...]] [GCLOUD_WIDE_FLAG ...]
 
@@ -45,7 +45,7 @@ FLAGS
         If true, enable machine learning for the intent. Enabled by default,
         use --no-ml-enabled to disable.
 
-     --other-properties=[OTHER_PROPERTIES,...]
+     --other-properties=[KEY=VALUE,...]
         Map containing other properties to set on the intent.
 
         Only the properties specified will be updated.
diff --git a/gcloud/alpha/edge-cache/keysets/create b/gcloud/alpha/edge-cache/keysets/create
index 197f2f197..ffcb34f72 100644
--- a/gcloud/alpha/edge-cache/keysets/create
+++ b/gcloud/alpha/edge-cache/keysets/create
@@ -3,9 +3,10 @@ NAME
 
 SYNOPSIS
     gcloud alpha edge-cache keysets create (KEYSET : --location=LOCATION)
-        [--async] [--description=DESCRIPTION] [--labels=KEY=VALUE]
-        [--public-key=PUBLIC_KEY]
-        [--validation-shared-key=VALIDATION_SHARED_KEY] [GCLOUD_WIDE_FLAG ...]
+        [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]]
+        [--public-key=[id=ID],[managed=MANAGED],[value=VALUE]]
+        [--validation-shared-key=[secret_version=SECRET_VERSION]]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (ALPHA) Create a new EdgeCacheKeyset resource.
@@ -56,10 +57,10 @@ FLAGS
      --description=DESCRIPTION
         Human-readable description of the resource.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of KEY=VALUE labels to attach to this resource.
 
-     --public-key=PUBLIC_KEY
+     --public-key=[id=ID],[managed=MANAGED],[value=VALUE]
         Set of public keys to use for validating signed requests, when
         associated with a route. This flag can be repeated to create a Keyset
         with multiple public keys.
@@ -91,7 +92,7 @@ FLAGS
 
         At least one of public-key or validation-shared-key must be specified.
 
-     --validation-shared-key=VALIDATION_SHARED_KEY
+     --validation-shared-key=[secret_version=SECRET_VERSION]
         An ordered list of shared keys to use for validating signed requests.
 
         To create a validation shared key pointing to a Secret Manager secret
diff --git a/gcloud/alpha/edge-cache/keysets/update b/gcloud/alpha/edge-cache/keysets/update
index cd12ee488..c2275e489 100644
--- a/gcloud/alpha/edge-cache/keysets/update
+++ b/gcloud/alpha/edge-cache/keysets/update
@@ -3,9 +3,10 @@ NAME
 
 SYNOPSIS
     gcloud alpha edge-cache keysets update (KEYSET : --location=LOCATION)
-        [--async] [--description=DESCRIPTION] [--labels=KEY=VALUE]
-        [--public-key=PUBLIC_KEY]
-        [--validation-shared-key=VALIDATION_SHARED_KEY] [GCLOUD_WIDE_FLAG ...]
+        [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]]
+        [--public-key=[id=ID],[managed=MANAGED],[value=VALUE]]
+        [--validation-shared-key=[secret_version=SECRET_VERSION]]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (ALPHA) Update an existing EdgeCacheKeyset resource.
@@ -69,10 +70,10 @@ FLAGS
      --description=DESCRIPTION
         Human-readable description of the resource.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of KEY=VALUE labels to attach to this resource.
 
-     --public-key=PUBLIC_KEY
+     --public-key=[id=ID],[managed=MANAGED],[value=VALUE]
         Set of public keys to use for validating signed requests, when
         associated with a route. This flag can be repeated to create a Keyset
         with multiple public keys.
@@ -104,7 +105,7 @@ FLAGS
 
         At least one of public-key or validation-shared-key must be specified.
 
-     --validation-shared-key=VALIDATION_SHARED_KEY
+     --validation-shared-key=[secret_version=SECRET_VERSION]
         An ordered list of shared keys to use for validating signed requests.
 
         To create a validation shared key pointing to a Secret Manager secret
diff --git a/gcloud/alpha/edge-cache/origins/create b/gcloud/alpha/edge-cache/origins/create
index 6e0efc3f7..d463a0da4 100644
--- a/gcloud/alpha/edge-cache/origins/create
+++ b/gcloud/alpha/edge-cache/origins/create
@@ -4,7 +4,7 @@ NAME
 SYNOPSIS
     gcloud alpha edge-cache origins create (ORIGIN : --location=LOCATION)
         --origin-address=ORIGIN_ADDRESS [--async] [--description=DESCRIPTION]
-        [--failover-origin=FAILOVER_ORIGIN] [--labels=KEY=VALUE]
+        [--failover-origin=FAILOVER_ORIGIN] [--labels=[KEY=VALUE,...]]
         [--max-attempts=MAX_ATTEMPTS] [--port=PORT] [--protocol=PROTOCOL]
         [--response-timeout=RESPONSE_TIMEOUT]
         [--retry-conditions=[RETRY_CONDITIONS,...]] [GCLOUD_WIDE_FLAG ...]
@@ -89,7 +89,7 @@ OPTIONAL FLAGS
         The value of timeout.maxAttemptsTimeout dictates the timeout across all
         origins.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of KEY=VALUE labels to attach to this resource.
 
      --max-attempts=MAX_ATTEMPTS
diff --git a/gcloud/alpha/edge-cache/origins/update b/gcloud/alpha/edge-cache/origins/update
index 337f9d1d0..130609381 100644
--- a/gcloud/alpha/edge-cache/origins/update
+++ b/gcloud/alpha/edge-cache/origins/update
@@ -4,7 +4,7 @@ NAME
 SYNOPSIS
     gcloud alpha edge-cache origins update (ORIGIN : --location=LOCATION)
         [--async] [--description=DESCRIPTION]
-        [--failover-origin=FAILOVER_ORIGIN] [--labels=KEY=VALUE]
+        [--failover-origin=FAILOVER_ORIGIN] [--labels=[KEY=VALUE,...]]
         [--max-attempts=MAX_ATTEMPTS] [--origin-address=ORIGIN_ADDRESS]
         [--port=PORT] [--protocol=PROTOCOL]
         [--response-timeout=RESPONSE_TIMEOUT]
@@ -73,7 +73,7 @@ FLAGS
         The value of timeout.maxAttemptsTimeout dictates the timeout across all
         origins.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of KEY=VALUE labels to attach to this resource.
 
      --max-attempts=MAX_ATTEMPTS
diff --git a/gcloud/alpha/edge-cache/services/update b/gcloud/alpha/edge-cache/services/update
index 8ee91d618..28a066681 100644
--- a/gcloud/alpha/edge-cache/services/update
+++ b/gcloud/alpha/edge-cache/services/update
@@ -7,7 +7,7 @@ SYNOPSIS
         [--async] [--description=DESCRIPTION]
         [--edge-security-policy=EDGE_SECURITY_POLICY]
         [--edge-ssl-certificate=[EDGE_SSL_CERTIFICATE,...]] [--enable-logging]
-        [--labels=KEY=VALUE] [--logging-sample-rate=LOGGING_SAMPLE_RATE]
+        [--labels=[KEY=VALUE,...]] [--logging-sample-rate=LOGGING_SAMPLE_RATE]
         [--require-tls] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -86,7 +86,7 @@ FLAGS
 
         Defaults to false.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of KEY=VALUE labels to attach to this resource.
 
      --logging-sample-rate=LOGGING_SAMPLE_RATE
diff --git a/gcloud/alpha/filestore/backups/create b/gcloud/alpha/filestore/backups/create
index f9ed0092d..454d81955 100644
--- a/gcloud/alpha/filestore/backups/create
+++ b/gcloud/alpha/filestore/backups/create
@@ -4,7 +4,7 @@ NAME
 SYNOPSIS
     gcloud alpha filestore backups create BACKUP --file-share=FILE_SHARE
         --instance=INSTANCE --instance-zone=INSTANCE_ZONE --region=REGION
-        [--async] [--description=DESCRIPTION] [--labels=KEY=VALUE]
+        [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]]
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -51,7 +51,7 @@ OPTIONAL FLAGS
      --description=DESCRIPTION
         Description for the backup. Limit: 2048 characters.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
 GCLOUD WIDE FLAGS
diff --git a/gcloud/alpha/filestore/snapshots/create b/gcloud/alpha/filestore/snapshots/create
index 24b2c7de2..bd51b27b8 100644
--- a/gcloud/alpha/filestore/snapshots/create
+++ b/gcloud/alpha/filestore/snapshots/create
@@ -4,7 +4,7 @@ NAME
 SYNOPSIS
     gcloud alpha filestore snapshots create SNAPSHOT --file-share=FILE_SHARE
         --instance=INSTANCE --instance-zone=INSTANCE_ZONE [--async]
-        [--labels=KEY=VALUE] [--region=REGION] [GCLOUD_WIDE_FLAG ...]
+        [--labels=[KEY=VALUE,...]] [--region=REGION] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (ALPHA) Take a Filestore snapshot of an instance file share.
@@ -50,7 +50,7 @@ OPTIONAL FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
      --region=REGION
diff --git a/gcloud/alpha/firestore/indexes/composite/create b/gcloud/alpha/firestore/indexes/composite/create
index 3a0868533..e9ca006b4 100644
--- a/gcloud/alpha/firestore/indexes/composite/create
+++ b/gcloud/alpha/firestore/indexes/composite/create
@@ -3,7 +3,9 @@ NAME
         index
 
 SYNOPSIS
-    gcloud alpha firestore indexes composite create --field-config=FIELD_CONFIG
+    gcloud alpha firestore indexes composite create
+        --field-config=[array-config=ARRAY-CONFIG],
+          [field-path=FIELD-PATH],[order=ORDER]
         (--collection-group=COLLECTION_GROUP : --database=DATABASE)
         [--api-scope=API_SCOPE; default="any-api"] [--async]
         [--query-scope=QUERY_SCOPE; default="collection"]
@@ -28,7 +30,7 @@ EXAMPLES
             --field-config=field-path=timestamp,order=descending
 
 REQUIRED FLAGS
-     --field-config=FIELD_CONFIG
+     --field-config=[array-config=ARRAY-CONFIG],[field-path=FIELD-PATH],[order=ORDER]
         Configuration for a field.
 
         This flag must be repeated to provide the ordered list of field
diff --git a/gcloud/alpha/firestore/indexes/fields/update b/gcloud/alpha/firestore/indexes/fields/update
index 0682dc0eb..838450841 100644
--- a/gcloud/alpha/firestore/indexes/fields/update
+++ b/gcloud/alpha/firestore/indexes/fields/update
@@ -5,8 +5,8 @@ NAME
 SYNOPSIS
     gcloud alpha firestore indexes fields update
         (FIELD : --collection-group=COLLECTION_GROUP --database=DATABASE)
-        (--clear-exemption | --disable-indexes | --index=KEY=VALUE) [--async]
-        [GCLOUD_WIDE_FLAG ...]
+        (--clear-exemption | --disable-indexes | --index=[KEY=VALUE,...])
+        [--async] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (ALPHA) Update the index configuration of the given field.
@@ -88,7 +88,7 @@ REQUIRED FLAGS
        --disable-indexes
           If provided, the field will no longer be indexed at all.
 
-       --index=KEY=VALUE
+       --index=[KEY=VALUE,...]
           An index for the field.
 
           This flag can be repeated to provide multiple indexes. Any existing
diff --git a/gcloud/alpha/healthcare/consent-stores/check-data-access b/gcloud/alpha/healthcare/consent-stores/check-data-access
index d5210cdc0..59124b1d3 100644
--- a/gcloud/alpha/healthcare/consent-stores/check-data-access
+++ b/gcloud/alpha/healthcare/consent-stores/check-data-access
@@ -5,7 +5,7 @@ NAME
 SYNOPSIS
     gcloud alpha healthcare consent-stores check-data-access
         (CONSENT_STORE : --dataset=DATASET --location=LOCATION)
-        --data-id=DATA_ID [--request-attributes=[REQUEST_ATTRIBUTES,...]]
+        --data-id=DATA_ID [--request-attributes=[KEY=VALUE,...]]
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -68,7 +68,7 @@ REQUIRED FLAGS
         The unique identifier of the data to check access for.
 
 OPTIONAL FLAGS
-     --request-attributes=[REQUEST_ATTRIBUTES,...]
+     --request-attributes=[KEY=VALUE,...]
         Comma-separated list of request attributes associated with this access
         request. Each attribute has the form "KEY=VALUE".
 
diff --git a/gcloud/alpha/healthcare/consent-stores/evaluate-user-consents b/gcloud/alpha/healthcare/consent-stores/evaluate-user-consents
index 73709aa0b..700d43c40 100644
--- a/gcloud/alpha/healthcare/consent-stores/evaluate-user-consents
+++ b/gcloud/alpha/healthcare/consent-stores/evaluate-user-consents
@@ -7,9 +7,9 @@ SYNOPSIS
         (CONSENT_STORE : --dataset=DATASET --location=LOCATION)
         --user-id=USER_ID [--consent-list=[CONSENT_LIST,...]]
         [--page-size=PAGE_SIZE] [--page-token=PAGE_TOKEN]
-        [--request-attributes=[REQUEST_ATTRIBUTES,...]]
-        [--resource-attributes=[RESOURCE_ATTRIBUTES,...]]
-        [--response-view=RESPONSE_VIEW] [GCLOUD_WIDE_FLAG ...]
+        [--request-attributes=[KEY=VALUE,...]]
+        [--resource-attributes=[KEY=VALUE,...]] [--response-view=RESPONSE_VIEW]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (ALPHA) Check if each matching user data mapping in the given Cloud
@@ -84,11 +84,11 @@ OPTIONAL FLAGS
      --page-token=PAGE_TOKEN
         Token to retrieve the next page of results.
 
-     --request-attributes=[REQUEST_ATTRIBUTES,...]
+     --request-attributes=[KEY=VALUE,...]
         Comma-separated list of request attributes associated with this access
         request. Each attribute has the form "KEY=VALUE".
 
-     --resource-attributes=[RESOURCE_ATTRIBUTES,...]
+     --resource-attributes=[KEY=VALUE,...]
         Comma-separated list of resource attributes associated with this access
         request. Each attribute has the form "KEY=VALUE". If no values are
         specified, then all data types are queried.
diff --git a/gcloud/alpha/healthcare/consent-stores/query-accessible-data b/gcloud/alpha/healthcare/consent-stores/query-accessible-data
index 503e8d84a..41d2644d8 100644
--- a/gcloud/alpha/healthcare/consent-stores/query-accessible-data
+++ b/gcloud/alpha/healthcare/consent-stores/query-accessible-data
@@ -5,10 +5,8 @@ NAME
 SYNOPSIS
     gcloud alpha healthcare consent-stores query-accessible-data
         (CONSENT_STORE : --dataset=DATASET --location=LOCATION)
-        --gcs-uri=GCS_URI [--async]
-        [--request-attributes=[REQUEST_ATTRIBUTES,...]]
-        [--resource-attributes=[RESOURCE_ATTRIBUTES,...]]
-        [GCLOUD_WIDE_FLAG ...]
+        --gcs-uri=GCS_URI [--async] [--request-attributes=[KEY=VALUE,...]]
+        [--resource-attributes=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (ALPHA) Queries all data IDs that are consented for a given use in the
@@ -79,11 +77,11 @@ OPTIONAL FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
-     --request-attributes=[REQUEST_ATTRIBUTES,...]
+     --request-attributes=[KEY=VALUE,...]
         Comma-separated list of request attributes associated with this access
         request. Each attribute has the form "KEY=VALUE".
 
-     --resource-attributes=[RESOURCE_ATTRIBUTES,...]
+     --resource-attributes=[KEY=VALUE,...]
         Comma-separated list of resources attributes associated with the type
         of data being requested. Each attribute has the form "KEY=VALUE". If no
         values are specified, then all data types are included in the output.
diff --git a/gcloud/alpha/iam/service-accounts/keys/create b/gcloud/alpha/iam/service-accounts/keys/create
index 4fc593279..41ef2dd99 100644
--- a/gcloud/alpha/iam/service-accounts/keys/create
+++ b/gcloud/alpha/iam/service-accounts/keys/create
@@ -1,6 +1,6 @@
 NAME
-    gcloud alpha iam service-accounts keys create - create a private key for a
-        service account
+    gcloud alpha iam service-accounts keys create - create a service account
+        key
 
 SYNOPSIS
     gcloud alpha iam service-accounts keys create OUTPUT-FILE
@@ -12,7 +12,7 @@ DESCRIPTION
     PERMISSION_DENIED error.
 
 EXAMPLES
-    To create a new private key for a service account, and save a copy of it
+    To create a new service account key and save the private portion of the key
     locally, run:
 
         $ gcloud alpha iam service-accounts keys create key.json \
diff --git a/gcloud/alpha/iam/service-accounts/keys/delete b/gcloud/alpha/iam/service-accounts/keys/delete
index 1e9aa7bb6..4a8b11941 100644
--- a/gcloud/alpha/iam/service-accounts/keys/delete
+++ b/gcloud/alpha/iam/service-accounts/keys/delete
@@ -1,6 +1,6 @@
 NAME
-    gcloud alpha iam service-accounts keys delete - delete a user-managed key
-        from a service account
+    gcloud alpha iam service-accounts keys delete - delete a service account
+        key
 
 SYNOPSIS
     gcloud alpha iam service-accounts keys delete KEY-ID
diff --git a/gcloud/alpha/iam/service-accounts/keys/disable b/gcloud/alpha/iam/service-accounts/keys/disable
index 456012e69..780f85381 100644
--- a/gcloud/alpha/iam/service-accounts/keys/disable
+++ b/gcloud/alpha/iam/service-accounts/keys/disable
@@ -1,13 +1,13 @@
 NAME
-    gcloud alpha iam service-accounts keys disable - disable a public key
-        related to an IAM service account
+    gcloud alpha iam service-accounts keys disable - disable a service account
+        key
 
 SYNOPSIS
     gcloud alpha iam service-accounts keys disable
         (IAM_KEY : --iam-account=IAM_ACCOUNT) [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (ALPHA) Disable a public key related to an IAM service account.
+    (ALPHA) Disable a service account key.
 
     If the service account does not exist, this command returns a
     PERMISSION_DENIED error.
diff --git a/gcloud/alpha/iam/service-accounts/keys/enable b/gcloud/alpha/iam/service-accounts/keys/enable
index 7daffb97b..93b44f62e 100644
--- a/gcloud/alpha/iam/service-accounts/keys/enable
+++ b/gcloud/alpha/iam/service-accounts/keys/enable
@@ -1,13 +1,13 @@
 NAME
-    gcloud alpha iam service-accounts keys enable - enable a public key related
-        to an IAM service account
+    gcloud alpha iam service-accounts keys enable - enable a service account
+        key
 
 SYNOPSIS
     gcloud alpha iam service-accounts keys enable
         (IAM_KEY : --iam-account=IAM_ACCOUNT) [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (ALPHA) Enable a public key related to an IAM service account.
+    (ALPHA) Enable a service account key.
 
     If the service account does not exist, this command returns a
     PERMISSION_DENIED error.
diff --git a/gcloud/alpha/iam/service-accounts/keys/help b/gcloud/alpha/iam/service-accounts/keys/help
index 785fdff14..923d1e6ad 100644
--- a/gcloud/alpha/iam/service-accounts/keys/help
+++ b/gcloud/alpha/iam/service-accounts/keys/help
@@ -23,16 +23,16 @@ COMMANDS
     COMMAND is one of the following:
 
      create
-        (ALPHA) Create a private key for a service account.
+        (ALPHA) Create a service account key.
 
      delete
-        (ALPHA) Delete a user-managed key from a service account.
+        (ALPHA) Delete a service account key.
 
      disable
-        (ALPHA) Disable a public key related to an IAM service account.
+        (ALPHA) Disable a service account key.
 
      enable
-        (ALPHA) Enable a public key related to an IAM service account.
+        (ALPHA) Enable a service account key.
 
      get-public-key
         (ALPHA) Get the public key for a service account key pair.
diff --git a/gcloud/alpha/iam/workforce-pools/providers/create-oidc b/gcloud/alpha/iam/workforce-pools/providers/create-oidc
index 7b9adf013..fa199546f 100644
--- a/gcloud/alpha/iam/workforce-pools/providers/create-oidc
+++ b/gcloud/alpha/iam/workforce-pools/providers/create-oidc
@@ -5,7 +5,7 @@ NAME
 SYNOPSIS
     gcloud alpha iam workforce-pools providers create-oidc
         (PROVIDER : --location=LOCATION --workforce-pool=WORKFORCE_POOL)
-        --attribute-mapping=[ATTRIBUTE_MAPPING,...] --client-id=CLIENT_ID
+        --attribute-mapping=[KEY=VALUE,...] --client-id=CLIENT_ID
         --issuer-uri=ISSUER_URI
         (--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR
           --web-sso-response-type=WEB_SSO_RESPONSE_TYPE
@@ -73,7 +73,7 @@ POSITIONAL ARGUMENTS
           ▸ provide the argument --workforce-pool on the command line.
 
 REQUIRED FLAGS
-     --attribute-mapping=[ATTRIBUTE_MAPPING,...]
+     --attribute-mapping=[KEY=VALUE,...]
         Maps claims from the authentication credentials issued by the Identity
         Provider into Google Cloud IAM attributes, e.g. subject, segment.
 
diff --git a/gcloud/alpha/iam/workforce-pools/providers/update-oidc b/gcloud/alpha/iam/workforce-pools/providers/update-oidc
index bc2e270b7..db4c88ae3 100644
--- a/gcloud/alpha/iam/workforce-pools/providers/update-oidc
+++ b/gcloud/alpha/iam/workforce-pools/providers/update-oidc
@@ -6,7 +6,7 @@ SYNOPSIS
     gcloud alpha iam workforce-pools providers update-oidc
         (PROVIDER : --location=LOCATION --workforce-pool=WORKFORCE_POOL)
         [--async] [--attribute-condition=ATTRIBUTE_CONDITION]
-        [--attribute-mapping=[ATTRIBUTE_MAPPING,...]] [--client-id=CLIENT_ID]
+        [--attribute-mapping=[KEY=VALUE,...]] [--client-id=CLIENT_ID]
         [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME]
         [--issuer-uri=ISSUER_URI]
         [--web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...]]
@@ -105,7 +105,7 @@ FLAGS
 
             "'admins' in google.groups"
 
-     --attribute-mapping=[ATTRIBUTE_MAPPING,...]
+     --attribute-mapping=[KEY=VALUE,...]
         Maps claims from the authentication credentials issued by the Identity
         Provider into Google Cloud IAM attributes, e.g. subject, segment.
 
diff --git a/gcloud/alpha/iam/workload-identity-pools/providers/create-aws b/gcloud/alpha/iam/workload-identity-pools/providers/create-aws
index 97c256ac1..1302d44f6 100644
--- a/gcloud/alpha/iam/workload-identity-pools/providers/create-aws
+++ b/gcloud/alpha/iam/workload-identity-pools/providers/create-aws
@@ -7,9 +7,8 @@ SYNOPSIS
         (PROVIDER : --location=LOCATION
           --workload-identity-pool=WORKLOAD_IDENTITY_POOL)
         --account-id=ACCOUNT_ID [--attribute-condition=ATTRIBUTE_CONDITION]
-        [--attribute-mapping=[ATTRIBUTE_MAPPING,...]]
-        [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME]
-        [GCLOUD_WIDE_FLAG ...]
+        [--attribute-mapping=[KEY=VALUE,...]] [--description=DESCRIPTION]
+        [--disabled] [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (ALPHA) Create a new AWS workload identity pool provider.
@@ -103,7 +102,7 @@ OPTIONAL FLAGS
 
             "'admins' in google.groups"
 
-     --attribute-mapping=[ATTRIBUTE_MAPPING,...]
+     --attribute-mapping=[KEY=VALUE,...]
         Maps attributes from authentication credentials issued by an external
         identity provider to Google Cloud attributes, such as subject and
         segment.
diff --git a/gcloud/alpha/iam/workload-identity-pools/providers/create-oidc b/gcloud/alpha/iam/workload-identity-pools/providers/create-oidc
index 12c3278bc..b953a4501 100644
--- a/gcloud/alpha/iam/workload-identity-pools/providers/create-oidc
+++ b/gcloud/alpha/iam/workload-identity-pools/providers/create-oidc
@@ -6,7 +6,7 @@ SYNOPSIS
     gcloud alpha iam workload-identity-pools providers create-oidc
         (PROVIDER : --location=LOCATION
           --workload-identity-pool=WORKLOAD_IDENTITY_POOL)
-        --attribute-mapping=[ATTRIBUTE_MAPPING,...] --issuer-uri=ISSUER_URI
+        --attribute-mapping=[KEY=VALUE,...] --issuer-uri=ISSUER_URI
         [--allowed-audiences=[ALLOWED_AUDIENCES,...]]
         [--attribute-condition=ATTRIBUTE_CONDITION] [--description=DESCRIPTION]
         [--disabled] [--display-name=DISPLAY_NAME]
@@ -76,7 +76,7 @@ POSITIONAL ARGUMENTS
             line.
 
 REQUIRED FLAGS
-     --attribute-mapping=[ATTRIBUTE_MAPPING,...]
+     --attribute-mapping=[KEY=VALUE,...]
         Maps attributes from authentication credentials issued by an external
         identity provider to Google Cloud attributes, such as subject and
         segment.
diff --git a/gcloud/alpha/iam/workload-identity-pools/providers/update-aws b/gcloud/alpha/iam/workload-identity-pools/providers/update-aws
index 3b68d88ed..f4064272b 100644
--- a/gcloud/alpha/iam/workload-identity-pools/providers/update-aws
+++ b/gcloud/alpha/iam/workload-identity-pools/providers/update-aws
@@ -7,9 +7,8 @@ SYNOPSIS
         (PROVIDER : --location=LOCATION
           --workload-identity-pool=WORKLOAD_IDENTITY_POOL)
         [--account-id=ACCOUNT_ID] [--attribute-condition=ATTRIBUTE_CONDITION]
-        [--attribute-mapping=[ATTRIBUTE_MAPPING,...]]
-        [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME]
-        [GCLOUD_WIDE_FLAG ...]
+        [--attribute-mapping=[KEY=VALUE,...]] [--description=DESCRIPTION]
+        [--disabled] [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (ALPHA) Update an AWS workload identity pool provider.
@@ -102,7 +101,7 @@ FLAGS
 
             "'admins' in google.groups"
 
-     --attribute-mapping=[ATTRIBUTE_MAPPING,...]
+     --attribute-mapping=[KEY=VALUE,...]
         Maps attributes from authentication credentials issued by an external
         identity provider to Google Cloud attributes, such as subject and
         segment.
diff --git a/gcloud/alpha/iam/workload-identity-pools/providers/update-oidc b/gcloud/alpha/iam/workload-identity-pools/providers/update-oidc
index 0e00075bb..295142c10 100644
--- a/gcloud/alpha/iam/workload-identity-pools/providers/update-oidc
+++ b/gcloud/alpha/iam/workload-identity-pools/providers/update-oidc
@@ -8,10 +8,9 @@ SYNOPSIS
           --workload-identity-pool=WORKLOAD_IDENTITY_POOL)
         [--allowed-audiences=[ALLOWED_AUDIENCES,...]]
         [--attribute-condition=ATTRIBUTE_CONDITION]
-        [--attribute-mapping=[ATTRIBUTE_MAPPING,...]]
-        [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME]
-        [--issuer-uri=ISSUER_URI] [--jwk-json-path=JWK_JSON_PATH]
-        [GCLOUD_WIDE_FLAG ...]
+        [--attribute-mapping=[KEY=VALUE,...]] [--description=DESCRIPTION]
+        [--disabled] [--display-name=DISPLAY_NAME] [--issuer-uri=ISSUER_URI]
+        [--jwk-json-path=JWK_JSON_PATH] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (ALPHA) Update an OIDC workload identity pool provider.
@@ -117,7 +116,7 @@ FLAGS
 
             "'admins' in google.groups"
 
-     --attribute-mapping=[ATTRIBUTE_MAPPING,...]
+     --attribute-mapping=[KEY=VALUE,...]
         Maps attributes from authentication credentials issued by an external
         identity provider to Google Cloud attributes, such as subject and
         segment.
diff --git a/gcloud/alpha/identity/groups/create b/gcloud/alpha/identity/groups/create
index 2b8665adb..79d2f7599 100644
--- a/gcloud/alpha/identity/groups/create
+++ b/gcloud/alpha/identity/groups/create
@@ -4,7 +4,8 @@ NAME
 SYNOPSIS
     gcloud alpha identity groups create EMAIL --organization=ORGANIZATION
         [--description=DESCRIPTION] [--display-name=DISPLAY_NAME]
-        [--dynamic-user-query=DYNAMIC_USER_QUERY] [--posix-group=POSIX_GROUP]
+        [--dynamic-user-query=DYNAMIC_USER_QUERY]
+        [--posix-group=[gid=GID],[name=NAME]]
         [--with-initial-owner=WITH_INITIAL_OWNER]
         [--group-type=GROUP_TYPE; default="discussion" | --labels=LABELS]
         [GCLOUD_WIDE_FLAG ...]
@@ -64,7 +65,7 @@ OPTIONAL FLAGS
         Example of a query:
         --dynamic-user-query="user.organizations.exists(org,org.title=='SWE')"
 
-     --posix-group=POSIX_GROUP
+     --posix-group=[gid=GID],[name=NAME]
         Group ID (gid) and name of the POSIX group that you want to associate
         with the specified Cloud Identity group. You can specify multiple POSIX
         groups with multiple instances of this flag.
diff --git a/gcloud/alpha/identity/groups/update b/gcloud/alpha/identity/groups/update
index 183195ad2..484225156 100644
--- a/gcloud/alpha/identity/groups/update
+++ b/gcloud/alpha/identity/groups/update
@@ -4,7 +4,7 @@ NAME
 SYNOPSIS
     gcloud alpha identity groups update EMAIL
         [--dynamic-user-query=DYNAMIC_USER_QUERY]
-        [--add-posix-group=POSIX_GROUP | --clear-posix-groups
+        [--add-posix-group=[gid=GID],[name=NAME] | --clear-posix-groups
           | --remove-posix-groups=[POSIX_GROUP,...]]
         [--clear-description | --description=DESCRIPTION]
         [--clear-display-name | --display-name=DISPLAY_NAME]
@@ -43,7 +43,7 @@ FLAGS
 
      At most one of these can be specified:
 
-       --add-posix-group=POSIX_GROUP
+       --add-posix-group=[gid=GID],[name=NAME]
           Group id (gid) and a name for a POSIX group that you want to add to
           the specified Cloud Identity group. You can specify multiple POSIX
           groups to add with multiple instances of this flag.
diff --git a/gcloud/alpha/infra-manager/help b/gcloud/alpha/infra-manager/help
index f16e17f68..869ecfa77 100644
--- a/gcloud/alpha/infra-manager/help
+++ b/gcloud/alpha/infra-manager/help
@@ -1,11 +1,11 @@
 NAME
-    gcloud alpha infra-manager - manage Config resources
+    gcloud alpha infra-manager - manage Infra Manager resources
 
 SYNOPSIS
     gcloud alpha infra-manager GROUP [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (ALPHA) Manage Config resources.
+    (ALPHA) Manage Infra Manager resources.
 
 GCLOUD WIDE FLAGS
     These flags are available to all commands: --help.
diff --git a/gcloud/alpha/memcache/instances/create b/gcloud/alpha/memcache/instances/create
index 3f5032298..04f7a8fbe 100644
--- a/gcloud/alpha/memcache/instances/create
+++ b/gcloud/alpha/memcache/instances/create
@@ -6,7 +6,7 @@ SYNOPSIS
     gcloud alpha memcache instances create (INSTANCE : --region=REGION)
         --node-count=NODE_COUNT --node-cpu=NODE_CPU --node-memory=NODE_MEMORY
         [--async] [--authorized-network=AUTHORIZED_NETWORK]
-        [--display-name=DISPLAY_NAME] [--labels=KEY=VALUE]
+        [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]]
         [--maintenance-window-day=MAINTENANCE_WINDOW_DAY]
         [--maintenance-window-duration=MAINTENANCE_WINDOW_DURATION]
         [--maintenance-window-start-time=MAINTENANCE_WINDOW_START_TIME]
@@ -90,7 +90,7 @@ OPTIONAL FLAGS
      --display-name=DISPLAY_NAME
         An arbitrary and optional user provided name for the instance.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
      --maintenance-window-day=MAINTENANCE_WINDOW_DAY
diff --git a/gcloud/alpha/memcache/instances/update b/gcloud/alpha/memcache/instances/update
index 46462478a..ed1c71e46 100644
--- a/gcloud/alpha/memcache/instances/update
+++ b/gcloud/alpha/memcache/instances/update
@@ -5,7 +5,8 @@ NAME
 SYNOPSIS
     gcloud alpha memcache instances update (INSTANCE : --region=REGION)
         (--parameters=KEY=VALUE | --display-name=DISPLAY_NAME
-          --labels=KEY=VALUE --node-count=NODE_COUNT --maintenance-window-any
+          --labels=[KEY=VALUE,...]
+          --node-count=NODE_COUNT --maintenance-window-any
           | --maintenance-window-day=MAINTENANCE_WINDOW_DAY
           --maintenance-window-duration=MAINTENANCE_WINDOW_DURATION
           --maintenance-window-start-time=MAINTENANCE_WINDOW_START_TIME)
@@ -142,7 +143,7 @@ REQUIRED FLAGS
        --display-name=DISPLAY_NAME
           An arbitrary and optional user provided name for the instance.
 
-       --labels=KEY=VALUE
+       --labels=[KEY=VALUE,...]
           List of label KEY=VALUE pairs to add.
 
        --node-count=NODE_COUNT
diff --git a/gcloud/alpha/metastore/operations/cancel b/gcloud/alpha/metastore/operations/cancel
index e2d749bae..9e9753f33 100644
--- a/gcloud/alpha/metastore/operations/cancel
+++ b/gcloud/alpha/metastore/operations/cancel
@@ -59,7 +59,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud metastore operations cancel
 
         $ gcloud beta metastore operations cancel
 
diff --git a/gcloud/alpha/metastore/services/alter-table-properties b/gcloud/alpha/metastore/services/alter-table-properties
index d6e1eea9d..1cf79f144 100644
--- a/gcloud/alpha/metastore/services/alter-table-properties
+++ b/gcloud/alpha/metastore/services/alter-table-properties
@@ -4,7 +4,7 @@ NAME
 
 SYNOPSIS
     gcloud alpha metastore services alter-table-properties
-        (SERVICE : --location=LOCATION) --properties=PROPERTIES
+        (SERVICE : --location=LOCATION) --properties=[KEY=VALUE,...]
         --table-name=TABLE_NAME --update-mask=UPDATE_MASK [--async]
         [GCLOUD_WIDE_FLAG ...]
 
@@ -62,7 +62,7 @@ POSITIONAL ARGUMENTS
           ▸ set the property metastore/location.
 
 REQUIRED FLAGS
-     --properties=PROPERTIES
+     --properties=[KEY=VALUE,...]
         A string where field names are separated by a comma. Describes the
         desired values to mutate. If update-mask is empty, the properties will
         not update. Otherwise, the properties only alter the values whose
diff --git a/gcloud/alpha/metastore/services/create b/gcloud/alpha/metastore/services/create
index 780d4f4a5..80c65ceea 100644
--- a/gcloud/alpha/metastore/services/create
+++ b/gcloud/alpha/metastore/services/create
@@ -15,7 +15,7 @@ SYNOPSIS
           | --auxiliary-versions-from-file=AUXILIARY_VERSIONS_FROM_FILE]
         [--consumer-subnetworks=[CONSUMER_SUBNETWORKS,...] | --network=NETWORK
           | --network-config-from-file=NETWORK_CONFIG_FROM_FILE]
-        [--hive-metastore-configs=KEY=VALUE
+        [--hive-metastore-configs=[KEY=VALUE,...]
           | --hive-metastore-configs-from-file=HIVE_METASTORE_CONFIGS_FROM_FILE]
         [--instance-size=INSTANCE_SIZE | --scaling-factor=SCALING_FACTOR
           | --tier=TIER]
@@ -226,7 +226,7 @@ FLAGS
 
      At most one of these can be specified:
 
-       --hive-metastore-configs=KEY=VALUE
+       --hive-metastore-configs=[KEY=VALUE,...]
           A mapping of Hive metastore configuration key-value pairs to apply to
           the Hive metastore.
 
diff --git a/gcloud/alpha/metastore/services/update b/gcloud/alpha/metastore/services/update
index 0e76f8306..4dafd60e7 100644
--- a/gcloud/alpha/metastore/services/update
+++ b/gcloud/alpha/metastore/services/update
@@ -15,7 +15,7 @@ SYNOPSIS
           --maintenance-window-hour=MAINTENANCE_WINDOW_HOUR]
         [--update-auxiliary-versions-from-file=UPDATE_AUXILIARY_VERSIONS_FROM_FILE | --add-auxiliary-versions=[ADD_AUXILIARY_VERSIONS,
           ...] --clear-auxiliary-versions]
-        [--update-hive-metastore-configs-from-file=UPDATE_HIVE_METASTORE_CONFIGS_FROM_FILE | --update-hive-metastore-configs=[UPDATE_HIVE_METASTORE_CONFIGS,
+        [--update-hive-metastore-configs-from-file=UPDATE_HIVE_METASTORE_CONFIGS_FROM_FILE | --update-hive-metastore-configs=[KEY=VALUE,
           ...] --clear-hive-metastore-configs
           | --remove-hive-metastore-configs=[REMOVE_HIVE_METASTORE_CONFIGS,
           ...]] [GCLOUD_WIDE_FLAG ...]
@@ -266,7 +266,7 @@ FLAGS
        Modify the Hive metastore configuration properties by passing key-value
        pairs in through the flags.
 
-         --update-hive-metastore-configs=[UPDATE_HIVE_METASTORE_CONFIGS,...]
+         --update-hive-metastore-configs=[KEY=VALUE,...]
             Comma-separated list of Hive metastore configurations. Each
             configuration has the form "NAME=VALUE".
 
diff --git a/gcloud/alpha/ml/translate/batch-translate-text b/gcloud/alpha/ml/translate/batch-translate-text
index 6085e52b0..e2d3a79a2 100644
--- a/gcloud/alpha/ml/translate/batch-translate-text
+++ b/gcloud/alpha/ml/translate/batch-translate-text
@@ -4,9 +4,9 @@ NAME
 
 SYNOPSIS
     gcloud alpha ml translate batch-translate-text --destination=DESTINATION
-        --source=[SOURCE,...] --source-language=SOURCE_LANGUAGE
+        --source=[FILE_PATH[=FILE_TYPE],...] --source-language=SOURCE_LANGUAGE
         --target-language-codes=[TARGET_LANGUAGE_CODES,...]
-        [--glossaries=[GLOSSARIES,...]] [--models=[MODELS,...]]
+        [--glossaries=[KEY=VALUE,...]] [--models=[KEY=VALUE,...]]
         [--zone=ZONE; default="global"] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -27,7 +27,7 @@ REQUIRED FLAGS
         Location to which the results should be written. Must be a Google Cloud
         Storage URI.
 
-     --source=[SOURCE,...]
+     --source=[FILE_PATH[=FILE_TYPE],...]
         Comma-separated list of entries of the form FILE_PATH[=FILE_TYPE]
         specifying source files and files types for the translation. FILE_PATH
         must be a Google Cloud Storage URI. FILE_TYPE defaults to 'text/html'
@@ -45,11 +45,11 @@ REQUIRED FLAGS
         language codes here.
 
 OPTIONAL FLAGS
-     --glossaries=[GLOSSARIES,...]
+     --glossaries=[KEY=VALUE,...]
         Glossaries to be applied for translation. Comma-separated dictionary
         where map's key is target language code, map's value is glossary name.
 
-     --models=[MODELS,...]
+     --models=[KEY=VALUE,...]
         Models to use for translation. Comma-separated dictionary where map's
         key is target language code, map's value is model name. Value can be a
         built-in general model, or an AutoML Translation model.
diff --git a/gcloud/alpha/netapp/active-directories/create b/gcloud/alpha/netapp/active-directories/create
index 817a61d16..8f5a3b02c 100644
--- a/gcloud/alpha/netapp/active-directories/create
+++ b/gcloud/alpha/netapp/active-directories/create
@@ -146,7 +146,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp active-directories create
 
         $ gcloud beta netapp active-directories create
 
diff --git a/gcloud/alpha/netapp/active-directories/delete b/gcloud/alpha/netapp/active-directories/delete
index a5e578f3a..cb9d58e1b 100644
--- a/gcloud/alpha/netapp/active-directories/delete
+++ b/gcloud/alpha/netapp/active-directories/delete
@@ -73,7 +73,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp active-directories delete
 
         $ gcloud beta netapp active-directories delete
 
diff --git a/gcloud/alpha/netapp/active-directories/describe b/gcloud/alpha/netapp/active-directories/describe
index c19881e35..b4f0e3e51 100644
--- a/gcloud/alpha/netapp/active-directories/describe
+++ b/gcloud/alpha/netapp/active-directories/describe
@@ -62,7 +62,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp active-directories describe
 
         $ gcloud beta netapp active-directories describe
 
diff --git a/gcloud/alpha/netapp/active-directories/help b/gcloud/alpha/netapp/active-directories/help
index c68ef3af9..5d8465d6e 100644
--- a/gcloud/alpha/netapp/active-directories/help
+++ b/gcloud/alpha/netapp/active-directories/help
@@ -35,7 +35,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp active-directories
 
         $ gcloud beta netapp active-directories
 
diff --git a/gcloud/alpha/netapp/active-directories/list b/gcloud/alpha/netapp/active-directories/list
index cef629106..7d2dd408a 100644
--- a/gcloud/alpha/netapp/active-directories/list
+++ b/gcloud/alpha/netapp/active-directories/list
@@ -82,7 +82,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp active-directories list
 
         $ gcloud beta netapp active-directories list
 
diff --git a/gcloud/alpha/netapp/active-directories/update b/gcloud/alpha/netapp/active-directories/update
index b8aa22fc5..3f646c4f3 100644
--- a/gcloud/alpha/netapp/active-directories/update
+++ b/gcloud/alpha/netapp/active-directories/update
@@ -169,7 +169,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp active-directories update
 
         $ gcloud beta netapp active-directories update
 
diff --git a/gcloud/alpha/netapp/help b/gcloud/alpha/netapp/help
index 16ba32880..2e6f60260 100644
--- a/gcloud/alpha/netapp/help
+++ b/gcloud/alpha/netapp/help
@@ -45,7 +45,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp
 
         $ gcloud beta netapp
 
diff --git a/gcloud/alpha/netapp/locations/describe b/gcloud/alpha/netapp/locations/describe
index 787723653..8aa0c8197 100644
--- a/gcloud/alpha/netapp/locations/describe
+++ b/gcloud/alpha/netapp/locations/describe
@@ -45,7 +45,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp locations describe
 
         $ gcloud beta netapp locations describe
 
diff --git a/gcloud/alpha/netapp/locations/help b/gcloud/alpha/netapp/locations/help
index 306dbcd2b..dab448a98 100644
--- a/gcloud/alpha/netapp/locations/help
+++ b/gcloud/alpha/netapp/locations/help
@@ -26,7 +26,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp locations
 
         $ gcloud beta netapp locations
 
diff --git a/gcloud/alpha/netapp/locations/list b/gcloud/alpha/netapp/locations/list
index 8cb10e29e..664178837 100644
--- a/gcloud/alpha/netapp/locations/list
+++ b/gcloud/alpha/netapp/locations/list
@@ -58,7 +58,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp locations list
 
         $ gcloud beta netapp locations list
 
diff --git a/gcloud/alpha/netapp/operations/describe b/gcloud/alpha/netapp/operations/describe
index e17b48617..48ad843e4 100644
--- a/gcloud/alpha/netapp/operations/describe
+++ b/gcloud/alpha/netapp/operations/describe
@@ -60,7 +60,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp operations describe
 
         $ gcloud beta netapp operations describe
 
diff --git a/gcloud/alpha/netapp/operations/help b/gcloud/alpha/netapp/operations/help
index 4d5e6f6d2..258856010 100644
--- a/gcloud/alpha/netapp/operations/help
+++ b/gcloud/alpha/netapp/operations/help
@@ -26,7 +26,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp operations
 
         $ gcloud beta netapp operations
 
diff --git a/gcloud/alpha/netapp/operations/list b/gcloud/alpha/netapp/operations/list
index ff3e636c2..edd64ee61 100644
--- a/gcloud/alpha/netapp/operations/list
+++ b/gcloud/alpha/netapp/operations/list
@@ -81,7 +81,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp operations list
 
         $ gcloud beta netapp operations list
 
diff --git a/gcloud/alpha/netapp/storage-pools/create b/gcloud/alpha/netapp/storage-pools/create
index 40ecc63cc..7b0aecbb9 100644
--- a/gcloud/alpha/netapp/storage-pools/create
+++ b/gcloud/alpha/netapp/storage-pools/create
@@ -172,7 +172,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp storage-pools create
 
         $ gcloud beta netapp storage-pools create
 
diff --git a/gcloud/alpha/netapp/storage-pools/delete b/gcloud/alpha/netapp/storage-pools/delete
index 0d5056aef..0f3b6f6b2 100644
--- a/gcloud/alpha/netapp/storage-pools/delete
+++ b/gcloud/alpha/netapp/storage-pools/delete
@@ -72,7 +72,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp storage-pools delete
 
         $ gcloud beta netapp storage-pools delete
 
diff --git a/gcloud/alpha/netapp/storage-pools/describe b/gcloud/alpha/netapp/storage-pools/describe
index 30ac3baa6..88150f21b 100644
--- a/gcloud/alpha/netapp/storage-pools/describe
+++ b/gcloud/alpha/netapp/storage-pools/describe
@@ -62,7 +62,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp storage-pools describe
 
         $ gcloud beta netapp storage-pools describe
 
diff --git a/gcloud/alpha/netapp/storage-pools/help b/gcloud/alpha/netapp/storage-pools/help
index 5f0052823..da5cc7929 100644
--- a/gcloud/alpha/netapp/storage-pools/help
+++ b/gcloud/alpha/netapp/storage-pools/help
@@ -35,7 +35,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp storage-pools
 
         $ gcloud beta netapp storage-pools
 
diff --git a/gcloud/alpha/netapp/storage-pools/list b/gcloud/alpha/netapp/storage-pools/list
index 9cef7348e..7ea144db0 100644
--- a/gcloud/alpha/netapp/storage-pools/list
+++ b/gcloud/alpha/netapp/storage-pools/list
@@ -81,7 +81,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp storage-pools list
 
         $ gcloud beta netapp storage-pools list
 
diff --git a/gcloud/alpha/netapp/storage-pools/update b/gcloud/alpha/netapp/storage-pools/update
index 4905f90ff..eeed9bef3 100644
--- a/gcloud/alpha/netapp/storage-pools/update
+++ b/gcloud/alpha/netapp/storage-pools/update
@@ -131,7 +131,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp storage-pools update
 
         $ gcloud beta netapp storage-pools update
 
diff --git a/gcloud/alpha/netapp/volumes/create b/gcloud/alpha/netapp/volumes/create
index b04434b0f..7ab83c3c8 100644
--- a/gcloud/alpha/netapp/volumes/create
+++ b/gcloud/alpha/netapp/volumes/create
@@ -237,7 +237,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp volumes create
 
         $ gcloud beta netapp volumes create
 
diff --git a/gcloud/alpha/netapp/volumes/delete b/gcloud/alpha/netapp/volumes/delete
index 87a44bda2..07d0348a2 100644
--- a/gcloud/alpha/netapp/volumes/delete
+++ b/gcloud/alpha/netapp/volumes/delete
@@ -71,7 +71,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp volumes delete
 
         $ gcloud beta netapp volumes delete
 
diff --git a/gcloud/alpha/netapp/volumes/describe b/gcloud/alpha/netapp/volumes/describe
index 21846a851..502590513 100644
--- a/gcloud/alpha/netapp/volumes/describe
+++ b/gcloud/alpha/netapp/volumes/describe
@@ -58,7 +58,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp volumes describe
 
         $ gcloud beta netapp volumes describe
 
diff --git a/gcloud/alpha/netapp/volumes/help b/gcloud/alpha/netapp/volumes/help
index b92b10c9b..571435f11 100644
--- a/gcloud/alpha/netapp/volumes/help
+++ b/gcloud/alpha/netapp/volumes/help
@@ -43,7 +43,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp volumes
 
         $ gcloud beta netapp volumes
 
diff --git a/gcloud/alpha/netapp/volumes/list b/gcloud/alpha/netapp/volumes/list
index 793bdacd4..afe76c5f4 100644
--- a/gcloud/alpha/netapp/volumes/list
+++ b/gcloud/alpha/netapp/volumes/list
@@ -81,7 +81,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp volumes list
 
         $ gcloud beta netapp volumes list
 
diff --git a/gcloud/alpha/netapp/volumes/revert b/gcloud/alpha/netapp/volumes/revert
index ecc465968..b9e27bd15 100644
--- a/gcloud/alpha/netapp/volumes/revert
+++ b/gcloud/alpha/netapp/volumes/revert
@@ -94,7 +94,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp volumes revert
 
         $ gcloud beta netapp volumes revert
 
diff --git a/gcloud/alpha/netapp/volumes/snapshots/create b/gcloud/alpha/netapp/volumes/snapshots/create
index 0247e425c..0ef7323c3 100644
--- a/gcloud/alpha/netapp/volumes/snapshots/create
+++ b/gcloud/alpha/netapp/volumes/snapshots/create
@@ -8,11 +8,11 @@ SYNOPSIS
         [--labels=[KEY=VALUE,...]] [--volume=VOLUME] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (ALPHA) Create a Cloud NetApp Volume Snapshot
+    (ALPHA) Create a Cloud NetApp Volume Snapshot.
 
 EXAMPLES
     The following command creates a Snapshot named NAME using the required
-    arguments
+    arguments:
 
         $ gcloud alpha netapp volumes snapshots create NAME \
           --location=us-central1 --volume=vol1
@@ -106,7 +106,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp volumes snapshots create
 
         $ gcloud beta netapp volumes snapshots create
 
diff --git a/gcloud/alpha/netapp/volumes/snapshots/delete b/gcloud/alpha/netapp/volumes/snapshots/delete
index 1cbcc9a83..6958571df 100644
--- a/gcloud/alpha/netapp/volumes/snapshots/delete
+++ b/gcloud/alpha/netapp/volumes/snapshots/delete
@@ -8,11 +8,11 @@ SYNOPSIS
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (ALPHA) Delete a Cloud NetApp Volume Snapshot
+    (ALPHA) Delete a Cloud NetApp Volume Snapshot.
 
 EXAMPLES
     The following command deletes a Snapshot named NAME in the given location
-    and volume
+    and volume:
 
         $ gcloud alpha netapp volumes snapshots delete NAME \
           --location=us-central1 --volume=vol1
@@ -100,7 +100,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp volumes snapshots delete
 
         $ gcloud beta netapp volumes snapshots delete
 
diff --git a/gcloud/alpha/netapp/volumes/snapshots/describe b/gcloud/alpha/netapp/volumes/snapshots/describe
index f67fe7c3a..f0bd7cb28 100644
--- a/gcloud/alpha/netapp/volumes/snapshots/describe
+++ b/gcloud/alpha/netapp/volumes/snapshots/describe
@@ -8,11 +8,11 @@ SYNOPSIS
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (ALPHA) Describe a Cloud NetApp Volume Snapshot
+    (ALPHA) Describe a Cloud NetApp Volume Snapshot.
 
 EXAMPLES
     The following command describes a Snapshot named NAME in the given location
-    and volume
+    and volume:
 
         $ gcloud alpha netapp volumes snapshots describe NAME \
           --location=us-central1 --volume=vol1
@@ -91,7 +91,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp volumes snapshots describe
 
         $ gcloud beta netapp volumes snapshots describe
 
diff --git a/gcloud/alpha/netapp/volumes/snapshots/help b/gcloud/alpha/netapp/volumes/snapshots/help
index 9a8f673b7..7c0451c1a 100644
--- a/gcloud/alpha/netapp/volumes/snapshots/help
+++ b/gcloud/alpha/netapp/volumes/snapshots/help
@@ -35,7 +35,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp volumes snapshots
 
         $ gcloud beta netapp volumes snapshots
 
diff --git a/gcloud/alpha/netapp/volumes/snapshots/list b/gcloud/alpha/netapp/volumes/snapshots/list
index b92188a05..3144fd5ef 100644
--- a/gcloud/alpha/netapp/volumes/snapshots/list
+++ b/gcloud/alpha/netapp/volumes/snapshots/list
@@ -9,10 +9,10 @@ SYNOPSIS
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (ALPHA) Lists Cloud NetApp Volume Snapshots
+    (ALPHA) Lists Cloud NetApp Volume Snapshots.
 
 EXAMPLES
-    The following command lists all Snapshots in the given location and volume
+    The following command lists all Snapshots in the given location and volume:
 
         $ gcloud alpha netapp volumes snapshots list \
           --location=us-central1 --volume=vol1
@@ -107,7 +107,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp volumes snapshots list
 
         $ gcloud beta netapp volumes snapshots list
 
diff --git a/gcloud/alpha/netapp/volumes/snapshots/update b/gcloud/alpha/netapp/volumes/snapshots/update
index 43f6cd8c2..f8ea0ed6e 100644
--- a/gcloud/alpha/netapp/volumes/snapshots/update
+++ b/gcloud/alpha/netapp/volumes/snapshots/update
@@ -9,11 +9,11 @@ SYNOPSIS
         [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (ALPHA) Update a Cloud NetApp Volume Snapshot and its specified parameters
+    (ALPHA) Update a Cloud NetApp Volume Snapshot and its specified parameters.
 
 EXAMPLES
     The following command updates a Snapshot named NAME and its specified
-    parameters
+    parameters:
 
         $ gcloud alpha netapp volumes snapshots update NAME \
           --location=us-central1 --description="new" \
@@ -129,7 +129,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp volumes snapshots update
 
         $ gcloud beta netapp volumes snapshots update
 
diff --git a/gcloud/alpha/netapp/volumes/update b/gcloud/alpha/netapp/volumes/update
index 67b7cad45..c33e359c7 100644
--- a/gcloud/alpha/netapp/volumes/update
+++ b/gcloud/alpha/netapp/volumes/update
@@ -247,7 +247,9 @@ NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct
     project, you might be trying to access an API with an invitation-only early
-    access allowlist. This variant is also available:
+    access allowlist. These variants are also available:
+
+        $ gcloud netapp volumes update
 
         $ gcloud beta netapp volumes update
 
diff --git a/gcloud/alpha/network-connectivity/hubs/update b/gcloud/alpha/network-connectivity/hubs/update
index 976ab11e0..24069483f 100644
--- a/gcloud/alpha/network-connectivity/hubs/update
+++ b/gcloud/alpha/network-connectivity/hubs/update
@@ -3,7 +3,8 @@ NAME
 
 SYNOPSIS
     gcloud alpha network-connectivity hubs update HUB [--async]
-        [--description=DESCRIPTION] [--labels=KEY=VALUE] [GCLOUD_WIDE_FLAG ...]
+        [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (ALPHA) Update the details of a hub.
@@ -41,7 +42,7 @@ FLAGS
      --description=DESCRIPTION
         New description of the hub.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
 GCLOUD WIDE FLAGS
diff --git a/gcloud/alpha/network-connectivity/internal-ranges/create b/gcloud/alpha/network-connectivity/internal-ranges/create
index 91e990044..4b3a9352e 100644
--- a/gcloud/alpha/network-connectivity/internal-ranges/create
+++ b/gcloud/alpha/network-connectivity/internal-ranges/create
@@ -7,7 +7,7 @@ SYNOPSIS
         (INTERNAL_RANGE : --region=REGION) --network=NETWORK
         (--ip-cidr-range=IP_CIDR_RANGE | [--prefix-length=PREFIX_LENGTH
           : --target-cidr-range=[TARGET_CIDR_RANGE,...]]) [--async]
-        [--description=DESCRIPTION] [--labels=KEY=VALUE]
+        [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]]
         [--overlaps=[OVERLAPS,...]] [--peering=PEERING; default="for-self"]
         [--usage=USAGE; default="for-vpc"] [GCLOUD_WIDE_FLAG ...]
 
@@ -102,12 +102,16 @@ OPTIONAL FLAGS
      --description=DESCRIPTION
         Description of the internal range to be created.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
      --overlaps=[OVERLAPS,...]
         Overlap specifications for the range being created. OVERLAPS must be
-        (only one value is supported):
+        one of:
+
+         overlap-existing-subnet-range
+            Allows for creation of internal ranges that overlap with existing
+            subnets.
 
          overlap-route-range
             Allows for creation or existence of routes that have a more
diff --git a/gcloud/alpha/network-connectivity/internal-ranges/update b/gcloud/alpha/network-connectivity/internal-ranges/update
index ccf787aeb..f1b31e7aa 100644
--- a/gcloud/alpha/network-connectivity/internal-ranges/update
+++ b/gcloud/alpha/network-connectivity/internal-ranges/update
@@ -68,7 +68,11 @@ FLAGS
 
        --overlaps=[OVERLAPS,...]
           Overlap specifications for the range being updated. OVERLAPS must be
-          (only one value is supported):
+          one of:
+
+           overlap-existing-subnet-range
+              Allows for creation of internal ranges that overlap with existing
+              subnets.
 
            overlap-route-range
               Allows for creation or existence of routes that have a more
diff --git a/gcloud/alpha/network-connectivity/spokes/create b/gcloud/alpha/network-connectivity/spokes/create
index e382eba22..b264302be 100644
--- a/gcloud/alpha/network-connectivity/spokes/create
+++ b/gcloud/alpha/network-connectivity/spokes/create
@@ -5,9 +5,10 @@ SYNOPSIS
     gcloud alpha network-connectivity spokes create (SPOKE : --region=REGION)
         --hub=HUB
         (--interconnect-attachment=[INTERCONNECT_ATTACHMENT,...]
-          | --router-appliance=ROUTER_APPLIANCE
+          | --router-appliance=[instance=INSTANCE],[ip=IP]
           | --vpn-tunnel=[VPN_TUNNEL,...]) [--async]
-        [--description=DESCRIPTION] [--labels=KEY=VALUE] [GCLOUD_WIDE_FLAG ...]
+        [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (ALPHA) Create a new spoke with the given name.
@@ -61,7 +62,7 @@ REQUIRED FLAGS
        --interconnect-attachment=[INTERCONNECT_ATTACHMENT,...]
           Interconnect attachment that this spoke links to.
 
-       --router-appliance=ROUTER_APPLIANCE
+       --router-appliance=[instance=INSTANCE],[ip=IP]
           Router appliance instance(s) that this spoke links to.
 
           For example, use --router-appliance=instance=ins_1,ip=10.10.0.1 to
@@ -81,7 +82,7 @@ OPTIONAL FLAGS
      --description=DESCRIPTION
         Description of the spoke to be created.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
 GCLOUD WIDE FLAGS
diff --git a/gcloud/alpha/network-connectivity/spokes/update b/gcloud/alpha/network-connectivity/spokes/update
index c7f40acfa..e20670b67 100644
--- a/gcloud/alpha/network-connectivity/spokes/update
+++ b/gcloud/alpha/network-connectivity/spokes/update
@@ -4,8 +4,8 @@ NAME
 
 SYNOPSIS
     gcloud alpha network-connectivity spokes update (SPOKE : --region=REGION)
-        [--async] [--description=DESCRIPTION] [--labels=KEY=VALUE]
-        [--router-appliance=ROUTER_APPLIANCE] [GCLOUD_WIDE_FLAG ...]
+        [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]]
+        [--router-appliance=[instance=INSTANCE],[ip=IP]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (ALPHA) Update the detail of a spoke.
@@ -56,10 +56,10 @@ FLAGS
      --description=DESCRIPTION
         New description of the spoke.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
-     --router-appliance=ROUTER_APPLIANCE
+     --router-appliance=[instance=INSTANCE],[ip=IP]
         Replace the set of router appliance instances linked to this spoke.
         Pass this flag multiple times to use multiple instances. For example,
         use --router-appliance=instance=new_instance,ip=10.10.10.1 for a single
diff --git a/gcloud/alpha/network-security/address-groups/create b/gcloud/alpha/network-security/address-groups/create
index cf8e0605c..ff005440f 100644
--- a/gcloud/alpha/network-security/address-groups/create
+++ b/gcloud/alpha/network-security/address-groups/create
@@ -6,7 +6,7 @@ SYNOPSIS
     gcloud alpha network-security address-groups create
         (ADDRESS_GROUP : --location=LOCATION) --capacity=CAPACITY --type=TYPE
         [--async] [--description=DESCRIPTION] [--items=[ITEMS,...]]
-        [--labels=KEY=VALUE] [GCLOUD_WIDE_FLAG ...]
+        [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (ALPHA) Create a new address group with the given name.
@@ -69,7 +69,7 @@ OPTIONAL FLAGS
      --items=[ITEMS,...]
         Items of the address group.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
 GCLOUD WIDE FLAGS
diff --git a/gcloud/alpha/network-security/org-address-groups/create b/gcloud/alpha/network-security/org-address-groups/create
index 5e61cd634..fc1d30cf3 100644
--- a/gcloud/alpha/network-security/org-address-groups/create
+++ b/gcloud/alpha/network-security/org-address-groups/create
@@ -6,7 +6,7 @@ SYNOPSIS
     gcloud alpha network-security org-address-groups create
         (ADDRESS_GROUP : --location=LOCATION --organization=ORGANIZATION)
         --capacity=CAPACITY --type=TYPE [--async] [--description=DESCRIPTION]
-        [--items=[ITEMS,...]] [--labels=KEY=VALUE] [GCLOUD_WIDE_FLAG ...]
+        [--items=[ITEMS,...]] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (ALPHA) Create a new address group with the given name.
@@ -70,7 +70,7 @@ OPTIONAL FLAGS
      --items=[ITEMS,...]
         Items of the address group.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
 GCLOUD WIDE FLAGS
diff --git a/gcloud/alpha/recaptcha/keys/update b/gcloud/alpha/recaptcha/keys/update
index 14d9d59f1..ffc9b4787 100644
--- a/gcloud/alpha/recaptcha/keys/update
+++ b/gcloud/alpha/recaptcha/keys/update
@@ -3,7 +3,7 @@ NAME
 
 SYNOPSIS
     gcloud alpha recaptcha keys update KEY [--display-name=DISPLAY_NAME]
-        [--labels=KEY=VALUE]
+        [--labels=[KEY=VALUE,...]]
         [--android (--allow-all-package-names
           | --package-names=[PACKAGE_NAMES,...])
           | [--ios : --allow-all-bundle-ids | --bundle-ids=[BUNDLE_IDS,...]
@@ -45,7 +45,7 @@ FLAGS
      --display-name=DISPLAY_NAME
         A human-readable name for the key. Typically a site or app name.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
      At most one of these can be specified:
diff --git a/gcloud/alpha/recommender/recommendations/list b/gcloud/alpha/recommender/recommendations/list
index 14cb73560..ffb5ac386 100644
--- a/gcloud/alpha/recommender/recommendations/list
+++ b/gcloud/alpha/recommender/recommendations/list
@@ -48,10 +48,10 @@ REQUIRED FLAGS
 
 FLAGS
      --recommender=RECOMMENDER
-        Recommender to list recommendations for. Supported recommenders can be
-        found here: https://cloud.google.com/recommender/docs/recommenders. For
-        alpha and beta users: If no recommender is specified, recommendations
-        for all supported recommenders are listed.
+        Recommender to list recommendations for. If no recommender is
+        specified, recommendations for all supported recommenders is listed.
+        Supported recommenders can be found here:
+        https://cloud.google.com/recommender/docs/recommenders
 
 LIST COMMAND FLAGS
      --filter=EXPRESSION
diff --git a/gcloud/alpha/redis/instances/create b/gcloud/alpha/redis/instances/create
index 046236efb..95eb75cdb 100644
--- a/gcloud/alpha/redis/instances/create
+++ b/gcloud/alpha/redis/instances/create
@@ -14,10 +14,10 @@ SYNOPSIS
         [--persistence-mode=PERSISTENCE_MODE]
         [--rdb-snapshot-period=RDB_SNAPSHOT_PERIOD]
         [--rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME]
-        [--read-replicas-mode=READ_REPLICAS_MODE] [--redis-config=KEY=VALUE]
-        [--redis-version=VERSION] [--replica-count=REPLICA_COUNT]
-        [--reserved-ip-range=RESERVED_IP_RANGE] [--size=SIZE; default=1]
-        [--tier=TIER; default="basic"]
+        [--read-replicas-mode=READ_REPLICAS_MODE]
+        [--redis-config=[KEY=VALUE,...]] [--redis-version=VERSION]
+        [--replica-count=REPLICA_COUNT] [--reserved-ip-range=RESERVED_IP_RANGE]
+        [--size=SIZE; default=1] [--tier=TIER; default="basic"]
         [--transit-encryption-mode=TRANSIT_ENCRYPTION_MODE] [--zone=ZONE]
         [GCLOUD_WIDE_FLAG ...]
 
@@ -157,7 +157,7 @@ FLAGS
             provided and the instance can scale up and down the number of
             replicas.
 
-     --redis-config=KEY=VALUE
+     --redis-config=[KEY=VALUE,...]
         A list of Redis config KEY=VALUE pairs to set on the instance according
         to http://redis.io/topics/config. Currently, the only supported
         parameters are:
diff --git a/gcloud/alpha/run/jobs/executions/cancel b/gcloud/alpha/run/jobs/executions/cancel
new file mode 100644
index 000000000..d1c596a8f
--- /dev/null
+++ b/gcloud/alpha/run/jobs/executions/cancel
@@ -0,0 +1,60 @@
+NAME
+    gcloud alpha run jobs executions cancel - cancel an execution
+
+SYNOPSIS
+    gcloud alpha run jobs executions cancel EXECUTION [--[no-]async]
+        [--region=REGION] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) Cancel an execution.
+
+EXAMPLES
+    To cancel an execution:
+
+        $ gcloud alpha run jobs executions cancel my-execution
+
+POSITIONAL ARGUMENTS
+     Execution resource - Execution to cancel. This represents a Cloud
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument EXECUTION on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       EXECUTION
+          ID of the Execution or fully qualified identifier for the Execution.
+
+          To set the executions attribute:
+          ▸ provide the argument EXECUTION on the command line.
+
+FLAGS
+     --[no-]async
+        Return immediately, without waiting for the operation in progress to
+        complete. Defaults to --no-async. Use --async to enable and --no-async
+        to disable.
+
+     --region=REGION
+        Region in which the resource can be found. Alternatively, set the
+        property [run/region].
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. This variant is also available:
+
+        $ gcloud beta run jobs executions cancel
+
diff --git a/gcloud/alpha/run/jobs/executions/help b/gcloud/alpha/run/jobs/executions/help
index 8c7b88a98..c4e70565c 100644
--- a/gcloud/alpha/run/jobs/executions/help
+++ b/gcloud/alpha/run/jobs/executions/help
@@ -37,6 +37,9 @@ GROUPS
 COMMANDS
     COMMAND is one of the following:
 
+     cancel
+        (ALPHA) Cancel an execution.
+
      delete
         (ALPHA) Delete an execution.
 
diff --git a/gcloud/alpha/scc/assets/update-marks b/gcloud/alpha/scc/assets/update-marks
index d30512bce..24d9b2784 100644
--- a/gcloud/alpha/scc/assets/update-marks
+++ b/gcloud/alpha/scc/assets/update-marks
@@ -4,7 +4,7 @@ NAME
 
 SYNOPSIS
     gcloud alpha scc assets update-marks (ASSET : --organization=ORGANIZATION)
-        [--security-marks=[SECURITY_MARKS,...]] [--start-time=START_TIME]
+        [--security-marks=[KEY=VALUE,...]] [--start-time=START_TIME]
         [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -73,7 +73,7 @@ POSITIONAL ARGUMENTS
             line..
 
 FLAGS
-     --security-marks=[SECURITY_MARKS,...]
+     --security-marks=[KEY=VALUE,...]
         SecurityMarks resource to be passed as the request body. It's a
         key=value pair separated by comma (,). For example:
         --security-marks="key1=val1,key2=val2".
diff --git a/gcloud/alpha/scc/findings/create b/gcloud/alpha/scc/findings/create
index 0907461f2..53e603152 100644
--- a/gcloud/alpha/scc/findings/create
+++ b/gcloud/alpha/scc/findings/create
@@ -7,7 +7,7 @@ SYNOPSIS
         (FINDING : --organization=ORGANIZATION --source=SOURCE)
         --category=CATEGORY --event-time=EVENT_TIME
         --resource-name=RESOURCE_NAME [--external-uri=EXTERNAL_URI]
-        [--source-properties=[SOURCE_PROPERTIES,...]] [--state=STATE]
+        [--source-properties=[KEY=VALUE,...]] [--state=STATE]
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -108,7 +108,7 @@ OPTIONAL FLAGS
         finding can be found. This field is guaranteed to be either empty or a
         well formed URL.
 
-     --source-properties=[SOURCE_PROPERTIES,...]
+     --source-properties=[KEY=VALUE,...]
         Source specific properties. These properties are managed by the source
         that writes the finding. The key names in the source_properties map
         must be between 1 and 255 characters, and must start with a letter and
diff --git a/gcloud/alpha/scc/findings/update b/gcloud/alpha/scc/findings/update
index 41432d401..7e9f49d5e 100644
--- a/gcloud/alpha/scc/findings/update
+++ b/gcloud/alpha/scc/findings/update
@@ -6,7 +6,7 @@ SYNOPSIS
     gcloud alpha scc findings update
         (FINDING : --organization=ORGANIZATION --source=SOURCE)
         [--event-time=EVENT_TIME] [--external-uri=EXTERNAL_URI]
-        [--source-properties=[SOURCE_PROPERTIES,...]] [--state=STATE]
+        [--source-properties=[KEY=VALUE,...]] [--state=STATE]
         [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -98,7 +98,7 @@ FLAGS
         finding can be found. This field is guaranteed to be either empty or a
         well formed URL.
 
-     --source-properties=[SOURCE_PROPERTIES,...]
+     --source-properties=[KEY=VALUE,...]
         Source specific properties. These properties are managed by the source
         that writes the finding. The key names in the source_properties map
         must be between 1 and 255 characters, and must start with a letter and
diff --git a/gcloud/alpha/scc/findings/update-marks b/gcloud/alpha/scc/findings/update-marks
index f74e11915..020d0d4d6 100644
--- a/gcloud/alpha/scc/findings/update-marks
+++ b/gcloud/alpha/scc/findings/update-marks
@@ -5,7 +5,7 @@ NAME
 SYNOPSIS
     gcloud alpha scc findings update-marks
         (FINDING : --organization=ORGANIZATION --source=SOURCE)
-        [--security-marks=[SECURITY_MARKS,...]] [--start-time=START_TIME]
+        [--security-marks=[KEY=VALUE,...]] [--start-time=START_TIME]
         [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -86,7 +86,7 @@ POSITIONAL ARGUMENTS
           ▸ provide the argument --source on the command line.
 
 FLAGS
-     --security-marks=[SECURITY_MARKS,...]
+     --security-marks=[KEY=VALUE,...]
         SecurityMarks resource to be passed as the request body. It's a
         key=value pair separated by comma (,). For example:
         --security-marks="key1=val1,key2=val2".
diff --git a/gcloud/alpha/scheduler/jobs/create/app-engine b/gcloud/alpha/scheduler/jobs/create/app-engine
index 1682d7c09..b88012799 100644
--- a/gcloud/alpha/scheduler/jobs/create/app-engine
+++ b/gcloud/alpha/scheduler/jobs/create/app-engine
@@ -5,7 +5,7 @@ NAME
 SYNOPSIS
     gcloud alpha scheduler jobs create app-engine (JOB : --location=LOCATION)
         --schedule=SCHEDULE [--attempt-deadline=ATTEMPT_DEADLINE]
-        [--description=DESCRIPTION] [--headers=HEADERS]
+        [--description=DESCRIPTION] [--headers=[KEY=VALUE,...]]
         [--http-method=HTTP_METHOD; default="post"]
         [--max-backoff=MAX_BACKOFF; default="1h"]
         [--max-doublings=MAX_DOUBLINGS; default=16]
@@ -91,7 +91,7 @@ OPTIONAL FLAGS
      --description=DESCRIPTION
         Human-readable description of the job.
 
-     --headers=HEADERS
+     --headers=[KEY=VALUE,...]
         KEY=VALUE pairs of HTTP headers to include in the request. Cannot be
         repeated. For example: --headers
         Accept-Language=en-us,Accept=text/plain
diff --git a/gcloud/alpha/scheduler/jobs/create/http b/gcloud/alpha/scheduler/jobs/create/http
index dadbdbf61..06d1a1f75 100644
--- a/gcloud/alpha/scheduler/jobs/create/http
+++ b/gcloud/alpha/scheduler/jobs/create/http
@@ -5,7 +5,7 @@ NAME
 SYNOPSIS
     gcloud alpha scheduler jobs create http (JOB : --location=LOCATION)
         --schedule=SCHEDULE --uri=URI [--attempt-deadline=ATTEMPT_DEADLINE]
-        [--description=DESCRIPTION] [--headers=HEADERS]
+        [--description=DESCRIPTION] [--headers=[KEY=VALUE,...]]
         [--http-method=HTTP_METHOD; default="post"]
         [--max-backoff=MAX_BACKOFF; default="1h"]
         [--max-doublings=MAX_DOUBLINGS; default=16]
@@ -101,7 +101,7 @@ OPTIONAL FLAGS
      --description=DESCRIPTION
         Human-readable description of the job.
 
-     --headers=HEADERS
+     --headers=[KEY=VALUE,...]
         KEY=VALUE pairs of HTTP headers to include in the request. Cannot be
         repeated. For example: --headers
         Accept-Language=en-us,Accept=text/plain
diff --git a/gcloud/alpha/scheduler/jobs/update/app-engine b/gcloud/alpha/scheduler/jobs/update/app-engine
index 66a13b6f5..f6bcb8a8b 100644
--- a/gcloud/alpha/scheduler/jobs/update/app-engine
+++ b/gcloud/alpha/scheduler/jobs/update/app-engine
@@ -8,7 +8,7 @@ SYNOPSIS
         [--http-method=HTTP_METHOD; default="post"] [--schedule=SCHEDULE]
         [--version=VERSION]
         [--clear-headers | --remove-headers=[REMOVE_HEADERS,...]
-          --update-headers=[UPDATE_HEADERS,...]]
+          --update-headers=[KEY=VALUE,...]]
         [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="1h"]
         [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=16]
         [--clear-max-retry-attempts | --max-retry-attempts=MAX_RETRY_ATTEMPTS]
@@ -108,7 +108,7 @@ FLAGS
           KEY1,KEY2 list of HTTP headers to remove from the request.
           --remove-headers Accept-Language,Accept
 
-       --update-headers=[UPDATE_HEADERS,...]
+       --update-headers=[KEY=VALUE,...]
           KEY=VALUE pairs of HTTP headers to include in the request. Cannot be
           repeated. For example: --update-headers
           Accept-Language=en-us,Accept=text/plain
diff --git a/gcloud/alpha/scheduler/jobs/update/http b/gcloud/alpha/scheduler/jobs/update/http
index 3fcebada9..72e5a7e78 100644
--- a/gcloud/alpha/scheduler/jobs/update/http
+++ b/gcloud/alpha/scheduler/jobs/update/http
@@ -13,7 +13,7 @@ SYNOPSIS
           | [--oidc-service-account-email=OIDC_SERVICE_ACCOUNT_EMAIL
           : --oidc-token-audience=OIDC_TOKEN_AUDIENCE]]
         [--clear-headers | --remove-headers=[REMOVE_HEADERS,...]
-          --update-headers=[UPDATE_HEADERS,...]]
+          --update-headers=[KEY=VALUE,...]]
         [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="1h"]
         [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=16]
         [--clear-max-retry-attempts | --max-retry-attempts=MAX_RETRY_ATTEMPTS]
@@ -163,7 +163,7 @@ FLAGS
           KEY1,KEY2 list of HTTP headers to remove from the request.
           --remove-headers Accept-Language,Accept
 
-       --update-headers=[UPDATE_HEADERS,...]
+       --update-headers=[KEY=VALUE,...]
           KEY=VALUE pairs of HTTP headers to include in the request. Cannot be
           repeated. For example: --update-headers
           Accept-Language=en-us,Accept=text/plain
diff --git a/gcloud/alpha/scheduler/jobs/update/pubsub b/gcloud/alpha/scheduler/jobs/update/pubsub
index 7b78b6f81..237961296 100644
--- a/gcloud/alpha/scheduler/jobs/update/pubsub
+++ b/gcloud/alpha/scheduler/jobs/update/pubsub
@@ -6,7 +6,7 @@ SYNOPSIS
     gcloud alpha scheduler jobs update pubsub (JOB : --location=LOCATION)
         [--description=DESCRIPTION] [--schedule=SCHEDULE] [--topic=TOPIC]
         [--clear-attributes | --remove-attributes=[REMOVE_ATTRIBUTES,...]
-          --update-attributes=[UPDATE_ATTRIBUTES,...]]
+          --update-attributes=[KEY=VALUE,...]]
         [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="1h"]
         [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=16]
         [--clear-max-retry-attempts | --max-retry-attempts=MAX_RETRY_ATTEMPTS]
@@ -95,7 +95,7 @@ FLAGS
           Comma-separated list of attribute keys to remove with the form
           "KEY1,KEY2".
 
-       --update-attributes=[UPDATE_ATTRIBUTES,...]
+       --update-attributes=[KEY=VALUE,...]
           Comma-separated list of attributes. Each attribute has the form
           "NAME=VALUE". You can specify up to 100 attributes.
 
diff --git a/gcloud/alpha/telco-automation/orchestration-cluster/create b/gcloud/alpha/telco-automation/orchestration-cluster/create
index 79f29042d..a1244ed86 100644
--- a/gcloud/alpha/telco-automation/orchestration-cluster/create
+++ b/gcloud/alpha/telco-automation/orchestration-cluster/create
@@ -5,7 +5,8 @@ NAME
 SYNOPSIS
     gcloud alpha telco-automation orchestration-cluster create
         (ORCHESTRATION_CLUSTER : --location=LOCATION) [--async]
-        [--cidr-blocks=CIDR_BLOCKS] [--cluster-cidr-block=CLUSTER_CIDR_BLOCK]
+        [--cidr-blocks=[cidr-block=CIDR-BLOCK],[display-name=DISPLAY-NAME]]
+        [--cluster-cidr-block=CLUSTER_CIDR_BLOCK]
         [--cluster-named-range=CLUSTER_NAMED_RANGE] [--full-management-config]
         [--master-ipv4-cidr-block=MASTER_IPV4_CIDR_BLOCK]
         [--services-cidr-block=SERVICES_CIDR_BLOCK]
@@ -59,7 +60,7 @@ FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
-     --cidr-blocks=CIDR_BLOCKS
+     --cidr-blocks=[cidr-block=CIDR-BLOCK],[display-name=DISPLAY-NAME]
         Master Authorized Network that supports multiple CIDR blocks. Allows
         access to the k8s master from multiple blocks.
 
diff --git a/gcloud/alpha/workstations/clusters/create b/gcloud/alpha/workstations/clusters/create
index 15e786666..52c4cc0ff 100644
--- a/gcloud/alpha/workstations/clusters/create
+++ b/gcloud/alpha/workstations/clusters/create
@@ -3,7 +3,7 @@ NAME
 
 SYNOPSIS
     gcloud alpha workstations clusters create (CLUSTER : --region=REGION)
-        [--async] [--enable-private-endpoint] [--labels=[LABELS,...]]
+        [--async] [--enable-private-endpoint] [--labels=[KEY=VALUE,...]]
         [--network=NETWORK] [--subnetwork=SUBNETWORK] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -64,7 +64,7 @@ FLAGS
         workstations from public networks, but requires additional
         configuration. Learn more: https://cloud.google.com/workstations/docs.
 
-     --labels=[LABELS,...]
+     --labels=[KEY=VALUE,...]
         Labels that are applied to the cluster and propagated to the underlying
         Compute Engine resources.
 
diff --git a/gcloud/alpha/workstations/create b/gcloud/alpha/workstations/create
index e69369f2e..4bbb7d3f6 100644
--- a/gcloud/alpha/workstations/create
+++ b/gcloud/alpha/workstations/create
@@ -4,7 +4,7 @@ NAME
 SYNOPSIS
     gcloud alpha workstations create
         (WORKSTATION : --cluster=CLUSTER --config=CONFIG --region=REGION)
-        [--async] [--labels=[LABELS,...]] [GCLOUD_WIDE_FLAG ...]
+        [--async] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (ALPHA) Create a workstation.
@@ -67,7 +67,7 @@ FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
-     --labels=[LABELS,...]
+     --labels=[KEY=VALUE,...]
         Labels that are applied to the workstation and propagated to the
         underlying Compute Engine resources.
 
diff --git a/gcloud/artifacts/repositories/create b/gcloud/artifacts/repositories/create
index 2e4e67307..7b0140af0 100644
--- a/gcloud/artifacts/repositories/create
+++ b/gcloud/artifacts/repositories/create
@@ -16,7 +16,6 @@ SYNOPSIS
         [--remote-yum-repo=REMOTE_YUM_REPO]
         [--remote-yum-repo-path=REMOTE_YUM_REPO_PATH]
         [--upstream-policy-file=FILE] [--version-policy=VERSION_POLICY]
-        [--allow-sbom-generation | --disable-sbom-generation]
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -191,14 +190,6 @@ OPTIONAL FLAGS
          snapshot
             (Maven only) The repository accepts snapshot versions only.
 
-     At most one of these can be specified:
-
-       --allow-sbom-generation
-          Allow SBOM generation on the repository.
-
-       --disable-sbom-generation
-          Disable SBOM generation on the repository.
-
 GCLOUD WIDE FLAGS
     These flags are available to all commands: --access-token-file, --account,
     --billing-project, --configuration, --flags-file, --flatten, --format,
diff --git a/gcloud/artifacts/repositories/update b/gcloud/artifacts/repositories/update
index 631ac937e..5dd772e51 100644
--- a/gcloud/artifacts/repositories/update
+++ b/gcloud/artifacts/repositories/update
@@ -6,7 +6,6 @@ SYNOPSIS
     gcloud artifacts repositories update (REPOSITORY : --location=LOCATION)
         [--description=DESCRIPTION] [--immutable-tags]
         [--update-labels=[KEY=VALUE,...]] [--upstream-policy-file=FILE]
-        [--allow-sbom-generation | --disable-sbom-generation]
         [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -83,14 +82,6 @@ FLAGS
         "priority": 1 }, { "id": "test2", "repository":
         "projects/p2/locations/us-west2/repository/repo2", "priority": 2 } ]
 
-     At most one of these can be specified:
-
-       --allow-sbom-generation
-          Allow SBOM generation on the repository.
-
-       --disable-sbom-generation
-          Disable SBOM generation on the repository.
-
      At most one of these can be specified:
 
        --clear-labels
diff --git a/gcloud/beta/active-directory/domains/backups/create b/gcloud/beta/active-directory/domains/backups/create
index d82b99ec6..8564eb51f 100644
--- a/gcloud/beta/active-directory/domains/backups/create
+++ b/gcloud/beta/active-directory/domains/backups/create
@@ -4,7 +4,7 @@ NAME
 
 SYNOPSIS
     gcloud beta active-directory domains backups create
-        (BACKUP : --domain=DOMAIN) [--async] [--labels=KEY=VALUE]
+        (BACKUP : --domain=DOMAIN) [--async] [--labels=[KEY=VALUE,...]]
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -64,7 +64,7 @@ FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
 GCLOUD WIDE FLAGS
diff --git a/gcloud/beta/active-directory/domains/create b/gcloud/beta/active-directory/domains/create
index 3e8f9d8b6..c476d98a9 100644
--- a/gcloud/beta/active-directory/domains/create
+++ b/gcloud/beta/active-directory/domains/create
@@ -6,7 +6,7 @@ SYNOPSIS
     gcloud beta active-directory domains create DOMAIN --region=[REGION,...]
         --reserved-ip-range=RESERVED_IP_RANGE [--admin-name=ADMIN_NAME]
         [--async] [--authorized-networks=[AUTHORIZED_NETWORKS,...]]
-        [--enable-audit-logs] [--labels=KEY=VALUE] [GCLOUD_WIDE_FLAG ...]
+        [--enable-audit-logs] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (BETA) Create a new Managed Microsoft AD domain with the given name using
@@ -76,7 +76,7 @@ OPTIONAL FLAGS
         If specified, Active Directory data audit logs are enabled for the
         domain.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
 GCLOUD WIDE FLAGS
diff --git a/gcloud/beta/ai/help b/gcloud/beta/ai/help
index 92ae68fb4..b5a2b66c9 100644
--- a/gcloud/beta/ai/help
+++ b/gcloud/beta/ai/help
@@ -39,6 +39,9 @@ GROUPS
      operations
         (BETA) Manage Vertex AI operations.
 
+     persistent-resources
+        (BETA) Create and manage Vertex AI Persistent Resources.
+
      tensorboard-experiments
         (BETA) Manage Vertex AI Tensorboard experiments.
 
diff --git a/gcloud/beta/ai/persistent-resources/create b/gcloud/beta/ai/persistent-resources/create
new file mode 100644
index 000000000..90ee6ac98
--- /dev/null
+++ b/gcloud/beta/ai/persistent-resources/create
@@ -0,0 +1,191 @@
+NAME
+    gcloud beta ai persistent-resources create - create a new persistent
+        resource
+
+SYNOPSIS
+    gcloud beta ai persistent-resources create
+        --persistent-resource-id=PERSISTENT_RESOURCE_ID
+        (--config=CONFIG --resource-pool-spec=[RESOURCE_POOL_SPEC,...])
+        [--display-name=DISPLAY_NAME] [--enable-custom-service-account]
+        [--labels=[KEY=VALUE,...]] [--network=NETWORK] [--region=REGION]
+        [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING
+          --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command will create a persistent resource on the users project
+    to use with Vertex AI custom training jobs. Persistent resources remain
+    active until they are deleted by the user.
+
+EXAMPLES
+    To create a PersistentResource under project example in region us-central1,
+    run:
+
+        $ gcloud beta ai persistent-resources create --region=us-central1 \
+            --project=example \
+            --resource-pool-spec=replica-count=1,\
+        machine-type='n1-standard-4' --display-name=example-resource
+
+REQUIRED FLAGS
+     --persistent-resource-id=PERSISTENT_RESOURCE_ID
+        User-specified ID of the Persistent Resource.
+
+     resource pool specification.
+
+     At least one of these must be specified:
+
+       --config=CONFIG
+          Path to the Persistent Resource configuration file. This file should
+          be a YAML document containing a list of ResourcePool If an option is
+          specified both in the configuration file **and** via command-line
+          arguments, the command-line arguments override the configuration
+          file. Note that keys with underscore are invalid.
+
+          Example(YAML):
+
+              resourcePoolSpecs:
+                machineSpec:
+                  machineType: n1-standard-4
+                replicaCount: 1
+
+       --resource-pool-spec=[RESOURCE_POOL_SPEC,...]
+          Defines a resource pool to be created in the Persistent Resource. You
+          can include multiple resource pool specs in order to create a
+          Persistent Resource with multiple resource pools.
+
+          The spec can contain the following fields:
+
+           machine-type
+              (Required): The type of the machine. see
+              https://cloud.google.com/vertex-ai/docs/training/configure-compute#machine-types
+              for supported types. This field corresponds to the
+              machineSpec.machineType field in ResourcePool API message.
+           replica-count
+              (Required if autoscaling not enabled) The number of replicas to
+              use when creating this resource pool. This field corresponds to
+              the replicaCount field in 'ResourcePool' API message.
+           min-replica-count
+              (Optional) The minimum number of replicas that autoscaling will
+              down-size to for this resource pool. Both min-replica-count and
+              max-replica-count are required to enable autoscaling on this
+              resource pool. The value for this parameter must be at least 1.
+           max-replica-count
+              (Optional) The maximum number of replicas that autoscaling will
+              create for this resource pool. Both min-replica-count and
+              max-replica-count are required to enable autoscaling on this
+              resource pool. The maximum value for this parameter is 1000.
+           accelerator-type
+              (Optional) The type of GPU to attach to the machines. see
+              https://cloud.google.com/vertex-ai/docs/training/configure-compute#specifying_gpus
+              for more requirements. This field corresponds to the
+              machineSpec.acceleratorType field in ResourcePool API message.
+           accelerator-count
+              (Required with accelerator-type) The number of GPUs for each VM
+              in the resource pool to use. The default the value if 1. This
+              field corresponds to the machineSpec.acceleratorCount field in
+              ResourcePool API message.
+           disk-type
+              (Optional) The type of disk to use for each machine's boot disk
+              in the resource pool. The default is pd-standard. This field
+              corresponds to the diskSpec.bootDiskType field in ResourcePool
+              API message.
+           disk-size
+              (Optional) The disk size in Gb for each machine's boot disk in
+              the resource pool. The default is 100. This field corresponds to
+              the diskSpec.bootDiskSizeGb field in ResourcePool API message.
+
+          Example: --worker-pool-spec=replica-count=1,machine-type=n1-highmem-2
+
+OPTIONAL FLAGS
+     --display-name=DISPLAY_NAME
+        Display name of the Persistent Resource.
+
+     --enable-custom-service-account
+        Whether or not to use a custom user-managed service account with this
+        Persistent Resource.
+
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     --network=NETWORK
+        Full name of the Google Compute Engine network to which the Job is
+        peered with. Private services access must already have been configured.
+        If unspecified, the Job is not peered with any network.
+
+     Region resource - Cloud region to create a Persistent Resource. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --region on the command line with a fully
+        specified name;
+      ◆ set the property ai/region with a fully specified name;
+      ◆ choose one from the prompted list of available regions with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+       --region=REGION
+          ID of the region or fully qualified identifier for the region.
+
+          To set the region attribute:
+          ▸ provide the argument --region on the command line;
+          ▸ set the property ai/region;
+          ▸ choose one from the prompted list of available regions.
+
+     Key resource - The Cloud KMS (Key Management Service) cryptokey that will
+     be used to protect the persistent resource. The 'Vertex AI Service Agent'
+     service account must hold permission 'Cloud KMS CryptoKey
+     Encrypter/Decrypter'. The arguments in this group can be used to specify
+     the attributes of this resource.
+
+       --kms-key=KMS_KEY
+          ID of the key or fully qualified identifier for the key.
+
+          To set the kms-key attribute:
+          ▸ provide the argument --kms-key on the command line.
+
+          This flag argument must be specified if any of the other arguments in
+          this group are specified.
+
+       --kms-keyring=KMS_KEYRING
+          The KMS keyring of the key.
+
+          To set the kms-keyring attribute:
+          ▸ provide the argument --kms-key on the command line with a fully
+            specified name;
+          ▸ provide the argument --kms-keyring on the command line.
+
+       --kms-location=KMS_LOCATION
+          The Google Cloud location for the key.
+
+          To set the kms-location attribute:
+          ▸ provide the argument --kms-key on the command line with a fully
+            specified name;
+          ▸ provide the argument --kms-location on the command line.
+
+       --kms-project=KMS_PROJECT
+          The Google Cloud project for the key.
+
+          To set the kms-project attribute:
+          ▸ provide the argument --kms-key on the command line with a fully
+            specified name;
+          ▸ provide the argument --kms-project on the command line;
+          ▸ set the property core/project.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice.
+
diff --git a/gcloud/beta/ai/persistent-resources/delete b/gcloud/beta/ai/persistent-resources/delete
new file mode 100644
index 000000000..3887d3735
--- /dev/null
+++ b/gcloud/beta/ai/persistent-resources/delete
@@ -0,0 +1,64 @@
+NAME
+    gcloud beta ai persistent-resources delete - delete an active Persistent
+        Resource
+
+SYNOPSIS
+    gcloud beta ai persistent-resources delete
+        (PERSISTENT_RESOURCE : --region=REGION) [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) If the Persistent Resource is not in the active state, the command
+    will not perform any operation.
+
+EXAMPLES
+    To delete a persistent resource 123 under project example in region
+    us-central1, run:
+
+        $ gcloud beta ai persistent-resources delete 123 --project=example \
+            --region=us-central1
+
+POSITIONAL ARGUMENTS
+     Persistent resource resource - The persistent resource to delete. The
+     arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument persistent_resource on the command line with a
+        fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       PERSISTENT_RESOURCE
+          ID of the persistent resource or fully qualified identifier for the
+          persistent resource.
+
+          To set the name attribute:
+          ▸ provide the argument persistent_resource on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --region=REGION
+          Cloud region for the persistent resource.
+
+          To set the region attribute:
+          ▸ provide the argument persistent_resource on the command line with
+            a fully specified name;
+          ▸ provide the argument --region on the command line;
+          ▸ set the property ai/region;
+          ▸ choose one from the prompted list of available regions.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice.
+
diff --git a/gcloud/beta/ai/persistent-resources/describe b/gcloud/beta/ai/persistent-resources/describe
new file mode 100644
index 000000000..1a937238e
--- /dev/null
+++ b/gcloud/beta/ai/persistent-resources/describe
@@ -0,0 +1,60 @@
+NAME
+    gcloud beta ai persistent-resources describe - get detailed information
+        about a PersistentResource with a given id
+
+SYNOPSIS
+    gcloud beta ai persistent-resources describe
+        (PERSISTENT_RESOURCE : --region=REGION) [GCLOUD_WIDE_FLAG ...]
+
+EXAMPLES
+    To get the persistent resource with the PersistentResource id 123 under
+    project example in region us-central1, run:
+
+        $ gcloud beta ai persistent-resources describe 123 \
+            --project=example --region=us-central1
+
+POSITIONAL ARGUMENTS
+     Persistent resource resource - The persistent resource to describe. The
+     arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument persistent_resource on the command line with a
+        fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       PERSISTENT_RESOURCE
+          ID of the persistent resource or fully qualified identifier for the
+          persistent resource.
+
+          To set the name attribute:
+          ▸ provide the argument persistent_resource on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --region=REGION
+          Cloud region for the persistent resource.
+
+          To set the region attribute:
+          ▸ provide the argument persistent_resource on the command line with
+            a fully specified name;
+          ▸ provide the argument --region on the command line;
+          ▸ set the property ai/region;
+          ▸ choose one from the prompted list of available regions.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice.
+
diff --git a/gcloud/beta/ai/persistent-resources/help b/gcloud/beta/ai/persistent-resources/help
new file mode 100644
index 000000000..8595c156d
--- /dev/null
+++ b/gcloud/beta/ai/persistent-resources/help
@@ -0,0 +1,34 @@
+NAME
+    gcloud beta ai persistent-resources - create and manage Vertex AI
+        Persistent Resources
+
+SYNOPSIS
+    gcloud beta ai persistent-resources COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Create and manage Vertex AI Persistent Resources.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        (BETA) Create a new persistent resource.
+
+     delete
+        (BETA) Delete an active Persistent Resource.
+
+     describe
+        (BETA) Get detailed information about a PersistentResource with a given
+        id.
+
+     list
+        (BETA) Lists the active persistent resources.
+
+NOTES
+    This command is currently in beta and might change without notice.
+
diff --git a/gcloud/beta/ai/persistent-resources/list b/gcloud/beta/ai/persistent-resources/list
new file mode 100644
index 000000000..563d6727c
--- /dev/null
+++ b/gcloud/beta/ai/persistent-resources/list
@@ -0,0 +1,81 @@
+NAME
+    gcloud beta ai persistent-resources list - lists the active persistent
+        resources
+
+SYNOPSIS
+    gcloud beta ai persistent-resources list [--region=REGION]
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+EXAMPLES
+    To list the persistent resources of project example in region us-central1,
+    run:
+
+        $ gcloud beta ai persistent-resources list --project=example \
+            --region=us-central1
+
+FLAGS
+     Region resource - Cloud region to list persistent resources. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --region on the command line with a fully
+        specified name;
+      ◆ set the property ai/region with a fully specified name;
+      ◆ choose one from the prompted list of available regions with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+       --region=REGION
+          ID of the region or fully qualified identifier for the region.
+
+          To set the region attribute:
+          ▸ provide the argument --region on the command line;
+          ▸ set the property ai/region;
+          ▸ choose one from the prompted list of available regions.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice.
+
diff --git a/gcloud/beta/alloydb/clusters/create b/gcloud/beta/alloydb/clusters/create
index bf608bba0..550b8e3b0 100644
--- a/gcloud/beta/alloydb/clusters/create
+++ b/gcloud/beta/alloydb/clusters/create
@@ -4,8 +4,8 @@ NAME
 
 SYNOPSIS
     gcloud beta alloydb clusters create CLUSTER --password=PASSWORD
-        --region=REGION [--async] [--database-version=DATABASE_VERSION]
-        [--network=NETWORK]
+        --region=REGION [--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME]
+        [--async] [--database-version=DATABASE_VERSION] [--network=NETWORK]
         [--continuous-backup-recovery-window-days=RECOVERY_PERIOD
           --enable-continuous-backup
           [--continuous-backup-encryption-key=CONTINUOUS_BACKUP_ENCRYPTION_KEY
@@ -42,6 +42,14 @@ REQUIRED FLAGS
         regions at https://cloud.google.com/sql/docs/instance-locations.
 
 OPTIONAL FLAGS
+     --allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME
+        Name of the allocated IP range for the private IP AlloyDB cluster, for
+        example: "google-managed-services-default". If set, the instance IPs
+        for this cluster will be created in the allocated range. The range name
+        must comply with RFC 1035. Specifically, the name must be 1-63
+        characters long and match the regular expression
+        [a-z]([-a-z0-9][a-z0-9])?.
+
      --async
         Return immediately, without waiting for the operation in progress to
         complete.
diff --git a/gcloud/beta/alloydb/clusters/create-secondary b/gcloud/beta/alloydb/clusters/create-secondary
index fb87d7595..86f0e7c1b 100644
--- a/gcloud/beta/alloydb/clusters/create-secondary
+++ b/gcloud/beta/alloydb/clusters/create-secondary
@@ -4,7 +4,8 @@ NAME
 
 SYNOPSIS
     gcloud beta alloydb clusters create-secondary CLUSTER
-        --primary-cluster=PRIMARY_CLUSTER --region=REGION [--async]
+        --primary-cluster=PRIMARY_CLUSTER --region=REGION
+        [--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME] [--async]
         [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING
           --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]
         [GCLOUD_WIDE_FLAG ...]
@@ -33,6 +34,14 @@ REQUIRED FLAGS
         regions at https://cloud.google.com/sql/docs/instance-locations.
 
 OPTIONAL FLAGS
+     --allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME
+        Name of the allocated IP range for the private IP AlloyDB cluster, for
+        example: "google-managed-services-default". If set, the instance IPs
+        for this cluster will be created in the allocated range. The range name
+        must comply with RFC 1035. Specifically, the name must be 1-63
+        characters long and match the regular expression
+        [a-z]([-a-z0-9][a-z0-9])?.
+
      --async
         Return immediately, without waiting for the operation in progress to
         complete.
diff --git a/gcloud/beta/alloydb/clusters/restore b/gcloud/beta/alloydb/clusters/restore
index f8a578812..257de8d41 100644
--- a/gcloud/beta/alloydb/clusters/restore
+++ b/gcloud/beta/alloydb/clusters/restore
@@ -6,7 +6,8 @@ SYNOPSIS
     gcloud beta alloydb clusters restore CLUSTER --region=REGION
         (--backup=BACKUP
           | --point-in-time=POINT_IN_TIME --source-cluster=SOURCE_CLUSTER)
-        [--async] [--network=NETWORK]
+        [--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME] [--async]
+        [--network=NETWORK]
         [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING
           --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]
         [GCLOUD_WIDE_FLAG ...]
@@ -59,6 +60,14 @@ REQUIRED FLAGS
             in this group are specified.
 
 OPTIONAL FLAGS
+     --allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME
+        Name of the allocated IP range for the private IP AlloyDB cluster, for
+        example: "google-managed-services-default". If set, the instance IPs
+        for this cluster will be created in the allocated range. The range name
+        must comply with RFC 1035. Specifically, the name must be 1-63
+        characters long and match the regular expression
+        [a-z]([-a-z0-9][a-z0-9])?.
+
      --async
         Return immediately, without waiting for the operation in progress to
         complete.
diff --git a/gcloud/beta/alloydb/instances/create b/gcloud/beta/alloydb/instances/create
index c1a954a71..6c634bc30 100644
--- a/gcloud/beta/alloydb/instances/create
+++ b/gcloud/beta/alloydb/instances/create
@@ -11,7 +11,9 @@ SYNOPSIS
         [--insights-config-query-string-length=INSIGHTS_CONFIG_QUERY_STRING_LENGTH]
         [--[no-]insights-config-record-application-tags]
         [--[no-]insights-config-record-client-address]
-        [--read-pool-node-count=READ_POOL_NODE_COUNT] [GCLOUD_WIDE_FLAG ...]
+        [--read-pool-node-count=READ_POOL_NODE_COUNT]
+        [--[no-]require-connectors]
+        [--ssl-mode=SSL_MODE; default="ENCRYPTED_ONLY"] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (BETA) Creates a new AlloyDB instance within a given cluster.
@@ -65,13 +67,16 @@ OPTIONAL FLAGS
         complete.
 
      --availability-type=AVAILABILITY_TYPE
-        Specifies level of availability. AVAILABILITY_TYPE must be (only one
-        value is supported):
+        Specifies level of availability. AVAILABILITY_TYPE must be one of:
 
          REGIONAL
-            Provides high availability and is recommended for production
-            instances; instance automatically fails over to another zone within
+            Provide high availability instances. Recommended for production
+            instances; instances automatically fail over to another zone within
             your selected region.
+         ZONAL
+            Provide zonal availability instances. Not recommended for
+            production instances; instance does not automatically fail over to
+            another zone.
 
      --database-flags=FLAG=VALUE,[FLAG=VALUE,...]
         Comma-separated list of database flags to set on the instance. Use an
@@ -105,6 +110,20 @@ OPTIONAL FLAGS
      --read-pool-node-count=READ_POOL_NODE_COUNT
         Read capacity, i.e. number of nodes in a read pool instance.
 
+     --[no-]require-connectors
+        Enable or disable enforcing connectors only (ex: AuthProxy)connections
+        to the database. Use --require-connectors to enable and
+        --no-require-connectors to disable.
+
+     --ssl-mode=SSL_MODE; default="ENCRYPTED_ONLY"
+        Specify the SSL mode to use when the instance connects to the database.
+        Default SSL mode is ENCRYPTED_ONLY. SSL_MODE must be one of:
+
+         ALLOW_UNENCRYPTED_AND_ENCRYPTED
+            SSL connections are optional. CA verification is not enforced.
+         ENCRYPTED_ONLY
+            SSL connections are required. CA verification is not enforced.
+
 GCLOUD WIDE FLAGS
     These flags are available to all commands: --access-token-file, --account,
     --billing-project, --configuration, --flags-file, --flatten, --format,
diff --git a/gcloud/beta/alloydb/instances/create-secondary b/gcloud/beta/alloydb/instances/create-secondary
index edb985fee..872c5e2b8 100644
--- a/gcloud/beta/alloydb/instances/create-secondary
+++ b/gcloud/beta/alloydb/instances/create-secondary
@@ -4,7 +4,8 @@ NAME
 
 SYNOPSIS
     gcloud beta alloydb instances create-secondary INSTANCE --cluster=CLUSTER
-        --region=REGION [--async] [GCLOUD_WIDE_FLAG ...]
+        --region=REGION [--async] [--availability-type=AVAILABILITY_TYPE]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (BETA) Creates a new AlloyDB SECONDARY instance within a given cluster.
@@ -32,6 +33,18 @@ OPTIONAL FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
+     --availability-type=AVAILABILITY_TYPE
+        Specifies level of availability. AVAILABILITY_TYPE must be one of:
+
+         REGIONAL
+            Provide high availability instances. Recommended for production
+            instances; instances automatically fail over to another zone within
+            your selected region.
+         ZONAL
+            Provide zonal availability instances. Not recommended for
+            production instances; instance does not automatically fail over to
+            another zone.
+
 GCLOUD WIDE FLAGS
     These flags are available to all commands: --access-token-file, --account,
     --billing-project, --configuration, --flags-file, --flatten, --format,
diff --git a/gcloud/beta/alloydb/instances/update b/gcloud/beta/alloydb/instances/update
index 63bdac366..f4abd4dd8 100644
--- a/gcloud/beta/alloydb/instances/update
+++ b/gcloud/beta/alloydb/instances/update
@@ -11,6 +11,7 @@ SYNOPSIS
         [--[no-]insights-config-record-application-tags]
         [--[no-]insights-config-record-client-address]
         [--read-pool-node-count=READ_POOL_NODE_COUNT]
+        [--[no-]require-connectors] [--ssl-mode=SSL_MODE]
         [--update-mode=UPDATE_MODE] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -41,13 +42,16 @@ OPTIONAL FLAGS
         complete.
 
      --availability-type=AVAILABILITY_TYPE
-        Specifies level of availability. AVAILABILITY_TYPE must be (only one
-        value is supported):
+        Specifies level of availability. AVAILABILITY_TYPE must be one of:
 
          REGIONAL
-            Provides high availability and is recommended for production
-            instances; instance automatically fails over to another zone within
+            Provide high availability instances. Recommended for production
+            instances; instances automatically fail over to another zone within
             your selected region.
+         ZONAL
+            Provide zonal availability instances. Not recommended for
+            production instances; instance does not automatically fail over to
+            another zone.
 
      --cpu-count=CPU_COUNT
         Whole number value indicating how many vCPUs the machine should
@@ -87,6 +91,20 @@ OPTIONAL FLAGS
      --read-pool-node-count=READ_POOL_NODE_COUNT
         Read capacity, i.e. number of nodes in a read pool instance.
 
+     --[no-]require-connectors
+        Enable or disable enforcing connectors only (ex: AuthProxy)connections
+        to the database. Use --require-connectors to enable and
+        --no-require-connectors to disable.
+
+     --ssl-mode=SSL_MODE
+        Specify the SSL mode to use when the instance connects to the database.
+        SSL_MODE must be one of:
+
+         ALLOW_UNENCRYPTED_AND_ENCRYPTED
+            SSL connections are optional. CA verification is not enforced.
+         ENCRYPTED_ONLY
+            SSL connections are required. CA verification is not enforced.
+
      --update-mode=UPDATE_MODE
         Specify the mode for updating the instance. If unspecified, the update
         would follow a least disruptive approach. UPDATE_MODE must be (only one
diff --git a/gcloud/beta/billing/accounts/add-iam-policy-binding b/gcloud/beta/billing/accounts/add-iam-policy-binding
index deb414ddb..3b3c27cdd 100644
--- a/gcloud/beta/billing/accounts/add-iam-policy-binding
+++ b/gcloud/beta/billing/accounts/add-iam-policy-binding
@@ -64,8 +64,10 @@ API REFERENCE
     API can be found at: https://cloud.google.com/billing/docs/apis
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud billing accounts add-iam-policy-binding
 
         $ gcloud alpha billing accounts add-iam-policy-binding
 
diff --git a/gcloud/beta/billing/accounts/describe b/gcloud/beta/billing/accounts/describe
index b4875ea9e..27b540b1e 100644
--- a/gcloud/beta/billing/accounts/describe
+++ b/gcloud/beta/billing/accounts/describe
@@ -20,7 +20,7 @@ EXAMPLES
 POSITIONAL ARGUMENTS
      ACCOUNT_ID
         Specify a billing account ID. Billing account IDs are of the form
-        0X0X0X-0X0X0X-0X0X0X. To see available IDs, run $ gcloud alpha billing
+        0X0X0X-0X0X0X-0X0X0X. To see available IDs, run $ gcloud billing
         accounts list.
 
 GCLOUD WIDE FLAGS
@@ -36,8 +36,10 @@ API REFERENCE
     API can be found at: https://cloud.google.com/billing/v1/getting-started
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud billing accounts describe
 
         $ gcloud alpha billing accounts describe
 
diff --git a/gcloud/beta/billing/accounts/get-iam-policy b/gcloud/beta/billing/accounts/get-iam-policy
index da0aaf57d..d528bd8b6 100644
--- a/gcloud/beta/billing/accounts/get-iam-policy
+++ b/gcloud/beta/billing/accounts/get-iam-policy
@@ -71,8 +71,10 @@ API REFERENCE
     API can be found at: https://cloud.google.com/billing/docs/apis
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud billing accounts get-iam-policy
 
         $ gcloud alpha billing accounts get-iam-policy
 
diff --git a/gcloud/beta/billing/accounts/help b/gcloud/beta/billing/accounts/help
index ff3bbaa18..c07fa82dd 100644
--- a/gcloud/beta/billing/accounts/help
+++ b/gcloud/beta/billing/accounts/help
@@ -34,8 +34,10 @@ COMMANDS
         (BETA) Set the IAM policy for a Cloud Billing account.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud billing accounts
 
         $ gcloud alpha billing accounts
 
diff --git a/gcloud/beta/billing/accounts/list b/gcloud/beta/billing/accounts/list
index 1a56ac7ec..79acc0063 100644
--- a/gcloud/beta/billing/accounts/list
+++ b/gcloud/beta/billing/accounts/list
@@ -61,8 +61,10 @@ API REFERENCE
     API can be found at: https://cloud.google.com/billing/v1/getting-started
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud billing accounts list
 
         $ gcloud alpha billing accounts list
 
diff --git a/gcloud/beta/billing/accounts/remove-iam-policy-binding b/gcloud/beta/billing/accounts/remove-iam-policy-binding
index dc28e86fc..b12024d85 100644
--- a/gcloud/beta/billing/accounts/remove-iam-policy-binding
+++ b/gcloud/beta/billing/accounts/remove-iam-policy-binding
@@ -65,8 +65,10 @@ API REFERENCE
     API can be found at: https://cloud.google.com/billing/docs/apis
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud billing accounts remove-iam-policy-binding
 
         $ gcloud alpha billing accounts remove-iam-policy-binding
 
diff --git a/gcloud/beta/billing/accounts/set-iam-policy b/gcloud/beta/billing/accounts/set-iam-policy
index 1be0331bd..ba6bd3494 100644
--- a/gcloud/beta/billing/accounts/set-iam-policy
+++ b/gcloud/beta/billing/accounts/set-iam-policy
@@ -56,8 +56,10 @@ API REFERENCE
     API can be found at: https://cloud.google.com/billing/docs/apis
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud billing accounts set-iam-policy
 
         $ gcloud alpha billing accounts set-iam-policy
 
diff --git a/gcloud/beta/billing/budgets/create b/gcloud/beta/billing/budgets/create
index c922fde1b..eed2d3862 100644
--- a/gcloud/beta/billing/budgets/create
+++ b/gcloud/beta/billing/budgets/create
@@ -10,11 +10,11 @@ SYNOPSIS
         [--credit-types-treatment=CREDIT_TYPES_TREATMENT]
         [--disable-default-iam-recipients]
         [--filter-credit-types=[FILTER_CREDIT_TYPES,...]]
-        [--filter-labels=FILTER_LABELS]
+        [--filter-labels=[KEY=VALUE,...]]
         [--filter-projects=[FILTER_PROJECTS,...]]
         [--filter-services=[FILTER_SERVICES,...]]
         [--filter-subaccounts=[FILTER_SUBACCOUNTS,...]]
-        [--threshold-rule=THRESHOLD_RULE]
+        [--threshold-rule=[basis=BASIS],[percent=PERCENT]]
         [--calendar-period=CALENDAR_PERIOD
           | [--start-date=START_DATE : --end-date=END_DATE]]
         [GCLOUD_WIDE_FLAG ...]
@@ -97,7 +97,7 @@ OPTIONAL FLAGS
         specified, then --credit-types-treatment must be
         include-specified-credits.
 
-     --filter-labels=FILTER_LABELS
+     --filter-labels=[KEY=VALUE,...]
         Single label and value pair specifying that usage from only this set of
         labeled resources should be included in the budget. Currently, multiple
         entries or multiple values per entry are not allowed. If omitted, the
@@ -123,7 +123,7 @@ OPTIONAL FLAGS
         include usage from the parent account and all subaccounts, if they
         exist.
 
-     --threshold-rule=THRESHOLD_RULE
+     --threshold-rule=[basis=BASIS],[percent=PERCENT]
         Rule that triggers alerts (notifications of thresholds being crossed)
         when spend exceeds the specified percentages of the budget. This flag
         can be repeated to provide multiple thresholds above which an alert is
diff --git a/gcloud/beta/billing/budgets/update b/gcloud/beta/billing/budgets/update
index 1982cd00c..0faad49de 100644
--- a/gcloud/beta/billing/budgets/update
+++ b/gcloud/beta/billing/budgets/update
@@ -9,7 +9,7 @@ SYNOPSIS
         [--credit-types-treatment=CREDIT_TYPES_TREATMENT]
         [--disable-default-iam-recipients] [--display-name=DISPLAY_NAME]
         [--filter-credit-types=[FILTER_CREDIT_TYPES,...]]
-        [--filter-labels=FILTER_LABELS]
+        [--filter-labels=[KEY=VALUE,...]]
         [--filter-projects=[FILTER_PROJECTS,...]]
         [--filter-services=[FILTER_SERVICES,...]]
         [--filter-subaccounts=[FILTER_SUBACCOUNTS,...]]
@@ -17,8 +17,8 @@ SYNOPSIS
         [--calendar-period=CALENDAR_PERIOD
           | [--start-date=START_DATE : --end-date=END_DATE]]
         [--threshold-rules-from-file=THRESHOLD_RULES_FROM_FILE
-          | --add-threshold-rule=ADD_THRESHOLD_RULE --clear-threshold-rules]
-        [GCLOUD_WIDE_FLAG ...]
+          | --add-threshold-rule=[basis=BASIS],[percent=PERCENT]
+          --clear-threshold-rules] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (BETA) Update a budget.
@@ -98,7 +98,7 @@ FLAGS
         specified, then --credit-types-treatment must be
         include-specified-credits.
 
-     --filter-labels=FILTER_LABELS
+     --filter-labels=[KEY=VALUE,...]
         Single label and value pair specifying that usage from only this set of
         labeled resources should be included in the budget. Currently, multiple
         entries or multiple values per entry are not allowed. If omitted, the
@@ -160,7 +160,7 @@ FLAGS
           in the file will replace the rules in the budget. This can be used to
           add or remove specific threshold rules.
 
-       --add-threshold-rule=ADD_THRESHOLD_RULE
+       --add-threshold-rule=[basis=BASIS],[percent=PERCENT]
           Rule that triggers alerts (notifications of thresholds being crossed)
           when spend exceeds the specified percentages of the budget. This flag
           can be repeated to provide multiple thresholds above which an alert
diff --git a/gcloud/beta/billing/projects/describe b/gcloud/beta/billing/projects/describe
index c1f53e30a..e3dbae512 100644
--- a/gcloud/beta/billing/projects/describe
+++ b/gcloud/beta/billing/projects/describe
@@ -35,8 +35,10 @@ API REFERENCE
     API can be found at: https://cloud.google.com/billing/v1/getting-started
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud billing projects describe
 
         $ gcloud alpha billing projects describe
 
diff --git a/gcloud/beta/billing/projects/help b/gcloud/beta/billing/projects/help
index 940de8599..1b978c071 100644
--- a/gcloud/beta/billing/projects/help
+++ b/gcloud/beta/billing/projects/help
@@ -30,8 +30,10 @@ COMMANDS
         (BETA) Unlink the account (if any) linked with a project.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud billing projects
 
         $ gcloud alpha billing projects
 
diff --git a/gcloud/beta/billing/projects/link b/gcloud/beta/billing/projects/link
index a4a24306d..189bf37a1 100644
--- a/gcloud/beta/billing/projects/link
+++ b/gcloud/beta/billing/projects/link
@@ -38,7 +38,7 @@ POSITIONAL ARGUMENTS
 REQUIRED FLAGS
      --billing-account=ACCOUNT_ID
         Specify a billing account ID. Billing account IDs are of the form
-        0X0X0X-0X0X0X-0X0X0X. To see available IDs, run $ gcloud alpha billing
+        0X0X0X-0X0X0X-0X0X0X. To see available IDs, run $ gcloud billing
         accounts list.
 
 GCLOUD WIDE FLAGS
@@ -54,8 +54,10 @@ API REFERENCE
     API can be found at: https://cloud.google.com/billing/v1/getting-started
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud billing projects link
 
         $ gcloud alpha billing projects link
 
diff --git a/gcloud/beta/billing/projects/list b/gcloud/beta/billing/projects/list
index 5bf9e5e88..211ea921e 100644
--- a/gcloud/beta/billing/projects/list
+++ b/gcloud/beta/billing/projects/list
@@ -20,7 +20,7 @@ EXAMPLES
 REQUIRED FLAGS
      --billing-account=ACCOUNT_ID
         Specify a billing account ID. Billing account IDs are of the form
-        0X0X0X-0X0X0X-0X0X0X. To see available IDs, run $ gcloud alpha billing
+        0X0X0X-0X0X0X-0X0X0X. To see available IDs, run $ gcloud billing
         accounts list.
 
 LIST COMMAND FLAGS
@@ -58,8 +58,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud billing projects list
 
         $ gcloud alpha billing projects list
 
diff --git a/gcloud/beta/billing/projects/unlink b/gcloud/beta/billing/projects/unlink
index 91f31dea0..03194f3e7 100644
--- a/gcloud/beta/billing/projects/unlink
+++ b/gcloud/beta/billing/projects/unlink
@@ -37,8 +37,10 @@ API REFERENCE
     API can be found at: https://cloud.google.com/billing/v1/getting-started
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud billing projects unlink
 
         $ gcloud alpha billing projects unlink
 
diff --git a/gcloud/beta/compute/future-reservations/cancel b/gcloud/beta/compute/future-reservations/cancel
new file mode 100644
index 000000000..23f131e85
--- /dev/null
+++ b/gcloud/beta/compute/future-reservations/cancel
@@ -0,0 +1,73 @@
+NAME
+    gcloud beta compute future-reservations cancel - cancel a Compute Engine
+        future reservation
+
+SYNOPSIS
+    gcloud beta compute future-reservations cancel
+        (FUTURE_RESERVATION : --zone=ZONE) [--async] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Cancel a Compute Engine future reservation.
+
+EXAMPLES
+    To cancel a given Compute Engine future reservation, run:
+
+        $ gcloud beta compute future-reservations cancel my-reservation \
+            --zone=ZONE
+
+POSITIONAL ARGUMENTS
+     Future reservation resource - The name of the future reservation to
+     cancel. The arguments in this group can be used to specify the attributes
+     of this resource. (NOTE) Some attributes are not given arguments in this
+     group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument future_reservation on the command line with a
+        fully specified name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     This must be specified.
+
+       FUTURE_RESERVATION
+          ID of the future reservation or fully qualified identifier for the
+          future reservation.
+
+          To set the future_reservation attribute:
+          ▸ provide the argument future_reservation on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --zone=ZONE
+          The name of the Google Compute Engine zone.
+
+          To set the zone attribute:
+          ▸ provide the argument future_reservation on the command line with
+            a fully specified name;
+          ▸ provide the argument --zone on the command line;
+          ▸ set the property compute/zone.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the compute/beta API. The full documentation for this API
+    can be found at: https://cloud.google.com/compute/
+
+NOTES
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud alpha compute future-reservations cancel
+
diff --git a/gcloud/beta/compute/future-reservations/create b/gcloud/beta/compute/future-reservations/create
new file mode 100644
index 000000000..c8c070956
--- /dev/null
+++ b/gcloud/beta/compute/future-reservations/create
@@ -0,0 +1,226 @@
+NAME
+    gcloud beta compute future-reservations create - create a Compute Engine
+        future reservation
+
+SYNOPSIS
+    gcloud beta compute future-reservations create FUTURE_RESERVATION
+        --[no-]auto-delete-auto-created-reservations --total-count=TOTAL_COUNT
+        (--source-instance-template=SOURCE_INSTANCE_TEMPLATE
+          | [--machine-type=MACHINE_TYPE
+          : --accelerator=[count=COUNT],[type=TYPE]
+          --local-ssd=[count=COUNT],[interface=INTERFACE],[size=SIZE]
+          --min-cpu-platform=MIN_CPU_PLATFORM])
+        (--start-time=START_TIME (--duration=DURATION | --end-time=END_TIME))
+        [--description=DESCRIPTION] [--name-prefix=NAME_PREFIX]
+        [--planning-status=PLANNING_STATUS] [--zone=ZONE]
+        [--auto-created-reservations-delete-time=AUTO_CREATED_RESERVATIONS_DELETE_TIME | --auto-created-reservations-duration=AUTO_CREATED_RESERVATIONS_DURATION]
+        [--share-setting=SHARE_SETTING --share-with=PROJECT,[PROJECT,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Create a Compute Engine reservation.
+
+EXAMPLES
+    To create a Compute Engine future reservation by specifying VM properties
+    using an instance template, run:
+
+        $ gcloud beta compute future-reservations create \
+          my-future-reservation --total-count=1000 \
+          --start-time=2022-11-10 --end-time=2022-12-10 \
+          --name-prefix=prefix-reservation \
+          --source-instance-template=example-instance-template \
+          --zone=fake-zone
+
+    To create a Compute Engine future reservation by directly specifying VM
+    properties, run:
+
+        $ gcloud beta compute future-reservations create \
+          my-future-reservation --total-count=1000 \
+          --start-time=2022-11-10 --end-time=2022-12-10 \
+          --name-prefix=prefix-reservation --machine-type=custom-8-10240 \
+          --min-cpu-platform="Intel Haswell" \
+          --accelerator=count=2,type=nvidia-tesla-v100 \
+          --local-ssd=size=375,interface=scsi
+
+POSITIONAL ARGUMENTS
+     FUTURE_RESERVATION
+        Name of the future reservation to create.
+
+REQUIRED FLAGS
+     --[no-]auto-delete-auto-created-reservations
+        If specified, the auto-created reservations for a future reservation
+        are deleted at the end time (default) or at a specified delete time.
+        Use --auto-delete-auto-created-reservations to enable and
+        --no-auto-delete-auto-created-reservations to disable.
+
+     --total-count=TOTAL_COUNT
+        The total number of instances for which capacity assurance is requested
+        at a future time period.
+
+     Manage the instance properties for the auto-created reservations. You must
+     either provide a source instance template or define the instance
+     properties.
+
+     Exactly one of these must be specified:
+
+       --source-instance-template=SOURCE_INSTANCE_TEMPLATE
+          The url of the instance template that will be used to populate the
+          fields of the reservation. Instance properties can not be defined in
+          addition to source instance template.
+
+       Define individual instance properties for the specific SKU reservation.
+
+         --machine-type=MACHINE_TYPE
+            The type of machine (name only) that has a fixed number of vCPUs
+            and a fixed amount of memory. You can also specify a custom machine
+            type by using the pattern
+            custom-number_of_CPUs-amount_of_memory-for example,
+            custom-32-29440.
+
+            This flag argument must be specified if any of the other arguments
+            in this group are specified.
+
+         --accelerator=[count=COUNT],[type=TYPE]
+            Manage the configuration of the type and number of accelerator
+            cards attached.
+             count
+                The number of accelerators to attach to each instance in the
+                reservation.
+             type
+                The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80)
+                of accelerator to attach to instances in the reservation. Use
+                gcloud compute accelerator-types list to learn about all
+                available accelerator types.
+
+         --local-ssd=[count=COUNT],[interface=INTERFACE],[size=SIZE]
+            Manage the size and the interface of local SSD to use. See
+            https://cloud.google.com/compute/docs/disks/local-ssd for more
+            information.
+             interface
+                The kind of disk interface exposed to the VM for this SSD.
+                Valid values are scsi and nvme. SCSI is the default and is
+                supported by more guest operating systems. NVME may provide
+                higher performance.
+             size
+                The size of the local SSD in base-2 GB.
+             count
+                The number of local SSD to use per VM. Default value is 1.
+
+         --min-cpu-platform=MIN_CPU_PLATFORM
+            Optional minimum CPU platform of the reservation to create.
+
+     Manage the time specific properties for requesting future capacity
+
+     This must be specified.
+
+       --start-time=START_TIME
+          Start time of the Future Reservation. The start time must be an
+          RFC3339 valid string formatted by date, time, and timezone or
+          "YYYY-MM-DDTHH:MM:SSZ"; where YYYY = year, MM = month, DD = day, HH =
+          hours, MM = minutes, SS = seconds, and Z = timezone (i.e.
+          2021-11-20T07:00:00Z).
+
+          This flag argument must be specified if any of the other arguments in
+          this group are specified.
+
+       Exactly one of these must be specified:
+
+         --duration=DURATION
+            Alternate way of specifying time in the number of seconds to
+            terminate capacity request relative to the start time of a request.
+
+         --end-time=END_TIME
+            End time of the Future Reservation. The end time must be an RFC3339
+            valid string formatted by date, time, and timezone or
+            "YYYY-MM-DDTHH:MM:SSZ"; where YYYY = year, MM = month, DD = day, HH
+            = hours, MM = minutes, SS = seconds, and Z = timezone (i.e.
+            2021-11-20T07:00:00Z).
+
+OPTIONAL FLAGS
+     --description=DESCRIPTION
+        An optional description of the future reservation to create.
+
+     --name-prefix=NAME_PREFIX
+        A name prefix for the auto-created reservations when capacity is
+        delivered at the start time. Each auto-created reservation name starts
+        with the name prefix.
+
+     --planning-status=PLANNING_STATUS
+        The planning status of the future reservation. The default value is
+        DRAFT. While in DRAFT, any changes to the future reservation's
+        properties will be allowed. If set to SUBMITTED, the future reservation
+        will submit and its procurementStatus will change to PENDING_APPROVAL.
+        Once the future reservation is pending approval, changes to the future
+        reservation's properties will not be allowed. PLANNING_STATUS must be
+        one of:
+
+         DRAFT
+            Default planning status value.
+         SUBMITTED
+            Planning status value to immediately submit the future reservation.
+
+     --zone=ZONE
+        Zone of the future reservation to create. If not specified and the
+        compute/zone property isn't set, you might be prompted to select a zone
+        (interactive mode only).
+
+        To avoid prompting when this flag is omitted, you can set the
+        compute/zone property:
+
+            $ gcloud config set compute/zone ZONE
+
+        A list of zones can be fetched by running:
+
+            $ gcloud compute zones list
+
+        To unset the property, run:
+
+            $ gcloud config unset compute/zone
+
+        Alternatively, the zone can be stored in the environment variable
+        CLOUDSDK_COMPUTE_ZONE.
+
+     Manage the auto-delete time properties.
+
+     At most one of these can be specified:
+
+       --auto-created-reservations-delete-time=AUTO_CREATED_RESERVATIONS_DELETE_TIME
+          Automatically deletes an auto-created reservations at a specific
+          time. The specified time must be an RFC3339 timestamp, which must be
+          formatted as "YYYY-MM-DDTHH:MM:SSZ" where YYYY = year, MM = month, DD
+          = day, HH = hours, MM = minutes, SS = seconds, and Z = time zone in
+          Coordinated Universal Time (UTC). For example, specify
+          2021-11-20T07:00:00Z.
+
+       --auto-created-reservations-duration=AUTO_CREATED_RESERVATIONS_DURATION
+          Automatically deletes an auto-created reservations after a specified
+          number of days, hours, minutes, or seconds. For example, specify 30m
+          for 30 minutes, or 1d2h3m4s for 1 day, 2 hours, 3 minutes, and 4
+          seconds. For more information, see $ gcloud topic datetimes.
+
+     Manage the properties of a shared reservation.
+
+       --share-setting=SHARE_SETTING
+          Specify if this future reservation is shared, and if so, the type of
+          sharing. If you omit this flag, this value is local by default.
+          SHARE_SETTING must be one of: local, projects.
+
+       --share-with=PROJECT,[PROJECT,...]
+          If this future reservation is shared, provide a comma-separated list
+          of projects that this future reservation is shared with. The list
+          must contain project IDs or project numbers.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud alpha compute future-reservations create
+
diff --git a/gcloud/beta/compute/future-reservations/delete b/gcloud/beta/compute/future-reservations/delete
new file mode 100644
index 000000000..014ebbd5e
--- /dev/null
+++ b/gcloud/beta/compute/future-reservations/delete
@@ -0,0 +1,73 @@
+NAME
+    gcloud beta compute future-reservations delete - delete a Compute Engine
+        future reservation
+
+SYNOPSIS
+    gcloud beta compute future-reservations delete
+        (FUTURE_RESERVATION : --zone=ZONE) [--async] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Delete a Compute Engine future reservation.
+
+EXAMPLES
+    To delete a given Compute Engine future reservation, run:
+
+        $ gcloud beta compute future-reservations delete my-reservation \
+            --zone=ZONE
+
+POSITIONAL ARGUMENTS
+     Future reservation resource - The name of the future reservation to
+     delete. The arguments in this group can be used to specify the attributes
+     of this resource. (NOTE) Some attributes are not given arguments in this
+     group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument future_reservation on the command line with a
+        fully specified name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     This must be specified.
+
+       FUTURE_RESERVATION
+          ID of the future reservation or fully qualified identifier for the
+          future reservation.
+
+          To set the future_reservation attribute:
+          ▸ provide the argument future_reservation on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --zone=ZONE
+          The name of the Google Compute Engine zone.
+
+          To set the zone attribute:
+          ▸ provide the argument future_reservation on the command line with
+            a fully specified name;
+          ▸ provide the argument --zone on the command line;
+          ▸ set the property compute/zone.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the compute/beta API. The full documentation for this API
+    can be found at: https://cloud.google.com/compute/
+
+NOTES
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud alpha compute future-reservations delete
+
diff --git a/gcloud/beta/compute/future-reservations/describe b/gcloud/beta/compute/future-reservations/describe
new file mode 100644
index 000000000..71e041c41
--- /dev/null
+++ b/gcloud/beta/compute/future-reservations/describe
@@ -0,0 +1,68 @@
+NAME
+    gcloud beta compute future-reservations describe - show details about a
+        Compute Engine future reservation
+
+SYNOPSIS
+    gcloud beta compute future-reservations describe
+        (FUTURE_RESERVATION : --zone=ZONE) [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Show details about a Compute Engine future reservation.
+
+EXAMPLES
+    To describe a given Compute Engine future reservation, run:
+
+        $ gcloud beta compute future-reservations describe my-reservation \
+            --zone=ZONE
+
+POSITIONAL ARGUMENTS
+     Future reservation resource - The name of the future reservation to
+     describe. The arguments in this group can be used to specify the
+     attributes of this resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument future_reservation on the command line with a
+        fully specified name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     This must be specified.
+
+       FUTURE_RESERVATION
+          ID of the future reservation or fully qualified identifier for the
+          future reservation.
+
+          To set the future_reservation attribute:
+          ▸ provide the argument future_reservation on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --zone=ZONE
+          The name of the Google Compute Engine zone.
+
+          To set the zone attribute:
+          ▸ provide the argument future_reservation on the command line with
+            a fully specified name;
+          ▸ provide the argument --zone on the command line;
+          ▸ set the property compute/zone.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the compute/beta API. The full documentation for this API
+    can be found at: https://cloud.google.com/compute/
+
+NOTES
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud alpha compute future-reservations describe
+
diff --git a/gcloud/beta/compute/future-reservations/help b/gcloud/beta/compute/future-reservations/help
new file mode 100644
index 000000000..3a482a508
--- /dev/null
+++ b/gcloud/beta/compute/future-reservations/help
@@ -0,0 +1,42 @@
+NAME
+    gcloud beta compute future-reservations - manage Compute Engine future
+        reservations
+
+SYNOPSIS
+    gcloud beta compute future-reservations COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Manage Compute Engine future reservations.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     cancel
+        (BETA) Cancel a Compute Engine future reservation.
+
+     create
+        (BETA) Create a Compute Engine future reservation.
+
+     delete
+        (BETA) Delete a Compute Engine future reservation.
+
+     describe
+        (BETA) Show details about a Compute Engine future reservation.
+
+     list
+        (BETA) List Compute Engine future reservations.
+
+     update
+        (BETA) Update Compute Engine future reservations.
+
+NOTES
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud alpha compute future-reservations
+
diff --git a/gcloud/beta/compute/future-reservations/list b/gcloud/beta/compute/future-reservations/list
new file mode 100644
index 000000000..5f547d72a
--- /dev/null
+++ b/gcloud/beta/compute/future-reservations/list
@@ -0,0 +1,63 @@
+NAME
+    gcloud beta compute future-reservations list - list Compute Engine future
+        reservations
+
+SYNOPSIS
+    gcloud beta compute future-reservations list [--filter=EXPRESSION]
+        [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) List Compute Engine future reservations.
+
+EXAMPLES
+    To list all Compute Engine future reservations, run:
+
+        $ gcloud beta compute future-reservations list my-future-reservation
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud alpha compute future-reservations list
+
diff --git a/gcloud/beta/compute/future-reservations/update b/gcloud/beta/compute/future-reservations/update
new file mode 100644
index 000000000..eb353b820
--- /dev/null
+++ b/gcloud/beta/compute/future-reservations/update
@@ -0,0 +1,222 @@
+NAME
+    gcloud beta compute future-reservations update - update Compute Engine
+        future reservations
+
+SYNOPSIS
+    gcloud beta compute future-reservations update FUTURE_RESERVATION
+        [--[no-]auto-delete-auto-created-reservations]
+        [--description=DESCRIPTION] [--planning-status=PLANNING_STATUS]
+        [--total-count=TOTAL_COUNT] [--zone=ZONE]
+        [--auto-created-reservations-delete-time=AUTO_CREATED_RESERVATIONS_DELETE_TIME | --auto-created-reservations-duration=AUTO_CREATED_RESERVATIONS_DURATION]
+        [--clear-name-prefix | --name-prefix=NAME_PREFIX]
+        [--clear-share-settings
+          | --share-setting=SHARE_SETTING --share-with=PROJECT,[PROJECT,...]]
+        [--machine-type=MACHINE_TYPE --min-cpu-platform=MIN_CPU_PLATFORM
+          --accelerator=[count=COUNT],[type=TYPE]
+          | --clear-accelerator --clear-local-ssd
+          | --local-ssd=[count=COUNT],[interface=INTERFACE],[size=SIZE]]
+        [--start-time=START_TIME --duration=DURATION | --end-time=END_TIME]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Update Compute Engine future reservations.
+
+EXAMPLES
+    To update total count, start and end time of a Compute Engine future
+    reservation in us-central1-a, run:
+
+        $ gcloud beta compute future-reservations update \
+          my-future-reservation --total-count=1000 \
+          --start-time=2021-11-10T07:00:00Z \
+          --end-time=2021-12-10T07:00:00Z --zone=us-central1-a
+
+POSITIONAL ARGUMENTS
+     FUTURE_RESERVATION
+        Name of the future reservation to update.
+
+FLAGS
+     --[no-]auto-delete-auto-created-reservations
+        If specified, the auto-created reservations for a future reservation
+        are deleted at the end time (default) or at a specified delete time.
+        Use --auto-delete-auto-created-reservations to enable and
+        --no-auto-delete-auto-created-reservations to disable.
+
+     --description=DESCRIPTION
+        An optional description of the future reservation to create.
+
+     --planning-status=PLANNING_STATUS
+        The planning status of the future reservation. The default value is
+        DRAFT. While in DRAFT, any changes to the future reservation's
+        properties will be allowed. If set to SUBMITTED, the future reservation
+        will submit and its procurementStatus will change to PENDING_APPROVAL.
+        Once the future reservation is pending approval, changes to the future
+        reservation's properties will not be allowed. PLANNING_STATUS must be
+        one of:
+
+         DRAFT
+            Default planning status value.
+         SUBMITTED
+            Planning status value to immediately submit the future reservation.
+
+     --total-count=TOTAL_COUNT
+        The total number of instances for which capacity assurance is requested
+        at a future time period.
+
+     --zone=ZONE
+        Zone of the future reservation to update. If not specified and the
+        compute/zone property isn't set, you might be prompted to select a zone
+        (interactive mode only).
+
+        To avoid prompting when this flag is omitted, you can set the
+        compute/zone property:
+
+            $ gcloud config set compute/zone ZONE
+
+        A list of zones can be fetched by running:
+
+            $ gcloud compute zones list
+
+        To unset the property, run:
+
+            $ gcloud config unset compute/zone
+
+        Alternatively, the zone can be stored in the environment variable
+        CLOUDSDK_COMPUTE_ZONE.
+
+     Manage the auto-delete time properties.
+
+     At most one of these can be specified:
+
+       --auto-created-reservations-delete-time=AUTO_CREATED_RESERVATIONS_DELETE_TIME
+          Automatically deletes an auto-created reservations at a specific
+          time. The specified time must be an RFC3339 timestamp, which must be
+          formatted as "YYYY-MM-DDTHH:MM:SSZ" where YYYY = year, MM = month, DD
+          = day, HH = hours, MM = minutes, SS = seconds, and Z = time zone in
+          Coordinated Universal Time (UTC). For example, specify
+          2021-11-20T07:00:00Z.
+
+       --auto-created-reservations-duration=AUTO_CREATED_RESERVATIONS_DURATION
+          Automatically deletes an auto-created reservations after a specified
+          number of days, hours, minutes, or seconds. For example, specify 30m
+          for 30 minutes, or 1d2h3m4s for 1 day, 2 hours, 3 minutes, and 4
+          seconds. For more information, see $ gcloud topic datetimes.
+
+     Manage the name-prefix of a future reservation.
+
+     At most one of these can be specified:
+
+       --clear-name-prefix
+          Clears the name prefix for the system generated reservations.
+
+       --name-prefix=NAME_PREFIX
+          A name prefix for the auto-created reservations when capacity is
+          delivered at the start time. Each auto-created reservation name
+          starts with the name prefix.
+
+     Manage the properties of a shared future reservation.
+
+     At most one of these can be specified:
+
+       --clear-share-settings
+          Clear share settings on future reservation. This will result in
+          non-shared future reservation.
+
+       Manage the share settings of a future reservation.
+
+         --share-setting=SHARE_SETTING
+            Specify if this future reservation is shared, and if so, the type
+            of sharing. If you omit this flag, this value is local by default.
+            SHARE_SETTING must be one of: local, projects.
+
+         --share-with=PROJECT,[PROJECT,...]
+            If this future reservation is shared, provide a comma-separated
+            list of projects that this future reservation is shared with. The
+            list must contain project IDs or project numbers.
+
+     Manage the specific SKU reservation properties.
+
+       --machine-type=MACHINE_TYPE
+          The type of machine (name only) that has a fixed number of vCPUs and
+          a fixed amount of memory. You can also specify a custom machine type
+          by using the pattern custom-number_of_CPUs-amount_of_memory-for
+          example, custom-32-29440.
+
+       --min-cpu-platform=MIN_CPU_PLATFORM
+          Optional minimum CPU platform of the reservation to create.
+
+       Manage the accelerators of a future reservation.
+
+       At most one of these can be specified:
+
+         --accelerator=[count=COUNT],[type=TYPE]
+            Manage the configuration of the type and number of accelerator
+            cards attached.
+             count
+                The number of accelerators to attach to each instance in the
+                reservation.
+             type
+                The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80)
+                of accelerator to attach to instances in the reservation. Use
+                gcloud compute accelerator-types list to learn about all
+                available accelerator types.
+
+         --clear-accelerator
+            Remove all accelerators from the future reservation.
+
+       Manage the local ssd of a future reservation.
+
+       At most one of these can be specified:
+
+         --clear-local-ssd
+            Remove all local ssd information on the future reservation.
+
+         --local-ssd=[count=COUNT],[interface=INTERFACE],[size=SIZE]
+            Manage the size and the interface of local SSD to use. See
+            https://cloud.google.com/compute/docs/disks/local-ssd for more
+            information.
+             interface
+                The kind of disk interface exposed to the VM for this SSD.
+                Valid values are scsi and nvme. SCSI is the default and is
+                supported by more guest operating systems. NVME may provide
+                higher performance.
+             size
+                The size of the local SSD in base-2 GB.
+             count
+                The number of local SSD to use per VM. Default value is 1.
+
+     Manage the time specific properties for requesting future capacity
+
+       --start-time=START_TIME
+          Start time of the Future Reservation. The start time must be an
+          RFC3339 valid string formatted by date, time, and timezone or
+          "YYYY-MM-DDTHH:MM:SSZ"; where YYYY = year, MM = month, DD = day, HH =
+          hours, MM = minutes, SS = seconds, and Z = timezone (i.e.
+          2021-11-20T07:00:00Z).
+
+       At most one of these can be specified:
+
+         --duration=DURATION
+            Alternate way of specifying time in the number of seconds to
+            terminate capacity request relative to the start time of a request.
+
+         --end-time=END_TIME
+            End time of the Future Reservation. The end time must be an RFC3339
+            valid string formatted by date, time, and timezone or
+            "YYYY-MM-DDTHH:MM:SSZ"; where YYYY = year, MM = month, DD = day, HH
+            = hours, MM = minutes, SS = seconds, and Z = timezone (i.e.
+            2021-11-20T07:00:00Z).
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud alpha compute future-reservations update
+
diff --git a/gcloud/beta/compute/help b/gcloud/beta/compute/help
index 1d430fc30..97275c644 100644
--- a/gcloud/beta/compute/help
+++ b/gcloud/beta/compute/help
@@ -61,6 +61,9 @@ GROUPS
         (BETA) Read and manipulate traffic forwarding rules to network load
         balancers.
 
+     future-reservations
+        (BETA) Manage Compute Engine future reservations.
+
      health-checks
         (BETA) Read and manipulate health checks for load balanced instances.
 
diff --git a/gcloud/beta/compute/routers/get-nat-ip-info b/gcloud/beta/compute/routers/get-nat-ip-info
new file mode 100644
index 000000000..270d46e53
--- /dev/null
+++ b/gcloud/beta/compute/routers/get-nat-ip-info
@@ -0,0 +1,70 @@
+NAME
+    gcloud beta compute routers get-nat-ip-info - display NAT IP information in
+        a router
+
+SYNOPSIS
+    gcloud beta compute routers get-nat-ip-info NAME [--nat-name=NAT_NAME]
+        [--region=REGION] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) $ gcloud beta compute routers get-nat-ip-info
+
+    shows a mapping of IP:[usage, mode] allocated to each NAT via the specified
+    router.
+
+EXAMPLES
+    To show NAT IP information from all NATs in router 'r1' in region
+    'us-central1', run:
+
+        $ gcloud beta compute routers get-nat-ip-info r1 --region=us-central1
+
+    To show NAT IP information for a specific NAT 'nat1' in router 'r1' in
+    region 'us-central1', run:
+
+        $ gcloud beta compute routers get-nat-ip-info r1 \
+          --region=us-central1 --nat-name="nat1"
+
+POSITIONAL ARGUMENTS
+     NAME
+        Name of the router to get NAT IP info.
+
+FLAGS
+     --nat-name=NAT_NAME
+        The NAT name to filter out NAT IP information
+
+     --region=REGION
+        Region of the router to get NAT IP info. If not specified, you might be
+        prompted to select a region (interactive mode only).
+
+        To avoid prompting when this flag is omitted, you can set the
+        compute/region property:
+
+            $ gcloud config set compute/region REGION
+
+        A list of regions can be fetched by running:
+
+            $ gcloud compute regions list
+
+        To unset the property, run:
+
+            $ gcloud config unset compute/region
+
+        Alternatively, the region can be stored in the environment variable
+        CLOUDSDK_COMPUTE_REGION.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud compute routers get-nat-ip-info
+
+        $ gcloud alpha compute routers get-nat-ip-info
+
diff --git a/gcloud/beta/compute/routers/help b/gcloud/beta/compute/routers/help
index 41d37dbd8..73ce37d41 100644
--- a/gcloud/beta/compute/routers/help
+++ b/gcloud/beta/compute/routers/help
@@ -44,6 +44,9 @@ COMMANDS
      describe
         (BETA) Describe a Compute Engine router.
 
+     get-nat-ip-info
+        (BETA) Display NAT IP information in a router.
+
      get-nat-mapping-info
         (BETA) Display NAT Mapping information in a router.
 
diff --git a/gcloud/beta/container/bare-metal/admin-clusters/create b/gcloud/beta/container/bare-metal/admin-clusters/create
index 46e844e2f..45656f5d6 100644
--- a/gcloud/beta/container/bare-metal/admin-clusters/create
+++ b/gcloud/beta/container/bare-metal/admin-clusters/create
@@ -16,6 +16,7 @@ SYNOPSIS
         ((--lvp-node-mounts-config-path=LVP_NODE_MOUNTS_CONFIG_PATH
           --lvp-node-mounts-config-storage-class=LVP_NODE_MOUNTS_CONFIG_STORAGE_CLASS) ((--lvp-share-path=LVP_SHARE_PATH --lvp-share-storage-class=LVP_SHARE_STORAGE_CLASS) : --shared-path-pv-count=SHARED_PATH_PV_COUNT))
         [--admin-users=ADMIN_USERS] [--annotations=[KEY=VALUE,...]] [--async]
+        [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE]
         [--description=DESCRIPTION] [--enable-application-logs]
         [--login-user=LOGIN_USER]
         [--maintenance-address-cidr-blocks=[MAINTENANCE_ADDRESS_CIDR_BLOCKS,
@@ -200,6 +201,11 @@ OPTIONAL FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
+     --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE
+        Set Binary Authorization evaluation mode for this cluster.
+        BINAUTHZ_EVALUATION_MODE must be one of: DISABLED,
+        PROJECT_SINGLETON_POLICY_ENFORCE.
+
      --description=DESCRIPTION
         Description for the resource.
 
diff --git a/gcloud/beta/container/bare-metal/admin-clusters/update b/gcloud/beta/container/bare-metal/admin-clusters/update
index 8cf97fe2e..6e67ea5d8 100644
--- a/gcloud/beta/container/bare-metal/admin-clusters/update
+++ b/gcloud/beta/container/bare-metal/admin-clusters/update
@@ -5,6 +5,7 @@ NAME
 SYNOPSIS
     gcloud beta container bare-metal admin-clusters update
         (ADMIN_CLUSTER : --location=LOCATION) [--async]
+        [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE]
         [--description=DESCRIPTION] [--enable-application-logs]
         [--island-mode-service-address-cidr-blocks=SERVICE_ADDRESS,[...]]
         [--login-user=LOGIN_USER]
@@ -64,6 +65,11 @@ FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
+     --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE
+        Set Binary Authorization evaluation mode for this cluster.
+        BINAUTHZ_EVALUATION_MODE must be one of: DISABLED,
+        PROJECT_SINGLETON_POLICY_ENFORCE.
+
      --description=DESCRIPTION
         Description for the resource.
 
diff --git a/gcloud/beta/container/bare-metal/clusters/create b/gcloud/beta/container/bare-metal/clusters/create
index 6d7e1c195..0a3d58ad0 100644
--- a/gcloud/beta/container/bare-metal/clusters/create
+++ b/gcloud/beta/container/bare-metal/clusters/create
@@ -39,6 +39,7 @@ SYNOPSIS
         ((--lvp-node-mounts-config-path=LVP_NODE_MOUNTS_CONFIG_PATH
           --lvp-node-mounts-config-storage-class=LVP_NODE_MOUNTS_CONFIG_STORAGE_CLASS) ((--lvp-share-path=LVP_SHARE_PATH --lvp-share-storage-class=LVP_SHARE_STORAGE_CLASS) : --shared-path-pv-count=SHARED_PATH_PV_COUNT))
         [--admin-users=ADMIN_USERS] [--annotations=[KEY=VALUE,...]] [--async]
+        [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE]
         [--description=DESCRIPTION] [--enable-application-logs]
         [--login-user=LOGIN_USER]
         [--maintenance-address-cidr-blocks=[MAINTENANCE_ADDRESS_CIDR_BLOCKS,
@@ -419,6 +420,11 @@ OPTIONAL FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
+     --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE
+        Set Binary Authorization evaluation mode for this cluster.
+        BINAUTHZ_EVALUATION_MODE must be one of: DISABLED,
+        PROJECT_SINGLETON_POLICY_ENFORCE.
+
      --description=DESCRIPTION
         Description for the resource.
 
diff --git a/gcloud/beta/container/bare-metal/clusters/update b/gcloud/beta/container/bare-metal/clusters/update
index 9f0d7f5ca..b1a38677e 100644
--- a/gcloud/beta/container/bare-metal/clusters/update
+++ b/gcloud/beta/container/bare-metal/clusters/update
@@ -5,8 +5,10 @@ NAME
 SYNOPSIS
     gcloud beta container bare-metal clusters update
         (CLUSTER : --location=LOCATION) [--admin-users=ADMIN_USERS]
-        [--allow-missing] [--async] [--description=DESCRIPTION]
-        [--enable-application-logs] [--login-user=LOGIN_USER]
+        [--allow-missing] [--async]
+        [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE]
+        [--description=DESCRIPTION] [--enable-application-logs]
+        [--login-user=LOGIN_USER]
         [--maintenance-address-cidr-blocks=[MAINTENANCE_ADDRESS_CIDR_BLOCKS,
           ...]] [--validate-only] [--version=VERSION]
         [--add-annotations=[KEY1=VALUE1,KEY2=VALUE2,...]
@@ -100,6 +102,11 @@ FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
+     --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE
+        Set Binary Authorization evaluation mode for this cluster.
+        BINAUTHZ_EVALUATION_MODE must be one of: DISABLED,
+        PROJECT_SINGLETON_POLICY_ENFORCE.
+
      --description=DESCRIPTION
         Description for the resource.
 
diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create
index e9a0c9208..f9ebb61e5 100644
--- a/gcloud/beta/container/clusters/create
+++ b/gcloud/beta/container/clusters/create
@@ -830,7 +830,8 @@ FLAGS
      --monitoring=[COMPONENT,...]
         Set the components that have monitoring enabled. Valid component values
         are: SYSTEM, WORKLOAD (Deprecated), NONE, API_SERVER,
-        CONTROLLER_MANAGER, SCHEDULER
+        CONTROLLER_MANAGER, SCHEDULER, DAEMONSET, DEPLOYMENT, HPA, POD,
+        STATEFULSET, STORAGE
 
         For more information, see
         https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics
@@ -838,7 +839,7 @@ FLAGS
         Examples:
 
             $ gcloud beta container clusters create \
-                --monitoring=SYSTEM,API_SERVER
+                --monitoring=SYSTEM,API_SERVER,POD
             $ gcloud beta container clusters create --monitoring=NONE
 
      --network=NETWORK
diff --git a/gcloud/beta/container/clusters/create-auto b/gcloud/beta/container/clusters/create-auto
index 40ff8e536..0edddf90c 100644
--- a/gcloud/beta/container/clusters/create-auto
+++ b/gcloud/beta/container/clusters/create-auto
@@ -231,7 +231,8 @@ FLAGS
      --monitoring=[COMPONENT,...]
         Set the components that have monitoring enabled. Valid component values
         are: SYSTEM, WORKLOAD (Deprecated), NONE, API_SERVER,
-        CONTROLLER_MANAGER, SCHEDULER
+        CONTROLLER_MANAGER, SCHEDULER, DAEMONSET, DEPLOYMENT, HPA, POD,
+        STATEFULSET, STORAGE
 
         For more information, see
         https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics
@@ -239,7 +240,7 @@ FLAGS
         Examples:
 
             $ gcloud beta container clusters create-auto \
-                --monitoring=SYSTEM,API_SERVER
+                --monitoring=SYSTEM,API_SERVER,POD
             $ gcloud beta container clusters create-auto --monitoring=NONE
 
      --network=NETWORK
diff --git a/gcloud/beta/container/clusters/update b/gcloud/beta/container/clusters/update
index 1a0edeeaa..c2d0312e9 100644
--- a/gcloud/beta/container/clusters/update
+++ b/gcloud/beta/container/clusters/update
@@ -1208,7 +1208,8 @@ REQUIRED FLAGS
        --monitoring=[COMPONENT,...]
           Set the components that have monitoring enabled. Valid component
           values are: SYSTEM, WORKLOAD (Deprecated), NONE, API_SERVER,
-          CONTROLLER_MANAGER, SCHEDULER
+          CONTROLLER_MANAGER, SCHEDULER, DAEMONSET, DEPLOYMENT, HPA, POD,
+          STATEFULSET, STORAGE
 
           For more information, see
           https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics
@@ -1216,7 +1217,7 @@ REQUIRED FLAGS
           Examples:
 
               $ gcloud beta container clusters update \
-                  --monitoring=SYSTEM,API_SERVER
+                  --monitoring=SYSTEM,API_SERVER,POD
               $ gcloud beta container clusters update --monitoring=NONE
 
        At most one of these can be specified:
diff --git a/gcloud/beta/container/fleet/create b/gcloud/beta/container/fleet/create
new file mode 100644
index 000000000..adead2f33
--- /dev/null
+++ b/gcloud/beta/container/fleet/create
@@ -0,0 +1,77 @@
+NAME
+    gcloud beta container fleet create - create a fleet
+
+SYNOPSIS
+    gcloud beta container fleet create [--async] [--display-name=DISPLAY_NAME]
+        [--labels=[KEY=VALUE,...]]
+        [--security-posture=SECURITY_POSTURE
+          --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project specified already has a fleet.
+      ▪ The active account does not have permission to access the given
+        project.
+
+EXAMPLES
+    To create a fleet in project example-foo-bar-1 with display name my-fleet,
+    run:
+
+        $ gcloud beta container fleet create --display-name=my-fleet \
+            --project=example-foo-bar-1
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --display-name=DISPLAY_NAME
+        Display name of the fleet to be created (optional). 4-30 characters,
+        alphanumeric and [ '"!-] only.
+
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     Default cluster configurations to apply across the fleet.
+
+       Security posture config.
+
+         --security-posture=SECURITY_POSTURE
+            To apply basic security posture to the clusters of the fleet,
+
+                $ gcloud beta container fleet create --security-posture=basic
+
+            SECURITY_POSTURE must be one of: disabled, basic, enterprise.
+
+         --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING
+            To apply basic vulnerability scanning to the clusters of the fleet,
+
+                $ gcloud beta container fleet create \
+                    --workload-vulnerability-scanning=disabled
+
+            WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, basic,
+            enterprise.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet create
+
+        $ gcloud alpha container fleet create
+
diff --git a/gcloud/beta/container/fleet/delete b/gcloud/beta/container/fleet/delete
new file mode 100644
index 000000000..22f50497b
--- /dev/null
+++ b/gcloud/beta/container/fleet/delete
@@ -0,0 +1,39 @@
+NAME
+    gcloud beta container fleet delete - delete a fleet
+
+SYNOPSIS
+    gcloud beta container fleet delete [--async] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project specified already has a fleet.
+      ▪ The active account does not have permission to access the given
+        project.
+
+EXAMPLES
+    To delete a fleet in project example-foo-bar-1, run:
+
+        $ gcloud beta container fleet delete --project=example-foo-bar-1
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet delete
+
+        $ gcloud alpha container fleet delete
+
diff --git a/gcloud/beta/container/fleet/describe b/gcloud/beta/container/fleet/describe
new file mode 100644
index 000000000..da84fc9a5
--- /dev/null
+++ b/gcloud/beta/container/fleet/describe
@@ -0,0 +1,34 @@
+NAME
+    gcloud beta container fleet describe - show fleet info
+
+SYNOPSIS
+    gcloud beta container fleet describe [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project specified does not have a fleet.
+      ▪ The active account does not have permission to access the given
+        project.
+
+EXAMPLES
+    To print metadata for the fleet in project example-foo-bar-1, run:
+
+        $ gcloud beta container fleet describe --project=example-foo-bar-1
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet describe
+
+        $ gcloud alpha container fleet describe
+
diff --git a/gcloud/beta/container/fleet/help b/gcloud/beta/container/fleet/help
index 7d460113a..592796079 100644
--- a/gcloud/beta/container/fleet/help
+++ b/gcloud/beta/container/fleet/help
@@ -80,6 +80,24 @@ GROUPS
      scopes
         (BETA) Manage scopes of all your GKE fleets.
 
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        (BETA) Create a fleet.
+
+     delete
+        (BETA) Delete a fleet.
+
+     describe
+        (BETA) Show fleet info.
+
+     list
+        (BETA) List fleets visible to the user in an organization.
+
+     update
+        (BETA) Update a fleet.
+
 NOTES
     This command is currently in beta and might change without notice. These
     variants are also available:
diff --git a/gcloud/beta/container/fleet/list b/gcloud/beta/container/fleet/list
new file mode 100644
index 000000000..15b365bfd
--- /dev/null
+++ b/gcloud/beta/container/fleet/list
@@ -0,0 +1,73 @@
+NAME
+    gcloud beta container fleet list - list fleets visible to the user in an
+        organization
+
+SYNOPSIS
+    gcloud beta container fleet list [--organization=ORGANIZATION_ID]
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The org or project specified does not exist.
+      ▪ The user does not have access to the project specified.
+
+EXAMPLES
+    The following command lists fleets in organization 12345:
+
+        $ gcloud beta container fleet list --organization=12345
+
+COMMONLY USED FLAGS
+     --organization=ORGANIZATION_ID
+        ID (number) for the organization to list fleets from. If neither
+        --organization nor --project are provided, defaults to the organization
+        of the active project.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet list
+
+        $ gcloud alpha container fleet list
+
diff --git a/gcloud/beta/container/fleet/memberships/bindings/create b/gcloud/beta/container/fleet/memberships/bindings/create
index 85b340f2e..a5fc83e6c 100644
--- a/gcloud/beta/container/fleet/memberships/bindings/create
+++ b/gcloud/beta/container/fleet/memberships/bindings/create
@@ -96,8 +96,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet memberships bindings create
 
         $ gcloud alpha container fleet memberships bindings create
 
diff --git a/gcloud/beta/container/fleet/memberships/bindings/delete b/gcloud/beta/container/fleet/memberships/bindings/delete
index ebc6da047..461d16f5a 100644
--- a/gcloud/beta/container/fleet/memberships/bindings/delete
+++ b/gcloud/beta/container/fleet/memberships/bindings/delete
@@ -79,8 +79,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet memberships bindings delete
 
         $ gcloud alpha container fleet memberships bindings delete
 
diff --git a/gcloud/beta/container/fleet/memberships/bindings/describe b/gcloud/beta/container/fleet/memberships/bindings/describe
index 79d6c1a17..d93fe059c 100644
--- a/gcloud/beta/container/fleet/memberships/bindings/describe
+++ b/gcloud/beta/container/fleet/memberships/bindings/describe
@@ -79,8 +79,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet memberships bindings describe
 
         $ gcloud alpha container fleet memberships bindings describe
 
diff --git a/gcloud/beta/container/fleet/memberships/bindings/help b/gcloud/beta/container/fleet/memberships/bindings/help
index d84d8fa6b..3e26d98c6 100644
--- a/gcloud/beta/container/fleet/memberships/bindings/help
+++ b/gcloud/beta/container/fleet/memberships/bindings/help
@@ -39,8 +39,10 @@ COMMANDS
         (BETA) Update the Binding in a Membership.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet memberships bindings
 
         $ gcloud alpha container fleet memberships bindings
 
diff --git a/gcloud/beta/container/fleet/memberships/bindings/list b/gcloud/beta/container/fleet/memberships/bindings/list
index 2008865fd..2d92ae751 100644
--- a/gcloud/beta/container/fleet/memberships/bindings/list
+++ b/gcloud/beta/container/fleet/memberships/bindings/list
@@ -78,8 +78,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet memberships bindings list
 
         $ gcloud alpha container fleet memberships bindings list
 
diff --git a/gcloud/beta/container/fleet/memberships/bindings/update b/gcloud/beta/container/fleet/memberships/bindings/update
index af2707828..1d2ec3eb2 100644
--- a/gcloud/beta/container/fleet/memberships/bindings/update
+++ b/gcloud/beta/container/fleet/memberships/bindings/update
@@ -120,8 +120,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet memberships bindings update
 
         $ gcloud alpha container fleet memberships bindings update
 
diff --git a/gcloud/beta/container/fleet/scopes/add-iam-policy-binding b/gcloud/beta/container/fleet/scopes/add-iam-policy-binding
new file mode 100644
index 000000000..95fda8709
--- /dev/null
+++ b/gcloud/beta/container/fleet/scopes/add-iam-policy-binding
@@ -0,0 +1,89 @@
+NAME
+    gcloud beta container fleet scopes add-iam-policy-binding - add IAM policy
+        binding to a Fleet Scope
+
+SYNOPSIS
+    gcloud beta container fleet scopes add-iam-policy-binding SCOPE
+        --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Add an IAM policy binding to the IAM policy of a Fleet Scope. One
+    binding consists of a member, and a role.
+
+EXAMPLES
+    To add an IAM policy binding for the role of 'roles/gkehub.scopeUser' for
+    the user 'test-user@gmail.com' with scope 'my-scope', run:
+
+        $ gcloud beta container fleet scopes add-iam-policy-binding \
+            my-scope --member='user:test-user@gmail.com' \
+            --role='roles/gkehub.scopeUser'
+
+    See https://cloud.google.com/iam/docs/managing-policies for details of
+    policy role and member types.
+
+POSITIONAL ARGUMENTS
+     Scope resource - The scope for which to add IAM policy binding to. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     To set the location attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+REQUIRED FLAGS
+     --member=PRINCIPAL
+        The principal to add the binding for. Should be of the form
+        user|group|serviceAccount:email or domain:domain.
+
+        Examples: user:test-user@gmail.com, group:admins@example.com,
+        serviceAccount:test123@example.domain.com, or
+        domain:example.domain.com.
+
+        Some resources also accept the following special values:
+        ◆ allUsers - Special identifier that represents anyone who is on the
+          internet, with or without a Google account.
+        ◆ allAuthenticatedUsers - Special identifier that represents anyone
+          who is authenticated with a Google account or a service account.
+
+     --role=ROLE
+        Role name to assign to the principal. The role name is the complete
+        path of a predefined role, such as roles/logging.viewer, or the role ID
+        for a custom role, such as
+        organizations/{ORGANIZATION_ID}/roles/logging.viewer.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1beta API. The full documentation for this
+    API can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet scopes add-iam-policy-binding
+
+        $ gcloud alpha container fleet scopes add-iam-policy-binding
+
diff --git a/gcloud/beta/container/fleet/scopes/create b/gcloud/beta/container/fleet/scopes/create
index a3811854d..4d77e9399 100644
--- a/gcloud/beta/container/fleet/scopes/create
+++ b/gcloud/beta/container/fleet/scopes/create
@@ -68,8 +68,10 @@ API REFERENCE
     https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet scopes create
 
         $ gcloud alpha container fleet scopes create
 
diff --git a/gcloud/beta/container/fleet/scopes/delete b/gcloud/beta/container/fleet/scopes/delete
index 0d66a70fd..f99b5f88e 100644
--- a/gcloud/beta/container/fleet/scopes/delete
+++ b/gcloud/beta/container/fleet/scopes/delete
@@ -70,8 +70,10 @@ API REFERENCE
     https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet scopes delete
 
         $ gcloud alpha container fleet scopes delete
 
diff --git a/gcloud/beta/container/fleet/scopes/describe b/gcloud/beta/container/fleet/scopes/describe
index bebcd8eb6..0e83bfda5 100644
--- a/gcloud/beta/container/fleet/scopes/describe
+++ b/gcloud/beta/container/fleet/scopes/describe
@@ -64,8 +64,10 @@ API REFERENCE
     https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet scopes describe
 
         $ gcloud alpha container fleet scopes describe
 
diff --git a/gcloud/beta/container/fleet/scopes/get-iam-policy b/gcloud/beta/container/fleet/scopes/get-iam-policy
new file mode 100644
index 000000000..ff6eeccba
--- /dev/null
+++ b/gcloud/beta/container/fleet/scopes/get-iam-policy
@@ -0,0 +1,88 @@
+NAME
+    gcloud beta container fleet scopes get-iam-policy - get the IAM policy for
+        a Fleet Scope
+
+SYNOPSIS
+    gcloud beta container fleet scopes get-iam-policy SCOPE
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command gets the IAM policy for a scope.
+
+EXAMPLES
+    To print the IAM policy for a given scope, run:
+
+        $ gcloud beta container fleet scopes get-iam-policy my-scope
+
+POSITIONAL ARGUMENTS
+     Scope resource - The scope for which to display the IAM policy. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     To set the location attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1beta API. The full documentation for this
+    API can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet scopes get-iam-policy
+
+        $ gcloud alpha container fleet scopes get-iam-policy
+
diff --git a/gcloud/beta/container/fleet/scopes/help b/gcloud/beta/container/fleet/scopes/help
index c500195d4..26af13ed4 100644
--- a/gcloud/beta/container/fleet/scopes/help
+++ b/gcloud/beta/container/fleet/scopes/help
@@ -12,9 +12,22 @@ GCLOUD WIDE FLAGS
 
     Run $ gcloud help for details.
 
+GROUPS
+    GROUP is one of the following:
+
+     namespaces
+        (BETA) Fleet namespaces are the fleet equivalent of k8s cluster
+        namespaces.
+
+     rbacrolebindings
+        (BETA) Fleet scope RBAC RoleBindings for permissions.
+
 COMMANDS
     COMMAND is one of the following:
 
+     add-iam-policy-binding
+        (BETA) Add IAM policy binding to a Fleet Scope.
+
      create
         (BETA) Create a new fleet scope.
 
@@ -24,15 +37,23 @@ COMMANDS
      describe
         (BETA) Describe a fleet scope.
 
+     get-iam-policy
+        (BETA) Get the IAM policy for a Fleet Scope.
+
      list
         (BETA) List fleet scopes.
 
+     remove-iam-policy-binding
+        (BETA) Remove IAM policy binding of a Fleet Scope.
+
      update
         (BETA) Update a scope.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet scopes
 
         $ gcloud alpha container fleet scopes
 
diff --git a/gcloud/beta/container/fleet/scopes/list b/gcloud/beta/container/fleet/scopes/list
index 4496b4ae9..a85b6264c 100644
--- a/gcloud/beta/container/fleet/scopes/list
+++ b/gcloud/beta/container/fleet/scopes/list
@@ -60,8 +60,10 @@ API REFERENCE
     https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet scopes list
 
         $ gcloud alpha container fleet scopes list
 
diff --git a/gcloud/beta/container/fleet/scopes/namespaces/create b/gcloud/beta/container/fleet/scopes/namespaces/create
new file mode 100644
index 000000000..b36a1dd90
--- /dev/null
+++ b/gcloud/beta/container/fleet/scopes/namespaces/create
@@ -0,0 +1,90 @@
+NAME
+    gcloud beta container fleet scopes namespaces create - create a fleet
+        namespace
+
+SYNOPSIS
+    gcloud beta container fleet scopes namespaces create
+        (NAMESPACE : --scope=SCOPE) [--labels=[KEY=VALUE,...]]
+        [--namespace-labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project has a fleet namespace with the same name.
+      ▪ The caller does not have permission to access the given project.
+
+EXAMPLES
+    To create a fleet namespace with name NAMESPACE in the active project, run:
+
+        $ gcloud beta container fleet scopes namespaces create NAMESPACE
+
+    To create a fleet namespace in fleet scope SCOPE in project PROJECT_ID with
+    name NAMESPACE, run:
+
+        $ gcloud beta container fleet scopes namespaces create NAMESPACE \
+            --scope=SCOPE --project=PROJECT_ID
+
+POSITIONAL ARGUMENTS
+     Namespace resource - The group of arguments defining the Fleet Namespace.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       NAMESPACE
+          ID of the namespace or fully qualified identifier for the namespace.
+
+          To set the namespace attribute:
+          ▸ provide the argument NAMESPACE on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --scope=SCOPE
+          the
+
+          To set the scope attribute:
+          ▸ provide the argument NAMESPACE on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+FLAGS
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     --namespace-labels=[KEY=VALUE,...]
+        List of namespace-level label KEY=VALUE pairs to add.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet scopes namespaces create
+
+        $ gcloud alpha container fleet scopes namespaces create
+
diff --git a/gcloud/beta/container/fleet/scopes/namespaces/delete b/gcloud/beta/container/fleet/scopes/namespaces/delete
new file mode 100644
index 000000000..569bc5ab0
--- /dev/null
+++ b/gcloud/beta/container/fleet/scopes/namespaces/delete
@@ -0,0 +1,77 @@
+NAME
+    gcloud beta container fleet scopes namespaces delete - delete a fleet
+        namespace
+
+SYNOPSIS
+    gcloud beta container fleet scopes namespaces delete
+        (NAMESPACE : --scope=SCOPE) [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The namespace specified does not exist.
+      ▪ The caller does not have permission to access the given project or
+        namespace.
+
+EXAMPLES
+    To delete fleet namespace NAMESPACE in the active project:
+
+        $ gcloud beta container fleet scopes namespaces delete NAMESPACE
+
+    To delete fleet namespace NAMESPACE in project PROJECT_ID:
+
+        $ gcloud beta container fleet scopes namespaces delete NAMESPACE \
+            --project=PROJECT_ID
+
+POSITIONAL ARGUMENTS
+     Namespace resource - The group of arguments defining the Fleet Namespace.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       NAMESPACE
+          ID of the namespace or fully qualified identifier for the namespace.
+
+          To set the namespace attribute:
+          ▸ provide the argument NAMESPACE on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --scope=SCOPE
+          the
+
+          To set the scope attribute:
+          ▸ provide the argument NAMESPACE on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet scopes namespaces delete
+
+        $ gcloud alpha container fleet scopes namespaces delete
+
diff --git a/gcloud/beta/container/fleet/scopes/namespaces/describe b/gcloud/beta/container/fleet/scopes/namespaces/describe
new file mode 100644
index 000000000..5a48eb897
--- /dev/null
+++ b/gcloud/beta/container/fleet/scopes/namespaces/describe
@@ -0,0 +1,77 @@
+NAME
+    gcloud beta container fleet scopes namespaces describe - show fleet
+        namespace info
+
+SYNOPSIS
+    gcloud beta container fleet scopes namespaces describe
+        (NAMESPACE : --scope=SCOPE) [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The namespace specified does not exist in the project.
+      ▪ The caller does not have permission to access the project or
+        namespace.
+
+EXAMPLES
+    To print metadata for the namespace NAMESPACE in the active project, run:
+
+        $ gcloud beta container fleet scopes namespaces describe NAMESPACE
+
+    To print metadata for the namespace NAMESPACE in project PROJECT_ID, run:
+
+        $ gcloud beta container fleet scopes namespaces describe NAMESPACE \
+            --project=PROJECT_ID
+
+POSITIONAL ARGUMENTS
+     Namespace resource - The group of arguments defining the Fleet Namespace.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       NAMESPACE
+          ID of the namespace or fully qualified identifier for the namespace.
+
+          To set the namespace attribute:
+          ▸ provide the argument NAMESPACE on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --scope=SCOPE
+          the
+
+          To set the scope attribute:
+          ▸ provide the argument NAMESPACE on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet scopes namespaces describe
+
+        $ gcloud alpha container fleet scopes namespaces describe
+
diff --git a/gcloud/beta/container/fleet/scopes/namespaces/get-credentials b/gcloud/beta/container/fleet/scopes/namespaces/get-credentials
new file mode 100644
index 000000000..29fea1992
--- /dev/null
+++ b/gcloud/beta/container/fleet/scopes/namespaces/get-credentials
@@ -0,0 +1,60 @@
+NAME
+    gcloud beta container fleet scopes namespaces get-credentials - fetch
+        credentials for a membership with a particular namespace
+
+SYNOPSIS
+    gcloud beta container fleet scopes namespaces get-credentials NAMESPACE
+        [--membership=MEMBERSHIP] [--membership-location=MEMBERSHIP_LOCATION]
+        [--set-namespace-in-config=SET_NAMESPACE_IN_CONFIG]
+        [GCLOUD_WIDE_FLAG ...]
+
+EXAMPLES
+    Get the Connect Gateway kubeconfig for global membership MEMBERSHIP, using
+    namespace NAMESPACE in the config:
+
+        $ gcloud beta container fleet scopes namespaces get-credentials \
+            NAMESPACE --membership=MEMBERSHIP --membership-location=global \
+            --set-namespace-in-config=true
+
+    Get the Connect Gateway kubeconfig for global membership MEMBERSHIP:
+
+        $ gcloud beta container fleet scopes namespaces get-credentials \
+            NAMESPACE --membership=MEMBERSHIP --membership-location=global
+
+POSITIONAL ARGUMENTS
+     NAMESPACE
+        Name of the namespace for which to get access to memberships.
+
+FLAGS
+     --membership=MEMBERSHIP
+        Membership ID to get credentials from. If not provided, a prompt will
+        offer a list of memberships in the fleet.
+
+     --membership-location=MEMBERSHIP_LOCATION
+        The location of the membership resource, e.g. us-central1. If not
+        specified, defaults to global.
+
+     --set-namespace-in-config=SET_NAMESPACE_IN_CONFIG
+        If true, the default namespace for the context in the generated
+        kubeconfig will be set to the Fleet namespace (i.e. the name given as
+        the positional argument in this command).
+
+        Otherwise, no default namespace will be set, functioning the same as
+        gcloud container fleet memberships get-credentials.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet scopes namespaces get-credentials
+
+        $ gcloud alpha container fleet scopes namespaces get-credentials
+
diff --git a/gcloud/beta/container/fleet/scopes/namespaces/help b/gcloud/beta/container/fleet/scopes/namespaces/help
new file mode 100644
index 000000000..be2476791
--- /dev/null
+++ b/gcloud/beta/container/fleet/scopes/namespaces/help
@@ -0,0 +1,55 @@
+NAME
+    gcloud beta container fleet scopes namespaces - fleet namespaces are the
+        fleet equivalent of k8s cluster namespaces
+
+SYNOPSIS
+    gcloud beta container fleet scopes namespaces COMMAND
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command group allows for manipulation of fleet namespaces.
+
+EXAMPLES
+    Manage fleet namespaces:
+
+        $ gcloud beta container fleet scopes namespaces --help
+
+    Manage RBAC RoleBindings in a fleet namespace:
+
+        $ gcloud beta container fleet scopes namespaces rbacrolebindings \
+            --help
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        (BETA) Create a fleet namespace.
+
+     delete
+        (BETA) Delete a fleet namespace.
+
+     describe
+        (BETA) Show fleet namespace info.
+
+     get-credentials
+        (BETA) Fetch credentials for a membership with a particular namespace.
+
+     list
+        (BETA) List fleet namespaces in a project.
+
+     update
+        (BETA) Update a fleet namespace.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet scopes namespaces
+
+        $ gcloud alpha container fleet scopes namespaces
+
diff --git a/gcloud/beta/container/fleet/scopes/namespaces/list b/gcloud/beta/container/fleet/scopes/namespaces/list
new file mode 100644
index 000000000..2c5a31732
--- /dev/null
+++ b/gcloud/beta/container/fleet/scopes/namespaces/list
@@ -0,0 +1,96 @@
+NAME
+    gcloud beta container fleet scopes namespaces list - list fleet namespaces
+        in a project
+
+SYNOPSIS
+    gcloud beta container fleet scopes namespaces list --scope=SCOPE
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The user does not have access to the project specified.
+
+EXAMPLES
+    The following command lists namespaces in the active project:
+
+        $ gcloud beta container fleet scopes namespaces list
+
+    The following command lists namespaces in project PROJECT_ID:
+
+        $ gcloud beta container fleet scopes namespaces list \
+            --project=PROJECT_ID
+
+REQUIRED FLAGS
+     Scope resource - The group of arguments defining the Fleet Scope. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --scope on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --scope on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       --scope=SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument --scope on the command line.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet scopes namespaces list
+
+        $ gcloud alpha container fleet scopes namespaces list
+
diff --git a/gcloud/beta/container/fleet/scopes/namespaces/update b/gcloud/beta/container/fleet/scopes/namespaces/update
new file mode 100644
index 000000000..199c3a32d
--- /dev/null
+++ b/gcloud/beta/container/fleet/scopes/namespaces/update
@@ -0,0 +1,141 @@
+NAME
+    gcloud beta container fleet scopes namespaces update - update a fleet
+        namespace
+
+SYNOPSIS
+    gcloud beta container fleet scopes namespaces update
+        (NAMESPACE : --scope=SCOPE) [--update-labels=[KEY=VALUE,...]]
+        [--update-namespace-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]]
+        [--clear-namespace-labels | --remove-namespace-labels=[KEY,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The fleet namespace does not exist in the project.
+      ▪ The caller does not have permission to access the project or
+        namespace.
+
+EXAMPLES
+    To update the namespace NAMESPACE in the active project:
+
+        $ gcloud beta container fleet scopes namespaces update NAMESPACE
+
+    To update the namespace NAMESPACE in project PROJECT_ID:
+
+        $ gcloud beta container fleet scopes namespaces update NAMESPACE \
+            --project=PROJECT_ID
+
+POSITIONAL ARGUMENTS
+     Namespace resource - The group of arguments defining the Fleet Namespace.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       NAMESPACE
+          ID of the namespace or fully qualified identifier for the namespace.
+
+          To set the namespace attribute:
+          ▸ provide the argument NAMESPACE on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --scope=SCOPE
+          the
+
+          To set the scope attribute:
+          ▸ provide the argument NAMESPACE on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+FLAGS
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     --update-namespace-labels=[KEY=VALUE,...]
+        List of namespace-level label KEY=VALUE pairs to update in the cluster
+        namespace. If a label exists, its value is modified. Otherwise, a new
+        label is' created.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud beta container fleet scopes namespaces update --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud beta container fleet scopes namespaces update \
+                --clear-labels --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+     At most one of these can be specified:
+
+       --clear-namespace-labels
+          Remove all namespace-level labels from the cluster namespace. If
+          --update-namespace-labels is also specified then
+          --clear-namespace-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud beta container fleet scopes namespaces update \
+                namespace_name --clear-namespace-labels
+
+          To remove all existing namespace-level labels and create two new
+          labels, foo and baz:
+
+              $ gcloud beta container fleet scopes namespaces update \
+                namespace_name --clear-namespace-labels \
+                --update-namespace-labels foo=bar,baz=qux
+
+       --remove-namespace-labels=[KEY,...]
+          List of namespace-level label keys to remove in the cluster
+          namespace. If a label does not exist it is silently ignored. If
+          --update-namespace-labels is also specified then
+          --update-namespace-labels is applied first.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet scopes namespaces update
+
+        $ gcloud alpha container fleet scopes namespaces update
+
diff --git a/gcloud/beta/container/fleet/scopes/rbacrolebindings/create b/gcloud/beta/container/fleet/scopes/rbacrolebindings/create
new file mode 100644
index 000000000..24d4666ef
--- /dev/null
+++ b/gcloud/beta/container/fleet/scopes/rbacrolebindings/create
@@ -0,0 +1,106 @@
+NAME
+    gcloud beta container fleet scopes rbacrolebindings create - create an RBAC
+        RoleBinding
+
+SYNOPSIS
+    gcloud beta container fleet scopes rbacrolebindings create
+        (NAME : --location=LOCATION --scope=SCOPE) --role=ROLE
+        (--group=GROUP | --user=USER) [--labels=[KEY=VALUE,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The RBAC RoleBinding already exists.
+      ▪ The caller does not have permission to access the given scope.
+
+EXAMPLES
+    To create an admin RBAC RoleBinding RBRB in scope SCOPE for user
+    person@google.com, run:
+
+        $ gcloud beta container fleet scopes rbacrolebindings create RBRB \
+            --scope=SCOPE --role=admin --user=person@google.com
+
+    To create a viewer RBAC RoleBinding RBRB in scope SCOPE for group
+    people@google.com, run:
+
+        $ gcloud beta container fleet scopes rbacrolebindings create RBRB \
+            --scope=SCOPE --role=viewer --group=people@google.com
+
+POSITIONAL ARGUMENTS
+     Rbacrolebinding resource - The group of arguments defining an
+     RBACRoleBinding. The arguments in this group can be used to specify the
+     attributes of this resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAME on the command line with a fully specified
+        name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       NAME
+          ID of the rbacrolebinding or fully qualified identifier for the
+          rbacrolebinding.
+
+          To set the rbacrolebinding attribute:
+          ▸ provide the argument NAME on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the rbacrolebinding.
+
+          To set the location attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --scope=SCOPE
+          Name of the rbacrolebinding.
+
+          To set the scope attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+REQUIRED FLAGS
+     --role=ROLE
+        Role to assign. ROLE must be one of: admin, edit, view.
+
+     Exactly one of these must be specified:
+
+       --group=GROUP
+          Group for the RoleBinding.
+
+       --user=USER
+          User for the RoleBinding.
+
+OPTIONAL FLAGS
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet scopes rbacrolebindings create
+
+        $ gcloud alpha container fleet scopes rbacrolebindings create
+
diff --git a/gcloud/beta/container/fleet/scopes/rbacrolebindings/delete b/gcloud/beta/container/fleet/scopes/rbacrolebindings/delete
new file mode 100644
index 000000000..2d7cf8e0f
--- /dev/null
+++ b/gcloud/beta/container/fleet/scopes/rbacrolebindings/delete
@@ -0,0 +1,76 @@
+NAME
+    gcloud beta container fleet scopes rbacrolebindings delete - delete a fleet
+        scope RBAC RoleBinding
+
+SYNOPSIS
+    gcloud beta container fleet scopes rbacrolebindings delete
+        (NAME : --location=LOCATION --scope=SCOPE) [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The RoleBinding specified does not exist.
+      ▪ The caller does not have permission to access the given RoleBinding.
+
+EXAMPLES
+    To delete RBAC RoleBinding RBRB in scope SCOPE in the active project:
+
+        $ gcloud beta container fleet scopes rbacrolebindings delete RBRB \
+            --scope=SCOPE
+
+POSITIONAL ARGUMENTS
+     Rbacrolebinding resource - The group of arguments defining an
+     RBACRoleBinding. The arguments in this group can be used to specify the
+     attributes of this resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAME on the command line with a fully specified
+        name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       NAME
+          ID of the rbacrolebinding or fully qualified identifier for the
+          rbacrolebinding.
+
+          To set the rbacrolebinding attribute:
+          ▸ provide the argument NAME on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the rbacrolebinding.
+
+          To set the location attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --scope=SCOPE
+          Name of the rbacrolebinding.
+
+          To set the scope attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet scopes rbacrolebindings delete
+
+        $ gcloud alpha container fleet scopes rbacrolebindings delete
+
diff --git a/gcloud/beta/container/fleet/scopes/rbacrolebindings/describe b/gcloud/beta/container/fleet/scopes/rbacrolebindings/describe
new file mode 100644
index 000000000..5865427f3
--- /dev/null
+++ b/gcloud/beta/container/fleet/scopes/rbacrolebindings/describe
@@ -0,0 +1,76 @@
+NAME
+    gcloud beta container fleet scopes rbacrolebindings describe - show fleet
+        scope RBAC RoleBinding information
+
+SYNOPSIS
+    gcloud beta container fleet scopes rbacrolebindings describe
+        (NAME : --location=LOCATION --scope=SCOPE) [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The RoleBinding specified does not exist in the project.
+      ▪ The caller does not have permission to access the RoleBinding.
+
+EXAMPLES
+    To print metadata for RBAC RoleBinding RBRB in the scope SCOPE, run:
+
+        $ gcloud beta container fleet scopes rbacrolebindings describe \
+            RBRB --scope=SCOPE
+
+POSITIONAL ARGUMENTS
+     Rbacrolebinding resource - The group of arguments defining an
+     RBACRoleBinding. The arguments in this group can be used to specify the
+     attributes of this resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAME on the command line with a fully specified
+        name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       NAME
+          ID of the rbacrolebinding or fully qualified identifier for the
+          rbacrolebinding.
+
+          To set the rbacrolebinding attribute:
+          ▸ provide the argument NAME on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the rbacrolebinding.
+
+          To set the location attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --scope=SCOPE
+          Name of the rbacrolebinding.
+
+          To set the scope attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet scopes rbacrolebindings describe
+
+        $ gcloud alpha container fleet scopes rbacrolebindings describe
+
diff --git a/gcloud/beta/container/fleet/scopes/rbacrolebindings/help b/gcloud/beta/container/fleet/scopes/rbacrolebindings/help
new file mode 100644
index 000000000..acc29eef9
--- /dev/null
+++ b/gcloud/beta/container/fleet/scopes/rbacrolebindings/help
@@ -0,0 +1,48 @@
+NAME
+    gcloud beta container fleet scopes rbacrolebindings - fleet scope RBAC
+        RoleBindings for permissions
+
+SYNOPSIS
+    gcloud beta container fleet scopes rbacrolebindings COMMAND
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command group allows for manipulation of fleet namespace RBAC
+    RoleBindings.
+
+EXAMPLES
+    Manage RBAC RoleBindings:
+
+        $ gcloud beta container fleet scopes rbacrolebindings --help
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        (BETA) Create an RBAC RoleBinding.
+
+     delete
+        (BETA) Delete a fleet scope RBAC RoleBinding.
+
+     describe
+        (BETA) Show fleet scope RBAC RoleBinding information.
+
+     list
+        (BETA) List RBAC RoleBindings in a fleet scope.
+
+     update
+        (BETA) Update a fleet scope RBAC RoleBinding.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet scopes rbacrolebindings
+
+        $ gcloud alpha container fleet scopes rbacrolebindings
+
diff --git a/gcloud/beta/container/fleet/scopes/rbacrolebindings/list b/gcloud/beta/container/fleet/scopes/rbacrolebindings/list
new file mode 100644
index 000000000..4e105fd39
--- /dev/null
+++ b/gcloud/beta/container/fleet/scopes/rbacrolebindings/list
@@ -0,0 +1,73 @@
+NAME
+    gcloud beta container fleet scopes rbacrolebindings list - list RBAC
+        RoleBindings in a fleet scope
+
+SYNOPSIS
+    gcloud beta container fleet scopes rbacrolebindings list --scope=SCOPE
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The scope specified does not exist.
+      ▪ The user does not have access to the specified scope.
+
+EXAMPLES
+    The following command lists RBAC RoleBindings in scope SCOPE in project
+    PROJECT_ID:
+
+        $ gcloud beta container fleet scopes rbacrolebindings list \
+            --scope=SCOPE --project=PROJECT_ID
+
+REQUIRED FLAGS
+     --scope=SCOPE
+        Name of the fleet scope to list RBAC RoleBindings from.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet scopes rbacrolebindings list
+
+        $ gcloud alpha container fleet scopes rbacrolebindings list
+
diff --git a/gcloud/beta/container/fleet/scopes/rbacrolebindings/update b/gcloud/beta/container/fleet/scopes/rbacrolebindings/update
new file mode 100644
index 000000000..3d1b16948
--- /dev/null
+++ b/gcloud/beta/container/fleet/scopes/rbacrolebindings/update
@@ -0,0 +1,129 @@
+NAME
+    gcloud beta container fleet scopes rbacrolebindings update - update a fleet
+        scope RBAC RoleBinding
+
+SYNOPSIS
+    gcloud beta container fleet scopes rbacrolebindings update
+        (NAME : --location=LOCATION --scope=SCOPE) [--role=ROLE]
+        [--update-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]]
+        [--group=GROUP | --user=USER] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The RoleBinding does not exist in the project.
+      ▪ The caller does not have permission to access the RoleBinding.
+
+EXAMPLES
+    To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to
+    the viewer role:
+
+        $ gcloud beta container fleet scopes rbacrolebindings update RBRB \
+            --scope=SCOPE --role=viewer
+
+    To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to
+    the user someone@google.com:
+
+        $ gcloud beta container fleet scopes rbacrolebindings update RBRB \
+            --scope=SCOPE --user=someone@google.com
+
+POSITIONAL ARGUMENTS
+     Rbacrolebinding resource - The group of arguments defining an
+     RBACRoleBinding. The arguments in this group can be used to specify the
+     attributes of this resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAME on the command line with a fully specified
+        name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       NAME
+          ID of the rbacrolebinding or fully qualified identifier for the
+          rbacrolebinding.
+
+          To set the rbacrolebinding attribute:
+          ▸ provide the argument NAME on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the rbacrolebinding.
+
+          To set the location attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --scope=SCOPE
+          Name of the rbacrolebinding.
+
+          To set the scope attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+FLAGS
+     --role=ROLE
+        Role for the RBACRoleBinding to update to. ROLE must be one of: admin,
+        edit, view.
+
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud beta container fleet scopes rbacrolebindings update \
+                --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud beta container fleet scopes rbacrolebindings update \
+                --clear-labels --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+     At most one of these can be specified:
+
+       --group=GROUP
+          Group for the RBACRoleBinding to update to.
+
+       --user=USER
+          User for the RBACRoleBinding to update to.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet scopes rbacrolebindings update
+
+        $ gcloud alpha container fleet scopes rbacrolebindings update
+
diff --git a/gcloud/beta/container/fleet/scopes/remove-iam-policy-binding b/gcloud/beta/container/fleet/scopes/remove-iam-policy-binding
new file mode 100644
index 000000000..3e8fc978b
--- /dev/null
+++ b/gcloud/beta/container/fleet/scopes/remove-iam-policy-binding
@@ -0,0 +1,90 @@
+NAME
+    gcloud beta container fleet scopes remove-iam-policy-binding - remove IAM
+        policy binding of a Fleet Scope
+
+SYNOPSIS
+    gcloud beta container fleet scopes remove-iam-policy-binding SCOPE
+        --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Remove an IAM policy binding from the IAM policy of a scope. One
+    binding consists of a member, and a role.
+
+EXAMPLES
+    To remove an IAM policy binding for the role of 'roles/gkehub.scopeUser'
+    for the user 'test-user@gmail.com' with scope 'my-scope', run:
+
+        $ gcloud beta container fleet scopes remove-iam-policy-binding \
+            my-scope --member='user:test-user@gmail.com' \
+            --role='roles/gkehub.scopeUser'
+
+    See https://cloud.google.com/iam/docs/managing-policies for details of
+    policy role and member types.
+
+POSITIONAL ARGUMENTS
+     Scope resource - The scope for which to remove IAM policy binding from.
+     This represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     To set the location attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+REQUIRED FLAGS
+     --member=PRINCIPAL
+        The principal to remove the binding for. Should be of the form
+        user|group|serviceAccount:email or domain:domain.
+
+        Examples: user:test-user@gmail.com, group:admins@example.com,
+        serviceAccount:test123@example.domain.com, or
+        domain:example.domain.com.
+
+        Deleted principals have an additional deleted: prefix and a ?uid=UID
+        suffix, where UID is a unique identifier for the principal. Example:
+        deleted:user:test-user@gmail.com?uid=123456789012345678901.
+
+        Some resources also accept the following special values:
+        ◆ allUsers - Special identifier that represents anyone who is on the
+          internet, with or without a Google account.
+        ◆ allAuthenticatedUsers - Special identifier that represents anyone
+          who is authenticated with a Google account or a service account.
+
+     --role=ROLE
+        The role to remove the principal from.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1beta API. The full documentation for this
+    API can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet scopes remove-iam-policy-binding
+
+        $ gcloud alpha container fleet scopes remove-iam-policy-binding
+
diff --git a/gcloud/beta/container/fleet/scopes/update b/gcloud/beta/container/fleet/scopes/update
index 9bf979625..67f58e1b6 100644
--- a/gcloud/beta/container/fleet/scopes/update
+++ b/gcloud/beta/container/fleet/scopes/update
@@ -10,8 +10,9 @@ SYNOPSIS
         [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING
           --remove-upgrade-soaking-overrides
           | --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE
-          --upgrade-selector=[UPGRADE_SELECTOR,...] --reset-upstream-scope
-          | --upstream-scope=UPSTREAM_SCOPE] [GCLOUD_WIDE_FLAG ...]
+          --upgrade-selector=[name=NAME],[version=VERSION]
+          --reset-upstream-scope | --upstream-scope=UPSTREAM_SCOPE]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (BETA) Update an existing Fleet Scope.
@@ -174,7 +175,7 @@ FLAGS
               This flag argument must be specified if any of the other
               arguments in this group are specified.
 
-           --upgrade-selector=[UPGRADE_SELECTOR,...]
+           --upgrade-selector=[name=NAME],[version=VERSION]
               Name and version of the upgrade to be overridden where version is
               a full GKE version. Currently, name can be either
               k8s_control_plane or k8s_node.
@@ -218,8 +219,10 @@ API REFERENCE
     https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet scopes update
 
         $ gcloud alpha container fleet scopes update
 
diff --git a/gcloud/beta/container/fleet/update b/gcloud/beta/container/fleet/update
new file mode 100644
index 000000000..aebcbe82e
--- /dev/null
+++ b/gcloud/beta/container/fleet/update
@@ -0,0 +1,99 @@
+NAME
+    gcloud beta container fleet update - update a fleet
+
+SYNOPSIS
+    gcloud beta container fleet update [--async] [--display-name=DISPLAY_NAME]
+        [--update-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]]
+        [--security-posture=SECURITY_POSTURE
+          --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project specified already has a fleet.
+      ▪ The active account does not have permission to access the given
+        project.
+
+EXAMPLES
+    To update the display name of the fleet in project example-foo-bar-1 to
+    updated-name, run:
+
+        $ gcloud beta container fleet update --display-name=updated-name \
+            --project=example-foo-bar-1
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --display-name=DISPLAY_NAME
+        Display name of the fleet to be created (optional). 4-30 characters,
+        alphanumeric and [ '"!-] only.
+
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud beta container fleet update --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud beta container fleet update --clear-labels \
+                --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+     Default cluster configurations to apply across the fleet.
+
+       Security posture config.
+
+         --security-posture=SECURITY_POSTURE
+            To apply basic security posture to the clusters of the fleet,
+
+                $ gcloud beta container fleet update --security-posture=basic
+
+            SECURITY_POSTURE must be one of: disabled, basic, enterprise.
+
+         --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING
+            To apply basic vulnerability scanning to the clusters of the fleet,
+
+                $ gcloud beta container fleet update \
+                    --workload-vulnerability-scanning=disabled
+
+            WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, basic,
+            enterprise.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container fleet update
+
+        $ gcloud alpha container fleet update
+
diff --git a/gcloud/beta/container/hub/create b/gcloud/beta/container/hub/create
new file mode 100644
index 000000000..115b29f41
--- /dev/null
+++ b/gcloud/beta/container/hub/create
@@ -0,0 +1,77 @@
+NAME
+    gcloud beta container hub create - create a fleet
+
+SYNOPSIS
+    gcloud beta container hub create [--async] [--display-name=DISPLAY_NAME]
+        [--labels=[KEY=VALUE,...]]
+        [--security-posture=SECURITY_POSTURE
+          --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project specified already has a fleet.
+      ▪ The active account does not have permission to access the given
+        project.
+
+EXAMPLES
+    To create a fleet in project example-foo-bar-1 with display name my-fleet,
+    run:
+
+        $ gcloud beta container hub create --display-name=my-fleet \
+            --project=example-foo-bar-1
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --display-name=DISPLAY_NAME
+        Display name of the fleet to be created (optional). 4-30 characters,
+        alphanumeric and [ '"!-] only.
+
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     Default cluster configurations to apply across the fleet.
+
+       Security posture config.
+
+         --security-posture=SECURITY_POSTURE
+            To apply basic security posture to the clusters of the fleet,
+
+                $ gcloud beta container hub create --security-posture=basic
+
+            SECURITY_POSTURE must be one of: disabled, basic, enterprise.
+
+         --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING
+            To apply basic vulnerability scanning to the clusters of the fleet,
+
+                $ gcloud beta container hub create \
+                    --workload-vulnerability-scanning=disabled
+
+            WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, basic,
+            enterprise.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub create
+
+        $ gcloud alpha container hub create
+
diff --git a/gcloud/beta/container/hub/delete b/gcloud/beta/container/hub/delete
new file mode 100644
index 000000000..4ab01067b
--- /dev/null
+++ b/gcloud/beta/container/hub/delete
@@ -0,0 +1,39 @@
+NAME
+    gcloud beta container hub delete - delete a fleet
+
+SYNOPSIS
+    gcloud beta container hub delete [--async] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project specified already has a fleet.
+      ▪ The active account does not have permission to access the given
+        project.
+
+EXAMPLES
+    To delete a fleet in project example-foo-bar-1, run:
+
+        $ gcloud beta container hub delete --project=example-foo-bar-1
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub delete
+
+        $ gcloud alpha container hub delete
+
diff --git a/gcloud/beta/container/hub/describe b/gcloud/beta/container/hub/describe
new file mode 100644
index 000000000..26f8b9b51
--- /dev/null
+++ b/gcloud/beta/container/hub/describe
@@ -0,0 +1,34 @@
+NAME
+    gcloud beta container hub describe - show fleet info
+
+SYNOPSIS
+    gcloud beta container hub describe [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project specified does not have a fleet.
+      ▪ The active account does not have permission to access the given
+        project.
+
+EXAMPLES
+    To print metadata for the fleet in project example-foo-bar-1, run:
+
+        $ gcloud beta container hub describe --project=example-foo-bar-1
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub describe
+
+        $ gcloud alpha container hub describe
+
diff --git a/gcloud/beta/container/hub/help b/gcloud/beta/container/hub/help
index d15f3f15a..58d595af3 100644
--- a/gcloud/beta/container/hub/help
+++ b/gcloud/beta/container/hub/help
@@ -80,6 +80,24 @@ GROUPS
      scopes
         (BETA) Manage scopes of all your GKE fleets.
 
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        (BETA) Create a fleet.
+
+     delete
+        (BETA) Delete a fleet.
+
+     describe
+        (BETA) Show fleet info.
+
+     list
+        (BETA) List fleets visible to the user in an organization.
+
+     update
+        (BETA) Update a fleet.
+
 NOTES
     This command is currently in beta and might change without notice. These
     variants are also available:
diff --git a/gcloud/beta/container/hub/list b/gcloud/beta/container/hub/list
new file mode 100644
index 000000000..c59bfed36
--- /dev/null
+++ b/gcloud/beta/container/hub/list
@@ -0,0 +1,73 @@
+NAME
+    gcloud beta container hub list - list fleets visible to the user in an
+        organization
+
+SYNOPSIS
+    gcloud beta container hub list [--organization=ORGANIZATION_ID]
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The org or project specified does not exist.
+      ▪ The user does not have access to the project specified.
+
+EXAMPLES
+    The following command lists fleets in organization 12345:
+
+        $ gcloud beta container hub list --organization=12345
+
+COMMONLY USED FLAGS
+     --organization=ORGANIZATION_ID
+        ID (number) for the organization to list fleets from. If neither
+        --organization nor --project are provided, defaults to the organization
+        of the active project.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub list
+
+        $ gcloud alpha container hub list
+
diff --git a/gcloud/beta/container/hub/memberships/bindings/create b/gcloud/beta/container/hub/memberships/bindings/create
index ced68fa7d..c4c76654f 100644
--- a/gcloud/beta/container/hub/memberships/bindings/create
+++ b/gcloud/beta/container/hub/memberships/bindings/create
@@ -96,8 +96,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub memberships bindings create
 
         $ gcloud alpha container hub memberships bindings create
 
diff --git a/gcloud/beta/container/hub/memberships/bindings/delete b/gcloud/beta/container/hub/memberships/bindings/delete
index 55ebd020d..0b690f456 100644
--- a/gcloud/beta/container/hub/memberships/bindings/delete
+++ b/gcloud/beta/container/hub/memberships/bindings/delete
@@ -79,8 +79,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub memberships bindings delete
 
         $ gcloud alpha container hub memberships bindings delete
 
diff --git a/gcloud/beta/container/hub/memberships/bindings/describe b/gcloud/beta/container/hub/memberships/bindings/describe
index 8ef6b696f..6284305cc 100644
--- a/gcloud/beta/container/hub/memberships/bindings/describe
+++ b/gcloud/beta/container/hub/memberships/bindings/describe
@@ -79,8 +79,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub memberships bindings describe
 
         $ gcloud alpha container hub memberships bindings describe
 
diff --git a/gcloud/beta/container/hub/memberships/bindings/help b/gcloud/beta/container/hub/memberships/bindings/help
index 22493a25e..30dbff836 100644
--- a/gcloud/beta/container/hub/memberships/bindings/help
+++ b/gcloud/beta/container/hub/memberships/bindings/help
@@ -39,8 +39,10 @@ COMMANDS
         (BETA) Update the Binding in a Membership.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub memberships bindings
 
         $ gcloud alpha container hub memberships bindings
 
diff --git a/gcloud/beta/container/hub/memberships/bindings/list b/gcloud/beta/container/hub/memberships/bindings/list
index b0e5e197d..38049d0e4 100644
--- a/gcloud/beta/container/hub/memberships/bindings/list
+++ b/gcloud/beta/container/hub/memberships/bindings/list
@@ -77,8 +77,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub memberships bindings list
 
         $ gcloud alpha container hub memberships bindings list
 
diff --git a/gcloud/beta/container/hub/memberships/bindings/update b/gcloud/beta/container/hub/memberships/bindings/update
index 919b8513c..45ed3d8d0 100644
--- a/gcloud/beta/container/hub/memberships/bindings/update
+++ b/gcloud/beta/container/hub/memberships/bindings/update
@@ -120,8 +120,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub memberships bindings update
 
         $ gcloud alpha container hub memberships bindings update
 
diff --git a/gcloud/beta/container/hub/scopes/add-iam-policy-binding b/gcloud/beta/container/hub/scopes/add-iam-policy-binding
new file mode 100644
index 000000000..aa3089584
--- /dev/null
+++ b/gcloud/beta/container/hub/scopes/add-iam-policy-binding
@@ -0,0 +1,89 @@
+NAME
+    gcloud beta container hub scopes add-iam-policy-binding - add IAM policy
+        binding to a Fleet Scope
+
+SYNOPSIS
+    gcloud beta container hub scopes add-iam-policy-binding SCOPE
+        --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Add an IAM policy binding to the IAM policy of a Fleet Scope. One
+    binding consists of a member, and a role.
+
+EXAMPLES
+    To add an IAM policy binding for the role of 'roles/gkehub.scopeUser' for
+    the user 'test-user@gmail.com' with scope 'my-scope', run:
+
+        $ gcloud beta container hub scopes add-iam-policy-binding my-scope \
+            --member='user:test-user@gmail.com' \
+            --role='roles/gkehub.scopeUser'
+
+    See https://cloud.google.com/iam/docs/managing-policies for details of
+    policy role and member types.
+
+POSITIONAL ARGUMENTS
+     Scope resource - The scope for which to add IAM policy binding to. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     To set the location attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+REQUIRED FLAGS
+     --member=PRINCIPAL
+        The principal to add the binding for. Should be of the form
+        user|group|serviceAccount:email or domain:domain.
+
+        Examples: user:test-user@gmail.com, group:admins@example.com,
+        serviceAccount:test123@example.domain.com, or
+        domain:example.domain.com.
+
+        Some resources also accept the following special values:
+        ◆ allUsers - Special identifier that represents anyone who is on the
+          internet, with or without a Google account.
+        ◆ allAuthenticatedUsers - Special identifier that represents anyone
+          who is authenticated with a Google account or a service account.
+
+     --role=ROLE
+        Role name to assign to the principal. The role name is the complete
+        path of a predefined role, such as roles/logging.viewer, or the role ID
+        for a custom role, such as
+        organizations/{ORGANIZATION_ID}/roles/logging.viewer.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1beta API. The full documentation for this
+    API can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub scopes add-iam-policy-binding
+
+        $ gcloud alpha container hub scopes add-iam-policy-binding
+
diff --git a/gcloud/beta/container/hub/scopes/create b/gcloud/beta/container/hub/scopes/create
index 7ccdde03b..ca43bd9fb 100644
--- a/gcloud/beta/container/hub/scopes/create
+++ b/gcloud/beta/container/hub/scopes/create
@@ -68,8 +68,10 @@ API REFERENCE
     https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub scopes create
 
         $ gcloud alpha container hub scopes create
 
diff --git a/gcloud/beta/container/hub/scopes/delete b/gcloud/beta/container/hub/scopes/delete
index 998f6e648..3303df09d 100644
--- a/gcloud/beta/container/hub/scopes/delete
+++ b/gcloud/beta/container/hub/scopes/delete
@@ -70,8 +70,10 @@ API REFERENCE
     https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub scopes delete
 
         $ gcloud alpha container hub scopes delete
 
diff --git a/gcloud/beta/container/hub/scopes/describe b/gcloud/beta/container/hub/scopes/describe
index 38fd1ca16..1830e7355 100644
--- a/gcloud/beta/container/hub/scopes/describe
+++ b/gcloud/beta/container/hub/scopes/describe
@@ -64,8 +64,10 @@ API REFERENCE
     https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub scopes describe
 
         $ gcloud alpha container hub scopes describe
 
diff --git a/gcloud/beta/container/hub/scopes/get-iam-policy b/gcloud/beta/container/hub/scopes/get-iam-policy
new file mode 100644
index 000000000..9f3398026
--- /dev/null
+++ b/gcloud/beta/container/hub/scopes/get-iam-policy
@@ -0,0 +1,88 @@
+NAME
+    gcloud beta container hub scopes get-iam-policy - get the IAM policy for a
+        Fleet Scope
+
+SYNOPSIS
+    gcloud beta container hub scopes get-iam-policy SCOPE [--filter=EXPRESSION]
+        [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command gets the IAM policy for a scope.
+
+EXAMPLES
+    To print the IAM policy for a given scope, run:
+
+        $ gcloud beta container hub scopes get-iam-policy my-scope
+
+POSITIONAL ARGUMENTS
+     Scope resource - The scope for which to display the IAM policy. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     To set the location attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1beta API. The full documentation for this
+    API can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub scopes get-iam-policy
+
+        $ gcloud alpha container hub scopes get-iam-policy
+
diff --git a/gcloud/beta/container/hub/scopes/help b/gcloud/beta/container/hub/scopes/help
index a8f038ed2..4312533a2 100644
--- a/gcloud/beta/container/hub/scopes/help
+++ b/gcloud/beta/container/hub/scopes/help
@@ -12,9 +12,22 @@ GCLOUD WIDE FLAGS
 
     Run $ gcloud help for details.
 
+GROUPS
+    GROUP is one of the following:
+
+     namespaces
+        (BETA) Fleet namespaces are the fleet equivalent of k8s cluster
+        namespaces.
+
+     rbacrolebindings
+        (BETA) Fleet scope RBAC RoleBindings for permissions.
+
 COMMANDS
     COMMAND is one of the following:
 
+     add-iam-policy-binding
+        (BETA) Add IAM policy binding to a Fleet Scope.
+
      create
         (BETA) Create a new fleet scope.
 
@@ -24,15 +37,23 @@ COMMANDS
      describe
         (BETA) Describe a fleet scope.
 
+     get-iam-policy
+        (BETA) Get the IAM policy for a Fleet Scope.
+
      list
         (BETA) List fleet scopes.
 
+     remove-iam-policy-binding
+        (BETA) Remove IAM policy binding of a Fleet Scope.
+
      update
         (BETA) Update a scope.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub scopes
 
         $ gcloud alpha container hub scopes
 
diff --git a/gcloud/beta/container/hub/scopes/list b/gcloud/beta/container/hub/scopes/list
index e6d74c1ef..6337bc48f 100644
--- a/gcloud/beta/container/hub/scopes/list
+++ b/gcloud/beta/container/hub/scopes/list
@@ -60,8 +60,10 @@ API REFERENCE
     https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub scopes list
 
         $ gcloud alpha container hub scopes list
 
diff --git a/gcloud/beta/container/hub/scopes/namespaces/create b/gcloud/beta/container/hub/scopes/namespaces/create
new file mode 100644
index 000000000..e70f75a23
--- /dev/null
+++ b/gcloud/beta/container/hub/scopes/namespaces/create
@@ -0,0 +1,90 @@
+NAME
+    gcloud beta container hub scopes namespaces create - create a fleet
+        namespace
+
+SYNOPSIS
+    gcloud beta container hub scopes namespaces create
+        (NAMESPACE : --scope=SCOPE) [--labels=[KEY=VALUE,...]]
+        [--namespace-labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project has a fleet namespace with the same name.
+      ▪ The caller does not have permission to access the given project.
+
+EXAMPLES
+    To create a fleet namespace with name NAMESPACE in the active project, run:
+
+        $ gcloud beta container hub scopes namespaces create NAMESPACE
+
+    To create a fleet namespace in fleet scope SCOPE in project PROJECT_ID with
+    name NAMESPACE, run:
+
+        $ gcloud beta container hub scopes namespaces create NAMESPACE \
+            --scope=SCOPE --project=PROJECT_ID
+
+POSITIONAL ARGUMENTS
+     Namespace resource - The group of arguments defining the Fleet Namespace.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       NAMESPACE
+          ID of the namespace or fully qualified identifier for the namespace.
+
+          To set the namespace attribute:
+          ▸ provide the argument NAMESPACE on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --scope=SCOPE
+          the
+
+          To set the scope attribute:
+          ▸ provide the argument NAMESPACE on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+FLAGS
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     --namespace-labels=[KEY=VALUE,...]
+        List of namespace-level label KEY=VALUE pairs to add.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub scopes namespaces create
+
+        $ gcloud alpha container hub scopes namespaces create
+
diff --git a/gcloud/beta/container/hub/scopes/namespaces/delete b/gcloud/beta/container/hub/scopes/namespaces/delete
new file mode 100644
index 000000000..dc603ca9d
--- /dev/null
+++ b/gcloud/beta/container/hub/scopes/namespaces/delete
@@ -0,0 +1,77 @@
+NAME
+    gcloud beta container hub scopes namespaces delete - delete a fleet
+        namespace
+
+SYNOPSIS
+    gcloud beta container hub scopes namespaces delete
+        (NAMESPACE : --scope=SCOPE) [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The namespace specified does not exist.
+      ▪ The caller does not have permission to access the given project or
+        namespace.
+
+EXAMPLES
+    To delete fleet namespace NAMESPACE in the active project:
+
+        $ gcloud beta container hub scopes namespaces delete NAMESPACE
+
+    To delete fleet namespace NAMESPACE in project PROJECT_ID:
+
+        $ gcloud beta container hub scopes namespaces delete NAMESPACE \
+            --project=PROJECT_ID
+
+POSITIONAL ARGUMENTS
+     Namespace resource - The group of arguments defining the Fleet Namespace.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       NAMESPACE
+          ID of the namespace or fully qualified identifier for the namespace.
+
+          To set the namespace attribute:
+          ▸ provide the argument NAMESPACE on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --scope=SCOPE
+          the
+
+          To set the scope attribute:
+          ▸ provide the argument NAMESPACE on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub scopes namespaces delete
+
+        $ gcloud alpha container hub scopes namespaces delete
+
diff --git a/gcloud/beta/container/hub/scopes/namespaces/describe b/gcloud/beta/container/hub/scopes/namespaces/describe
new file mode 100644
index 000000000..0439564f5
--- /dev/null
+++ b/gcloud/beta/container/hub/scopes/namespaces/describe
@@ -0,0 +1,77 @@
+NAME
+    gcloud beta container hub scopes namespaces describe - show fleet namespace
+        info
+
+SYNOPSIS
+    gcloud beta container hub scopes namespaces describe
+        (NAMESPACE : --scope=SCOPE) [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The namespace specified does not exist in the project.
+      ▪ The caller does not have permission to access the project or
+        namespace.
+
+EXAMPLES
+    To print metadata for the namespace NAMESPACE in the active project, run:
+
+        $ gcloud beta container hub scopes namespaces describe NAMESPACE
+
+    To print metadata for the namespace NAMESPACE in project PROJECT_ID, run:
+
+        $ gcloud beta container hub scopes namespaces describe NAMESPACE \
+            --project=PROJECT_ID
+
+POSITIONAL ARGUMENTS
+     Namespace resource - The group of arguments defining the Fleet Namespace.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       NAMESPACE
+          ID of the namespace or fully qualified identifier for the namespace.
+
+          To set the namespace attribute:
+          ▸ provide the argument NAMESPACE on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --scope=SCOPE
+          the
+
+          To set the scope attribute:
+          ▸ provide the argument NAMESPACE on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub scopes namespaces describe
+
+        $ gcloud alpha container hub scopes namespaces describe
+
diff --git a/gcloud/beta/container/hub/scopes/namespaces/get-credentials b/gcloud/beta/container/hub/scopes/namespaces/get-credentials
new file mode 100644
index 000000000..e0d50fba0
--- /dev/null
+++ b/gcloud/beta/container/hub/scopes/namespaces/get-credentials
@@ -0,0 +1,60 @@
+NAME
+    gcloud beta container hub scopes namespaces get-credentials - fetch
+        credentials for a membership with a particular namespace
+
+SYNOPSIS
+    gcloud beta container hub scopes namespaces get-credentials NAMESPACE
+        [--membership=MEMBERSHIP] [--membership-location=MEMBERSHIP_LOCATION]
+        [--set-namespace-in-config=SET_NAMESPACE_IN_CONFIG]
+        [GCLOUD_WIDE_FLAG ...]
+
+EXAMPLES
+    Get the Connect Gateway kubeconfig for global membership MEMBERSHIP, using
+    namespace NAMESPACE in the config:
+
+        $ gcloud beta container hub scopes namespaces get-credentials \
+            NAMESPACE --membership=MEMBERSHIP --membership-location=global \
+            --set-namespace-in-config=true
+
+    Get the Connect Gateway kubeconfig for global membership MEMBERSHIP:
+
+        $ gcloud beta container hub scopes namespaces get-credentials \
+            NAMESPACE --membership=MEMBERSHIP --membership-location=global
+
+POSITIONAL ARGUMENTS
+     NAMESPACE
+        Name of the namespace for which to get access to memberships.
+
+FLAGS
+     --membership=MEMBERSHIP
+        Membership ID to get credentials from. If not provided, a prompt will
+        offer a list of memberships in the fleet.
+
+     --membership-location=MEMBERSHIP_LOCATION
+        The location of the membership resource, e.g. us-central1. If not
+        specified, defaults to global.
+
+     --set-namespace-in-config=SET_NAMESPACE_IN_CONFIG
+        If true, the default namespace for the context in the generated
+        kubeconfig will be set to the Fleet namespace (i.e. the name given as
+        the positional argument in this command).
+
+        Otherwise, no default namespace will be set, functioning the same as
+        gcloud container fleet memberships get-credentials.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub scopes namespaces get-credentials
+
+        $ gcloud alpha container hub scopes namespaces get-credentials
+
diff --git a/gcloud/beta/container/hub/scopes/namespaces/help b/gcloud/beta/container/hub/scopes/namespaces/help
new file mode 100644
index 000000000..00f16fc11
--- /dev/null
+++ b/gcloud/beta/container/hub/scopes/namespaces/help
@@ -0,0 +1,53 @@
+NAME
+    gcloud beta container hub scopes namespaces - fleet namespaces are the
+        fleet equivalent of k8s cluster namespaces
+
+SYNOPSIS
+    gcloud beta container hub scopes namespaces COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command group allows for manipulation of fleet namespaces.
+
+EXAMPLES
+    Manage fleet namespaces:
+
+        $ gcloud beta container hub scopes namespaces --help
+
+    Manage RBAC RoleBindings in a fleet namespace:
+
+        $ gcloud beta container hub scopes namespaces rbacrolebindings --help
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        (BETA) Create a fleet namespace.
+
+     delete
+        (BETA) Delete a fleet namespace.
+
+     describe
+        (BETA) Show fleet namespace info.
+
+     get-credentials
+        (BETA) Fetch credentials for a membership with a particular namespace.
+
+     list
+        (BETA) List fleet namespaces in a project.
+
+     update
+        (BETA) Update a fleet namespace.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub scopes namespaces
+
+        $ gcloud alpha container hub scopes namespaces
+
diff --git a/gcloud/beta/container/hub/scopes/namespaces/list b/gcloud/beta/container/hub/scopes/namespaces/list
new file mode 100644
index 000000000..3b87f9ae9
--- /dev/null
+++ b/gcloud/beta/container/hub/scopes/namespaces/list
@@ -0,0 +1,96 @@
+NAME
+    gcloud beta container hub scopes namespaces list - list fleet namespaces in
+        a project
+
+SYNOPSIS
+    gcloud beta container hub scopes namespaces list --scope=SCOPE
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The user does not have access to the project specified.
+
+EXAMPLES
+    The following command lists namespaces in the active project:
+
+        $ gcloud beta container hub scopes namespaces list
+
+    The following command lists namespaces in project PROJECT_ID:
+
+        $ gcloud beta container hub scopes namespaces list \
+            --project=PROJECT_ID
+
+REQUIRED FLAGS
+     Scope resource - The group of arguments defining the Fleet Scope. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --scope on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --scope on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       --scope=SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument --scope on the command line.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub scopes namespaces list
+
+        $ gcloud alpha container hub scopes namespaces list
+
diff --git a/gcloud/beta/container/hub/scopes/namespaces/update b/gcloud/beta/container/hub/scopes/namespaces/update
new file mode 100644
index 000000000..253e66b01
--- /dev/null
+++ b/gcloud/beta/container/hub/scopes/namespaces/update
@@ -0,0 +1,141 @@
+NAME
+    gcloud beta container hub scopes namespaces update - update a fleet
+        namespace
+
+SYNOPSIS
+    gcloud beta container hub scopes namespaces update
+        (NAMESPACE : --scope=SCOPE) [--update-labels=[KEY=VALUE,...]]
+        [--update-namespace-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]]
+        [--clear-namespace-labels | --remove-namespace-labels=[KEY,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The fleet namespace does not exist in the project.
+      ▪ The caller does not have permission to access the project or
+        namespace.
+
+EXAMPLES
+    To update the namespace NAMESPACE in the active project:
+
+        $ gcloud beta container hub scopes namespaces update NAMESPACE
+
+    To update the namespace NAMESPACE in project PROJECT_ID:
+
+        $ gcloud beta container hub scopes namespaces update NAMESPACE \
+            --project=PROJECT_ID
+
+POSITIONAL ARGUMENTS
+     Namespace resource - The group of arguments defining the Fleet Namespace.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       NAMESPACE
+          ID of the namespace or fully qualified identifier for the namespace.
+
+          To set the namespace attribute:
+          ▸ provide the argument NAMESPACE on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --scope=SCOPE
+          the
+
+          To set the scope attribute:
+          ▸ provide the argument NAMESPACE on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+FLAGS
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     --update-namespace-labels=[KEY=VALUE,...]
+        List of namespace-level label KEY=VALUE pairs to update in the cluster
+        namespace. If a label exists, its value is modified. Otherwise, a new
+        label is' created.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud beta container hub scopes namespaces update --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud beta container hub scopes namespaces update \
+                --clear-labels --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+     At most one of these can be specified:
+
+       --clear-namespace-labels
+          Remove all namespace-level labels from the cluster namespace. If
+          --update-namespace-labels is also specified then
+          --clear-namespace-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud beta container hub scopes namespaces update \
+                namespace_name --clear-namespace-labels
+
+          To remove all existing namespace-level labels and create two new
+          labels, foo and baz:
+
+              $ gcloud beta container hub scopes namespaces update \
+                namespace_name --clear-namespace-labels \
+                --update-namespace-labels foo=bar,baz=qux
+
+       --remove-namespace-labels=[KEY,...]
+          List of namespace-level label keys to remove in the cluster
+          namespace. If a label does not exist it is silently ignored. If
+          --update-namespace-labels is also specified then
+          --update-namespace-labels is applied first.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub scopes namespaces update
+
+        $ gcloud alpha container hub scopes namespaces update
+
diff --git a/gcloud/beta/container/hub/scopes/rbacrolebindings/create b/gcloud/beta/container/hub/scopes/rbacrolebindings/create
new file mode 100644
index 000000000..855b93dde
--- /dev/null
+++ b/gcloud/beta/container/hub/scopes/rbacrolebindings/create
@@ -0,0 +1,106 @@
+NAME
+    gcloud beta container hub scopes rbacrolebindings create - create an RBAC
+        RoleBinding
+
+SYNOPSIS
+    gcloud beta container hub scopes rbacrolebindings create
+        (NAME : --location=LOCATION --scope=SCOPE) --role=ROLE
+        (--group=GROUP | --user=USER) [--labels=[KEY=VALUE,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The RBAC RoleBinding already exists.
+      ▪ The caller does not have permission to access the given scope.
+
+EXAMPLES
+    To create an admin RBAC RoleBinding RBRB in scope SCOPE for user
+    person@google.com, run:
+
+        $ gcloud beta container hub scopes rbacrolebindings create RBRB \
+            --scope=SCOPE --role=admin --user=person@google.com
+
+    To create a viewer RBAC RoleBinding RBRB in scope SCOPE for group
+    people@google.com, run:
+
+        $ gcloud beta container hub scopes rbacrolebindings create RBRB \
+            --scope=SCOPE --role=viewer --group=people@google.com
+
+POSITIONAL ARGUMENTS
+     Rbacrolebinding resource - The group of arguments defining an
+     RBACRoleBinding. The arguments in this group can be used to specify the
+     attributes of this resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAME on the command line with a fully specified
+        name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       NAME
+          ID of the rbacrolebinding or fully qualified identifier for the
+          rbacrolebinding.
+
+          To set the rbacrolebinding attribute:
+          ▸ provide the argument NAME on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the rbacrolebinding.
+
+          To set the location attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --scope=SCOPE
+          Name of the rbacrolebinding.
+
+          To set the scope attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+REQUIRED FLAGS
+     --role=ROLE
+        Role to assign. ROLE must be one of: admin, edit, view.
+
+     Exactly one of these must be specified:
+
+       --group=GROUP
+          Group for the RoleBinding.
+
+       --user=USER
+          User for the RoleBinding.
+
+OPTIONAL FLAGS
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub scopes rbacrolebindings create
+
+        $ gcloud alpha container hub scopes rbacrolebindings create
+
diff --git a/gcloud/beta/container/hub/scopes/rbacrolebindings/delete b/gcloud/beta/container/hub/scopes/rbacrolebindings/delete
new file mode 100644
index 000000000..5f9f45f77
--- /dev/null
+++ b/gcloud/beta/container/hub/scopes/rbacrolebindings/delete
@@ -0,0 +1,76 @@
+NAME
+    gcloud beta container hub scopes rbacrolebindings delete - delete a fleet
+        scope RBAC RoleBinding
+
+SYNOPSIS
+    gcloud beta container hub scopes rbacrolebindings delete
+        (NAME : --location=LOCATION --scope=SCOPE) [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The RoleBinding specified does not exist.
+      ▪ The caller does not have permission to access the given RoleBinding.
+
+EXAMPLES
+    To delete RBAC RoleBinding RBRB in scope SCOPE in the active project:
+
+        $ gcloud beta container hub scopes rbacrolebindings delete RBRB \
+            --scope=SCOPE
+
+POSITIONAL ARGUMENTS
+     Rbacrolebinding resource - The group of arguments defining an
+     RBACRoleBinding. The arguments in this group can be used to specify the
+     attributes of this resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAME on the command line with a fully specified
+        name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       NAME
+          ID of the rbacrolebinding or fully qualified identifier for the
+          rbacrolebinding.
+
+          To set the rbacrolebinding attribute:
+          ▸ provide the argument NAME on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the rbacrolebinding.
+
+          To set the location attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --scope=SCOPE
+          Name of the rbacrolebinding.
+
+          To set the scope attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub scopes rbacrolebindings delete
+
+        $ gcloud alpha container hub scopes rbacrolebindings delete
+
diff --git a/gcloud/beta/container/hub/scopes/rbacrolebindings/describe b/gcloud/beta/container/hub/scopes/rbacrolebindings/describe
new file mode 100644
index 000000000..c61221c2f
--- /dev/null
+++ b/gcloud/beta/container/hub/scopes/rbacrolebindings/describe
@@ -0,0 +1,76 @@
+NAME
+    gcloud beta container hub scopes rbacrolebindings describe - show fleet
+        scope RBAC RoleBinding information
+
+SYNOPSIS
+    gcloud beta container hub scopes rbacrolebindings describe
+        (NAME : --location=LOCATION --scope=SCOPE) [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The RoleBinding specified does not exist in the project.
+      ▪ The caller does not have permission to access the RoleBinding.
+
+EXAMPLES
+    To print metadata for RBAC RoleBinding RBRB in the scope SCOPE, run:
+
+        $ gcloud beta container hub scopes rbacrolebindings describe RBRB \
+            --scope=SCOPE
+
+POSITIONAL ARGUMENTS
+     Rbacrolebinding resource - The group of arguments defining an
+     RBACRoleBinding. The arguments in this group can be used to specify the
+     attributes of this resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAME on the command line with a fully specified
+        name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       NAME
+          ID of the rbacrolebinding or fully qualified identifier for the
+          rbacrolebinding.
+
+          To set the rbacrolebinding attribute:
+          ▸ provide the argument NAME on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the rbacrolebinding.
+
+          To set the location attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --scope=SCOPE
+          Name of the rbacrolebinding.
+
+          To set the scope attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub scopes rbacrolebindings describe
+
+        $ gcloud alpha container hub scopes rbacrolebindings describe
+
diff --git a/gcloud/beta/container/hub/scopes/rbacrolebindings/help b/gcloud/beta/container/hub/scopes/rbacrolebindings/help
new file mode 100644
index 000000000..ebb39c2ec
--- /dev/null
+++ b/gcloud/beta/container/hub/scopes/rbacrolebindings/help
@@ -0,0 +1,48 @@
+NAME
+    gcloud beta container hub scopes rbacrolebindings - fleet scope RBAC
+        RoleBindings for permissions
+
+SYNOPSIS
+    gcloud beta container hub scopes rbacrolebindings COMMAND
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command group allows for manipulation of fleet namespace RBAC
+    RoleBindings.
+
+EXAMPLES
+    Manage RBAC RoleBindings:
+
+        $ gcloud beta container hub scopes rbacrolebindings --help
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        (BETA) Create an RBAC RoleBinding.
+
+     delete
+        (BETA) Delete a fleet scope RBAC RoleBinding.
+
+     describe
+        (BETA) Show fleet scope RBAC RoleBinding information.
+
+     list
+        (BETA) List RBAC RoleBindings in a fleet scope.
+
+     update
+        (BETA) Update a fleet scope RBAC RoleBinding.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub scopes rbacrolebindings
+
+        $ gcloud alpha container hub scopes rbacrolebindings
+
diff --git a/gcloud/beta/container/hub/scopes/rbacrolebindings/list b/gcloud/beta/container/hub/scopes/rbacrolebindings/list
new file mode 100644
index 000000000..523706486
--- /dev/null
+++ b/gcloud/beta/container/hub/scopes/rbacrolebindings/list
@@ -0,0 +1,73 @@
+NAME
+    gcloud beta container hub scopes rbacrolebindings list - list RBAC
+        RoleBindings in a fleet scope
+
+SYNOPSIS
+    gcloud beta container hub scopes rbacrolebindings list --scope=SCOPE
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The scope specified does not exist.
+      ▪ The user does not have access to the specified scope.
+
+EXAMPLES
+    The following command lists RBAC RoleBindings in scope SCOPE in project
+    PROJECT_ID:
+
+        $ gcloud beta container hub scopes rbacrolebindings list \
+            --scope=SCOPE --project=PROJECT_ID
+
+REQUIRED FLAGS
+     --scope=SCOPE
+        Name of the fleet scope to list RBAC RoleBindings from.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub scopes rbacrolebindings list
+
+        $ gcloud alpha container hub scopes rbacrolebindings list
+
diff --git a/gcloud/beta/container/hub/scopes/rbacrolebindings/update b/gcloud/beta/container/hub/scopes/rbacrolebindings/update
new file mode 100644
index 000000000..6529cc5b3
--- /dev/null
+++ b/gcloud/beta/container/hub/scopes/rbacrolebindings/update
@@ -0,0 +1,129 @@
+NAME
+    gcloud beta container hub scopes rbacrolebindings update - update a fleet
+        scope RBAC RoleBinding
+
+SYNOPSIS
+    gcloud beta container hub scopes rbacrolebindings update
+        (NAME : --location=LOCATION --scope=SCOPE) [--role=ROLE]
+        [--update-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]]
+        [--group=GROUP | --user=USER] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The RoleBinding does not exist in the project.
+      ▪ The caller does not have permission to access the RoleBinding.
+
+EXAMPLES
+    To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to
+    the viewer role:
+
+        $ gcloud beta container hub scopes rbacrolebindings update RBRB \
+            --scope=SCOPE --role=viewer
+
+    To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to
+    the user someone@google.com:
+
+        $ gcloud beta container hub scopes rbacrolebindings update RBRB \
+            --scope=SCOPE --user=someone@google.com
+
+POSITIONAL ARGUMENTS
+     Rbacrolebinding resource - The group of arguments defining an
+     RBACRoleBinding. The arguments in this group can be used to specify the
+     attributes of this resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAME on the command line with a fully specified
+        name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       NAME
+          ID of the rbacrolebinding or fully qualified identifier for the
+          rbacrolebinding.
+
+          To set the rbacrolebinding attribute:
+          ▸ provide the argument NAME on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the rbacrolebinding.
+
+          To set the location attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --scope=SCOPE
+          Name of the rbacrolebinding.
+
+          To set the scope attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+FLAGS
+     --role=ROLE
+        Role for the RBACRoleBinding to update to. ROLE must be one of: admin,
+        edit, view.
+
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud beta container hub scopes rbacrolebindings update \
+                --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud beta container hub scopes rbacrolebindings update \
+                --clear-labels --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+     At most one of these can be specified:
+
+       --group=GROUP
+          Group for the RBACRoleBinding to update to.
+
+       --user=USER
+          User for the RBACRoleBinding to update to.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub scopes rbacrolebindings update
+
+        $ gcloud alpha container hub scopes rbacrolebindings update
+
diff --git a/gcloud/beta/container/hub/scopes/remove-iam-policy-binding b/gcloud/beta/container/hub/scopes/remove-iam-policy-binding
new file mode 100644
index 000000000..f11655011
--- /dev/null
+++ b/gcloud/beta/container/hub/scopes/remove-iam-policy-binding
@@ -0,0 +1,90 @@
+NAME
+    gcloud beta container hub scopes remove-iam-policy-binding - remove IAM
+        policy binding of a Fleet Scope
+
+SYNOPSIS
+    gcloud beta container hub scopes remove-iam-policy-binding SCOPE
+        --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Remove an IAM policy binding from the IAM policy of a scope. One
+    binding consists of a member, and a role.
+
+EXAMPLES
+    To remove an IAM policy binding for the role of 'roles/gkehub.scopeUser'
+    for the user 'test-user@gmail.com' with scope 'my-scope', run:
+
+        $ gcloud beta container hub scopes remove-iam-policy-binding \
+            my-scope --member='user:test-user@gmail.com' \
+            --role='roles/gkehub.scopeUser'
+
+    See https://cloud.google.com/iam/docs/managing-policies for details of
+    policy role and member types.
+
+POSITIONAL ARGUMENTS
+     Scope resource - The scope for which to remove IAM policy binding from.
+     This represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     To set the location attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+REQUIRED FLAGS
+     --member=PRINCIPAL
+        The principal to remove the binding for. Should be of the form
+        user|group|serviceAccount:email or domain:domain.
+
+        Examples: user:test-user@gmail.com, group:admins@example.com,
+        serviceAccount:test123@example.domain.com, or
+        domain:example.domain.com.
+
+        Deleted principals have an additional deleted: prefix and a ?uid=UID
+        suffix, where UID is a unique identifier for the principal. Example:
+        deleted:user:test-user@gmail.com?uid=123456789012345678901.
+
+        Some resources also accept the following special values:
+        ◆ allUsers - Special identifier that represents anyone who is on the
+          internet, with or without a Google account.
+        ◆ allAuthenticatedUsers - Special identifier that represents anyone
+          who is authenticated with a Google account or a service account.
+
+     --role=ROLE
+        The role to remove the principal from.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1beta API. The full documentation for this
+    API can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub scopes remove-iam-policy-binding
+
+        $ gcloud alpha container hub scopes remove-iam-policy-binding
+
diff --git a/gcloud/beta/container/hub/scopes/update b/gcloud/beta/container/hub/scopes/update
index 80d32ce12..9f7f65fa7 100644
--- a/gcloud/beta/container/hub/scopes/update
+++ b/gcloud/beta/container/hub/scopes/update
@@ -10,8 +10,9 @@ SYNOPSIS
         [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING
           --remove-upgrade-soaking-overrides
           | --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE
-          --upgrade-selector=[UPGRADE_SELECTOR,...] --reset-upstream-scope
-          | --upstream-scope=UPSTREAM_SCOPE] [GCLOUD_WIDE_FLAG ...]
+          --upgrade-selector=[name=NAME],[version=VERSION]
+          --reset-upstream-scope | --upstream-scope=UPSTREAM_SCOPE]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (BETA) Update an existing Fleet Scope.
@@ -174,7 +175,7 @@ FLAGS
               This flag argument must be specified if any of the other
               arguments in this group are specified.
 
-           --upgrade-selector=[UPGRADE_SELECTOR,...]
+           --upgrade-selector=[name=NAME],[version=VERSION]
               Name and version of the upgrade to be overridden where version is
               a full GKE version. Currently, name can be either
               k8s_control_plane or k8s_node.
@@ -218,8 +219,10 @@ API REFERENCE
     https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub scopes update
 
         $ gcloud alpha container hub scopes update
 
diff --git a/gcloud/beta/container/hub/update b/gcloud/beta/container/hub/update
new file mode 100644
index 000000000..c9e09fa64
--- /dev/null
+++ b/gcloud/beta/container/hub/update
@@ -0,0 +1,99 @@
+NAME
+    gcloud beta container hub update - update a fleet
+
+SYNOPSIS
+    gcloud beta container hub update [--async] [--display-name=DISPLAY_NAME]
+        [--update-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]]
+        [--security-posture=SECURITY_POSTURE
+          --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project specified already has a fleet.
+      ▪ The active account does not have permission to access the given
+        project.
+
+EXAMPLES
+    To update the display name of the fleet in project example-foo-bar-1 to
+    updated-name, run:
+
+        $ gcloud beta container hub update --display-name=updated-name \
+            --project=example-foo-bar-1
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --display-name=DISPLAY_NAME
+        Display name of the fleet to be created (optional). 4-30 characters,
+        alphanumeric and [ '"!-] only.
+
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud beta container hub update --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud beta container hub update --clear-labels \
+                --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+     Default cluster configurations to apply across the fleet.
+
+       Security posture config.
+
+         --security-posture=SECURITY_POSTURE
+            To apply basic security posture to the clusters of the fleet,
+
+                $ gcloud beta container hub update --security-posture=basic
+
+            SECURITY_POSTURE must be one of: disabled, basic, enterprise.
+
+         --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING
+            To apply basic vulnerability scanning to the clusters of the fleet,
+
+                $ gcloud beta container hub update \
+                    --workload-vulnerability-scanning=disabled
+
+            WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, basic,
+            enterprise.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud container hub update
+
+        $ gcloud alpha container hub update
+
diff --git a/gcloud/beta/dataproc/clusters/create b/gcloud/beta/dataproc/clusters/create
index 0f73dd5fe..22af356d6 100644
--- a/gcloud/beta/dataproc/clusters/create
+++ b/gcloud/beta/dataproc/clusters/create
@@ -56,7 +56,8 @@ SYNOPSIS
         [--image=IMAGE | --image-version=VERSION]
         [--kerberos-config-file=KERBEROS_CONFIG_FILE | --enable-kerberos
           --kerberos-root-principal-password-uri=KERBEROS_ROOT_PRINCIPAL_PASSWORD_URI [--kerberos-kms-key=KERBEROS_KMS_KEY : --kerberos-kms-key-keyring=KERBEROS_KMS_KEY_KEYRING --kerberos-kms-key-location=KERBEROS_KMS_KEY_LOCATION --kerberos-kms-key-project=KERBEROS_KMS_KEY_PROJECT]]
-        [--single-node | --num-secondary-workers=NUM_SECONDARY_WORKERS
+        [--single-node | --min-num-workers=MIN_NUM_WORKERS
+          --num-secondary-workers=NUM_SECONDARY_WORKERS
           --num-workers=NUM_WORKERS
           --secondary-worker-type=TYPE; default="preemptible"]
         [GCLOUD_WIDE_FLAG ...]
@@ -755,6 +756,10 @@ FLAGS
 
        Multi-node cluster flags
 
+         --min-num-workers=MIN_NUM_WORKERS
+            The minimum number of workers nodes to provision for cluster create
+            operations to succeed.
+
          --num-secondary-workers=NUM_SECONDARY_WORKERS
             The number of secondary worker nodes in the cluster.
 
diff --git a/gcloud/beta/dataproc/help b/gcloud/beta/dataproc/help
index 9245fa33a..da6c01208 100644
--- a/gcloud/beta/dataproc/help
+++ b/gcloud/beta/dataproc/help
@@ -52,6 +52,12 @@ GROUPS
      operations
         (BETA) View and manage Dataproc operations.
 
+     session-templates
+        (BETA) Create and manage Dataproc session templates.
+
+     sessions
+        (BETA) Create and manage Dataproc sessions.
+
      workflow-templates
         (BETA) Create and manage Dataproc workflow templates.
 
diff --git a/gcloud/beta/dataproc/session-templates/delete b/gcloud/beta/dataproc/session-templates/delete
new file mode 100644
index 000000000..85e279cbe
--- /dev/null
+++ b/gcloud/beta/dataproc/session-templates/delete
@@ -0,0 +1,62 @@
+NAME
+    gcloud beta dataproc session-templates delete - delete a session template
+
+SYNOPSIS
+    gcloud beta dataproc session-templates delete
+        (SESSION_TEMPLATE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...]
+
+EXAMPLES
+    The following command deletes the session template
+    example-session-template:
+
+        $ gcloud beta dataproc session-templates delete \
+            example-session-template
+
+POSITIONAL ARGUMENTS
+     Session template resource - The session template to delete. The arguments
+     in this group can be used to specify the attributes of this resource.
+     (NOTE) Some attributes are not given arguments in this group but can be
+     set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument session_template on the command line with a
+        fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       SESSION_TEMPLATE
+          ID of the session template or fully qualified identifier for the
+          session template.
+
+          To set the session_template attribute:
+          ▸ provide the argument session_template on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Dataproc location for the session template. Each Dataproc location
+          constitutes an independent resource namespace constrained to
+          deploying instances into Compute Engine zones inside the location.
+          Overrides the default dataproc/location property value for this
+          command invocation.
+
+          To set the location attribute:
+          ▸ provide the argument session_template on the command line with a
+            fully specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property dataproc/location.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice.
+
diff --git a/gcloud/beta/dataproc/session-templates/describe b/gcloud/beta/dataproc/session-templates/describe
new file mode 100644
index 000000000..075252676
--- /dev/null
+++ b/gcloud/beta/dataproc/session-templates/describe
@@ -0,0 +1,63 @@
+NAME
+    gcloud beta dataproc session-templates describe - describe a session
+        template
+
+SYNOPSIS
+    gcloud beta dataproc session-templates describe
+        (SESSION_TEMPLATE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...]
+
+EXAMPLES
+    The following command prints out the session template
+    example-session-template:
+
+        $ gcloud beta dataproc session-templates describe \
+            example-session-template
+
+POSITIONAL ARGUMENTS
+     Session template resource - The session template to describe. The
+     arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument session_template on the command line with a
+        fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       SESSION_TEMPLATE
+          ID of the session template or fully qualified identifier for the
+          session template.
+
+          To set the session_template attribute:
+          ▸ provide the argument session_template on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Dataproc location for the session template. Each Dataproc location
+          constitutes an independent resource namespace constrained to
+          deploying instances into Compute Engine zones inside the location.
+          Overrides the default dataproc/location property value for this
+          command invocation.
+
+          To set the location attribute:
+          ▸ provide the argument session_template on the command line with a
+            fully specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property dataproc/location.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice.
+
diff --git a/gcloud/beta/dataproc/session-templates/export b/gcloud/beta/dataproc/session-templates/export
new file mode 100644
index 000000000..34a96f37f
--- /dev/null
+++ b/gcloud/beta/dataproc/session-templates/export
@@ -0,0 +1,74 @@
+NAME
+    gcloud beta dataproc session-templates export - export a session template
+
+SYNOPSIS
+    gcloud beta dataproc session-templates export
+        (SESSION_TEMPLATE : --location=LOCATION) [--destination=DESTINATION]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Exporting a session template is similar to describing one, except
+    that export omits output only fields, such as the template id and resource
+    name. This is to allow piping the output of export directly into import,
+    which requires that output only fields are omitted.
+
+EXAMPLES
+    The following command saves the contents of session template
+    example-session-template to a file so that it can be imported later:
+
+        $ gcloud beta dataproc session-templates export \
+            example-session-template --destination=saved-template.yaml
+
+POSITIONAL ARGUMENTS
+     Session template resource - The session template to export. The arguments
+     in this group can be used to specify the attributes of this resource.
+     (NOTE) Some attributes are not given arguments in this group but can be
+     set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument session_template on the command line with a
+        fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       SESSION_TEMPLATE
+          ID of the session template or fully qualified identifier for the
+          session template.
+
+          To set the session_template attribute:
+          ▸ provide the argument session_template on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Dataproc location for the session template. Each Dataproc location
+          constitutes an independent resource namespace constrained to
+          deploying instances into Compute Engine zones inside the location.
+          Overrides the default dataproc/location property value for this
+          command invocation.
+
+          To set the location attribute:
+          ▸ provide the argument session_template on the command line with a
+            fully specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property dataproc/location.
+
+FLAGS
+     --destination=DESTINATION
+        Path to a YAML file where the configuration will be exported.
+        Alternatively, you may omit this flag to write to standard output.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice.
+
diff --git a/gcloud/beta/dataproc/session-templates/help b/gcloud/beta/dataproc/session-templates/help
new file mode 100644
index 000000000..34df58a38
--- /dev/null
+++ b/gcloud/beta/dataproc/session-templates/help
@@ -0,0 +1,59 @@
+NAME
+    gcloud beta dataproc session-templates - create and manage Dataproc session
+        templates
+
+SYNOPSIS
+    gcloud beta dataproc session-templates COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Create and manage Dataproc session templates.
+
+EXAMPLES
+    To see the list of all session templates, run:
+
+        $ gcloud beta dataproc session-templates list
+
+    To view the details of a session template, run:
+
+        $ gcloud beta dataproc session-templates describe my-template
+
+    To view just the non-output only fields of a session template, run:
+
+        $ gcloud beta dataproc session-templates export my-template \
+            --destination template-file.yaml
+
+    To create or update a session template, run:
+
+        $ gcloud beta dataproc session-templates import my-template \
+            --source template-file.yaml
+
+    To delete a session template, run:
+
+        $ gcloud beta dataproc session-templates delete my-template
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     delete
+        (BETA) Delete a session template.
+
+     describe
+        (BETA) Describe a session template.
+
+     export
+        (BETA) Export a session template.
+
+     import
+        (BETA) Import a session template.
+
+     list
+        (BETA) List session templates.
+
+NOTES
+    This command is currently in beta and might change without notice.
+
diff --git a/gcloud/beta/dataproc/session-templates/import b/gcloud/beta/dataproc/session-templates/import
new file mode 100644
index 000000000..1e0703b22
--- /dev/null
+++ b/gcloud/beta/dataproc/session-templates/import
@@ -0,0 +1,78 @@
+NAME
+    gcloud beta dataproc session-templates import - import a session template
+
+SYNOPSIS
+    gcloud beta dataproc session-templates import
+        (SESSION_TEMPLATE : --location=LOCATION) [--source=SOURCE]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) If the specified session template already exists, it will be
+    overwritten. Otherwise, a new session template will be created. To edit an
+    existing session template, you can export the session template to a file,
+    edit its configuration, and then import the new configuration.
+
+    This command does not allow output only fields, such as template id and
+    resource name. It populates the id field based on the resource name
+    specified as the first command line argument.
+
+EXAMPLES
+    The following command creates or updates the contents of session template
+    example-session-template based on a yaml file:
+
+        $ gcloud beta dataproc session-templates import \
+            example-session-template --source=saved-template.yaml
+
+POSITIONAL ARGUMENTS
+     Session template resource - The session template to import. The arguments
+     in this group can be used to specify the attributes of this resource.
+     (NOTE) Some attributes are not given arguments in this group but can be
+     set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument session_template on the command line with a
+        fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       SESSION_TEMPLATE
+          ID of the session template or fully qualified identifier for the
+          session template.
+
+          To set the session_template attribute:
+          ▸ provide the argument session_template on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Dataproc location for the session template. Each Dataproc location
+          constitutes an independent resource namespace constrained to
+          deploying instances into Compute Engine zones inside the location.
+          Overrides the default dataproc/location property value for this
+          command invocation.
+
+          To set the location attribute:
+          ▸ provide the argument session_template on the command line with a
+            fully specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property dataproc/location.
+
+FLAGS
+     --source=SOURCE
+        Path to a YAML file containing configuration export data.
+        Alternatively, you may omit this flag to read from standard input.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice.
+
diff --git a/gcloud/beta/dataproc/session-templates/list b/gcloud/beta/dataproc/session-templates/list
new file mode 100644
index 000000000..d14366c36
--- /dev/null
+++ b/gcloud/beta/dataproc/session-templates/list
@@ -0,0 +1,64 @@
+NAME
+    gcloud beta dataproc session-templates list - list session templates
+
+SYNOPSIS
+    gcloud beta dataproc session-templates list [--location=LOCATION]
+        [--filter=EXPRESSION] [--limit=LIMIT]
+        [--page-size=PAGE_SIZE; default=100] [--sort-by=[FIELD,...]] [--uri]
+        [GCLOUD_WIDE_FLAG ...]
+
+EXAMPLES
+    The following command lists all session templates in Dataproc's
+    'us-central1' region:
+
+        $ gcloud beta dataproc session-templates list --location=us-central1
+
+FLAGS
+     --location=LOCATION
+        Dataproc location to use. Each Dataproc location constitutes an
+        independent resource namespace constrained to deploying instances into
+        Compute Engine zones inside the location. Overrides the default
+        dataproc/location property value for this command invocation.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE; default=100
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is 100.
+        Paging may be applied before or after --filter and --limit depending on
+        the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice.
+
diff --git a/gcloud/beta/dataproc/sessions/create/help b/gcloud/beta/dataproc/sessions/create/help
new file mode 100644
index 000000000..4157a3c0b
--- /dev/null
+++ b/gcloud/beta/dataproc/sessions/create/help
@@ -0,0 +1,135 @@
+NAME
+    gcloud beta dataproc sessions create - create a Dataproc session
+
+SYNOPSIS
+    gcloud beta dataproc sessions create COMMAND [--async]
+        [--container-image=CONTAINER_IMAGE]
+        [--history-server-cluster=HISTORY_SERVER_CLUSTER] [--kernel=KERNEL]
+        [--kms-key=KMS_KEY] [--labels=[KEY=VALUE,...]] [--max-idle=MAX_IDLE]
+        [--metastore-service=METASTORE_SERVICE]
+        [--property=[PROPERTY=VALUE,...]] [--request-id=REQUEST_ID]
+        [--service-account=SERVICE_ACCOUNT]
+        [--session_template=SESSION_TEMPLATE] [--staging-bucket=STAGING_BUCKET]
+        [--tags=[TAGS,...]] [--ttl=TTL] [--user=USER] [--version=VERSION]
+        [--network=NETWORK | --subnet=SUBNET] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Create various sessions, such as Spark.
+
+EXAMPLES
+    To create a Spark session, run:
+
+        $ gcloud beta dataproc sessions create spark my-session \
+            --location='us-central1'
+
+FLAGS
+     --async
+        Return immediately without waiting for the operation in progress to
+        complete.
+
+     --container-image=CONTAINER_IMAGE
+        Optional custom container image to use for the batch/session runtime
+        environment. If not specified, a default container image will be used.
+        The value should follow the container image naming format:
+        {registry}/{repository}/{name}:{tag}, for example,
+        gcr.io/my-project/my-image:1.2.3
+
+     --history-server-cluster=HISTORY_SERVER_CLUSTER
+        Spark History Server configuration for the batch/session job. Resource
+        name of an existing Dataproc cluster to act as a Spark History Server
+        for the workload in the format:
+        "projects/{project_id}/regions/{region}/clusters/{cluster_name}".
+
+     --kernel=KERNEL
+        Jupyter kernel type. The value could be "python" or "scala". KERNEL
+        must be one of: python, scala.
+
+     --kms-key=KMS_KEY
+        Cloud KMS key to use for encryption.
+
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     --max-idle=MAX_IDLE
+        The duration after which an idle session will be automatically
+        terminated, for example, "20m" or "2h". A session is considered idle if
+        it has no active Spark applications and no active Jupyter kernels. Run
+        gcloud topic datetimes
+        (https://cloud.google.com/sdk/gcloud/reference/topic/datetimes) for
+        information on duration formats.
+
+     --metastore-service=METASTORE_SERVICE
+        Name of a Dataproc Metastore service to be used as an external
+        metastore in the format:
+        "projects/{project-id}/locations/{region}/services/{service-name}".
+
+     --property=[PROPERTY=VALUE,...]
+        Specifies configuration properties.
+
+     --request-id=REQUEST_ID
+        A unique ID that identifies the request. If the service receives two
+        session create requests with the same request_id, the second request is
+        ignored and the operation that corresponds to the first session created
+        and stored in the backend is returned. Recommendation: Always set this
+        value to a UUID. The value must contain only letters (a-z, A-Z),
+        numbers (0-9), underscores (), and hyphens (-). The maximum length is
+        40 characters.
+
+     --service-account=SERVICE_ACCOUNT
+        The IAM service account to be used for a batch/session job.
+
+     --session_template=SESSION_TEMPLATE
+        The session template to use for creating the session.
+
+     --staging-bucket=STAGING_BUCKET
+        The Cloud Storage bucket to use to store job dependencies, config
+        files, and job driver console output. If not specified, the default
+        [staging bucket]
+        (https://cloud.google.com/dataproc-serverless/docs/concepts/buckets) is
+        used.
+
+     --tags=[TAGS,...]
+        Network tags for traffic control.
+
+     --ttl=TTL
+        The duration after the workload will be unconditionally terminated, for
+        example, '20m' or '1h'. Run gcloud topic datetimes
+        (https://cloud.google.com/sdk/gcloud/reference/topic/datetimes) for
+        information on duration formats.
+
+     --user=USER
+        The email address of the user who owns the session. The session will be
+        authenticated as this user if credentials injection is enabled.
+
+     --version=VERSION
+        Optional runtime version. If not specified, a default version will be
+        used.
+
+     At most one of these can be specified:
+
+       --network=NETWORK
+          Network URI to connect network to.
+
+       --subnet=SUBNET
+          Subnetwork URI to connect network to. Subnet must have Private Google
+          Access enabled.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     spark
+        (BETA) Create a Spark session.
+
+NOTES
+    This command is currently in beta and might change without notice.
+
diff --git a/gcloud/beta/dataproc/sessions/create/spark b/gcloud/beta/dataproc/sessions/create/spark
new file mode 100644
index 000000000..7d700bdc7
--- /dev/null
+++ b/gcloud/beta/dataproc/sessions/create/spark
@@ -0,0 +1,167 @@
+NAME
+    gcloud beta dataproc sessions create spark - create a Spark session
+
+SYNOPSIS
+    gcloud beta dataproc sessions create spark (SESSION : --location=LOCATION)
+        [--async] [--container-image=CONTAINER_IMAGE]
+        [--history-server-cluster=HISTORY_SERVER_CLUSTER] [--kernel=KERNEL]
+        [--kms-key=KMS_KEY] [--labels=[KEY=VALUE,...]] [--max-idle=MAX_IDLE]
+        [--metastore-service=METASTORE_SERVICE]
+        [--property=[PROPERTY=VALUE,...]] [--request-id=REQUEST_ID]
+        [--service-account=SERVICE_ACCOUNT]
+        [--session_template=SESSION_TEMPLATE] [--staging-bucket=STAGING_BUCKET]
+        [--tags=[TAGS,...]] [--ttl=TTL] [--user=USER] [--version=VERSION]
+        [--network=NETWORK | --subnet=SUBNET] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Create a Spark session.
+
+EXAMPLES
+    To create a Spark session, to:
+
+        $ gcloud beta dataproc sessions create spark my-session \
+            --location=us-central1
+
+POSITIONAL ARGUMENTS
+     Session resource - ID of the session to create. The arguments in this
+     group can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument session on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       SESSION
+          ID of the session or fully qualified identifier for the session.
+
+          To set the session attribute:
+          ▸ provide the argument session on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Dataproc location for the session. Each Dataproc location constitutes
+          an independent resource namespace constrained to deploying instances
+          into Compute Engine zones inside the location. Overrides the default
+          dataproc/location property value for this command invocation.
+
+          To set the location attribute:
+          ▸ provide the argument session on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property dataproc/location.
+
+FLAGS
+     --async
+        Return immediately without waiting for the operation in progress to
+        complete.
+
+     --container-image=CONTAINER_IMAGE
+        Optional custom container image to use for the batch/session runtime
+        environment. If not specified, a default container image will be used.
+        The value should follow the container image naming format:
+        {registry}/{repository}/{name}:{tag}, for example,
+        gcr.io/my-project/my-image:1.2.3
+
+     --history-server-cluster=HISTORY_SERVER_CLUSTER
+        Spark History Server configuration for the batch/session job. Resource
+        name of an existing Dataproc cluster to act as a Spark History Server
+        for the workload in the format:
+        "projects/{project_id}/regions/{region}/clusters/{cluster_name}".
+
+     --kernel=KERNEL
+        Jupyter kernel type. The value could be "python" or "scala". KERNEL
+        must be one of: python, scala.
+
+     --kms-key=KMS_KEY
+        Cloud KMS key to use for encryption.
+
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     --max-idle=MAX_IDLE
+        The duration after which an idle session will be automatically
+        terminated, for example, "20m" or "2h". A session is considered idle if
+        it has no active Spark applications and no active Jupyter kernels. Run
+        gcloud topic datetimes
+        (https://cloud.google.com/sdk/gcloud/reference/topic/datetimes) for
+        information on duration formats.
+
+     --metastore-service=METASTORE_SERVICE
+        Name of a Dataproc Metastore service to be used as an external
+        metastore in the format:
+        "projects/{project-id}/locations/{region}/services/{service-name}".
+
+     --property=[PROPERTY=VALUE,...]
+        Specifies configuration properties.
+
+     --request-id=REQUEST_ID
+        A unique ID that identifies the request. If the service receives two
+        session create requests with the same request_id, the second request is
+        ignored and the operation that corresponds to the first session created
+        and stored in the backend is returned. Recommendation: Always set this
+        value to a UUID. The value must contain only letters (a-z, A-Z),
+        numbers (0-9), underscores (), and hyphens (-). The maximum length is
+        40 characters.
+
+     --service-account=SERVICE_ACCOUNT
+        The IAM service account to be used for a batch/session job.
+
+     --session_template=SESSION_TEMPLATE
+        The session template to use for creating the session.
+
+     --staging-bucket=STAGING_BUCKET
+        The Cloud Storage bucket to use to store job dependencies, config
+        files, and job driver console output. If not specified, the default
+        [staging bucket]
+        (https://cloud.google.com/dataproc-serverless/docs/concepts/buckets) is
+        used.
+
+     --tags=[TAGS,...]
+        Network tags for traffic control.
+
+     --ttl=TTL
+        The duration after the workload will be unconditionally terminated, for
+        example, '20m' or '1h'. Run gcloud topic datetimes
+        (https://cloud.google.com/sdk/gcloud/reference/topic/datetimes) for
+        information on duration formats.
+
+     --user=USER
+        The email address of the user who owns the session. The session will be
+        authenticated as this user if credentials injection is enabled.
+
+     --version=VERSION
+        Optional runtime version. If not specified, a default version will be
+        used.
+
+     At most one of these can be specified:
+
+       --network=NETWORK
+          Network URI to connect network to.
+
+       --subnet=SUBNET
+          Subnetwork URI to connect network to. Subnet must have Private Google
+          Access enabled.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice.
+
diff --git a/gcloud/beta/dataproc/sessions/delete b/gcloud/beta/dataproc/sessions/delete
new file mode 100644
index 000000000..1e7075b35
--- /dev/null
+++ b/gcloud/beta/dataproc/sessions/delete
@@ -0,0 +1,67 @@
+NAME
+    gcloud beta dataproc sessions delete - delete a session
+
+SYNOPSIS
+    gcloud beta dataproc sessions delete (SESSION : --location=LOCATION)
+        [--async] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Delete a session.
+
+EXAMPLES
+    To delete a "my-session" session in the "us-central1" location, run:
+
+        $ gcloud beta dataproc sessions delete my-session \
+            --location=us-central1
+
+POSITIONAL ARGUMENTS
+     Session resource - ID of the session to delete. The arguments in this
+     group can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument session on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       SESSION
+          ID of the session or fully qualified identifier for the session.
+
+          To set the session attribute:
+          ▸ provide the argument session on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Dataproc location for the session. Each Dataproc location constitutes
+          an independent resource namespace constrained to deploying instances
+          into Compute Engine zones inside the location. Overrides the default
+          dataproc/location property value for this command invocation.
+
+          To set the location attribute:
+          ▸ provide the argument session on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property dataproc/location.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice.
+
diff --git a/gcloud/beta/dataproc/sessions/describe b/gcloud/beta/dataproc/sessions/describe
new file mode 100644
index 000000000..ba70d3f0c
--- /dev/null
+++ b/gcloud/beta/dataproc/sessions/describe
@@ -0,0 +1,62 @@
+NAME
+    gcloud beta dataproc sessions describe - describe a session
+
+SYNOPSIS
+    gcloud beta dataproc sessions describe (SESSION : --location=LOCATION)
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Describe a session.
+
+EXAMPLES
+    To describe a session, run:
+
+        $ gcloud beta dataproc sessions describe EXAMPLE-SESSION \
+            --location=us-central1
+
+POSITIONAL ARGUMENTS
+     Session resource - ID of the session to describe. The arguments in this
+     group can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument session on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       SESSION
+          ID of the session or fully qualified identifier for the session.
+
+          To set the session attribute:
+          ▸ provide the argument session on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Dataproc location for the session. Each Dataproc location constitutes
+          an independent resource namespace constrained to deploying instances
+          into Compute Engine zones inside the location. Overrides the default
+          dataproc/location property value for this command invocation.
+
+          To set the location attribute:
+          ▸ provide the argument session on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property dataproc/location.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice.
+
diff --git a/gcloud/beta/dataproc/sessions/help b/gcloud/beta/dataproc/sessions/help
new file mode 100644
index 000000000..254518548
--- /dev/null
+++ b/gcloud/beta/dataproc/sessions/help
@@ -0,0 +1,63 @@
+NAME
+    gcloud beta dataproc sessions - create and manage Dataproc sessions
+
+SYNOPSIS
+    gcloud beta dataproc sessions GROUP | COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Create and manage Dataproc sessions.
+
+    Create a session:
+
+        $ gcloud beta dataproc sessions create
+
+    List all sessions:
+
+        $ gcloud beta dataproc sessions list
+
+    List session details:
+
+        $ gcloud beta dataproc sessions describe SESSION_ID
+
+    Delete a session:
+
+        $ gcloud beta dataproc sessions delete SESSION_ID
+
+    Terminate an active session:
+
+        $ gcloud beta dataproc sessions terminate SESSION_ID
+
+    Enable Personal Auth on an active session:
+
+        $ gcloud beta dataproc sessions enable-personal-auth-session \
+            SESSION_ID
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+GROUPS
+    GROUP is one of the following:
+
+     create
+        (BETA) Create a Dataproc session.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     delete
+        (BETA) Delete a session.
+
+     describe
+        (BETA) Describe a session.
+
+     list
+        (BETA) List sessions in a project.
+
+     terminate
+        (BETA) Terminate an active session.
+
+NOTES
+    This command is currently in beta and might change without notice.
+
diff --git a/gcloud/beta/dataproc/sessions/list b/gcloud/beta/dataproc/sessions/list
new file mode 100644
index 000000000..05df39ccd
--- /dev/null
+++ b/gcloud/beta/dataproc/sessions/list
@@ -0,0 +1,53 @@
+NAME
+    gcloud beta dataproc sessions list - list sessions in a project
+
+SYNOPSIS
+    gcloud beta dataproc sessions list [--location=LOCATION] [--limit=LIMIT]
+        [--page-size=PAGE_SIZE; default=100] [--sort-by=[FIELD,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) List sessions in a project. Page-size sets the maximum number of
+    sessions returned per page, and Page-token retrieves subsequent results.
+
+EXAMPLES
+    List sessions in the "us-central1" location:
+
+        $ gcloud beta dataproc sessions list --location="us-central1"
+
+FLAGS
+     --location=LOCATION
+        Dataproc location to use. Each Dataproc location constitutes an
+        independent resource namespace constrained to deploying instances into
+        Compute Engine zones inside the location. Overrides the default
+        dataproc/location property value for this command invocation.
+
+LIST COMMAND FLAGS
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE; default=100
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is 100.
+        Paging may be applied before or after --filter and --limit depending on
+        the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice.
+
diff --git a/gcloud/beta/dataproc/sessions/terminate b/gcloud/beta/dataproc/sessions/terminate
new file mode 100644
index 000000000..a4617f28d
--- /dev/null
+++ b/gcloud/beta/dataproc/sessions/terminate
@@ -0,0 +1,67 @@
+NAME
+    gcloud beta dataproc sessions terminate - terminate an active session
+
+SYNOPSIS
+    gcloud beta dataproc sessions terminate (SESSION : --location=LOCATION)
+        [--async] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Terminate an active session.
+
+EXAMPLES
+    To terminate a session "my-session" in the "us-central1" location, run:
+
+        $ gcloud beta dataproc sessions terminate my-session \
+            --location=us-central1
+
+POSITIONAL ARGUMENTS
+     Session resource - ID of the session to terminate. The arguments in this
+     group can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument session on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       SESSION
+          ID of the session or fully qualified identifier for the session.
+
+          To set the session attribute:
+          ▸ provide the argument session on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Dataproc location for the session. Each Dataproc location constitutes
+          an independent resource namespace constrained to deploying instances
+          into Compute Engine zones inside the location. Overrides the default
+          dataproc/location property value for this command invocation.
+
+          To set the location attribute:
+          ▸ provide the argument session on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property dataproc/location.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice.
+
diff --git a/gcloud/beta/dataproc/workflow-templates/set-managed-cluster b/gcloud/beta/dataproc/workflow-templates/set-managed-cluster
index 91acaea4a..ad3748a91 100644
--- a/gcloud/beta/dataproc/workflow-templates/set-managed-cluster
+++ b/gcloud/beta/dataproc/workflow-templates/set-managed-cluster
@@ -44,7 +44,8 @@ SYNOPSIS
           --tags=TAG,[TAG,...] --network=NETWORK | --subnet=SUBNET
           --reservation=RESERVATION
           --reservation-affinity=RESERVATION_AFFINITY; default="any"]
-        [--single-node | --num-secondary-workers=NUM_SECONDARY_WORKERS
+        [--single-node | --min-num-workers=MIN_NUM_WORKERS
+          --num-secondary-workers=NUM_SECONDARY_WORKERS
           --num-workers=NUM_WORKERS
           --secondary-worker-type=TYPE; default="preemptible"]
         [GCLOUD_WIDE_FLAG ...]
@@ -631,6 +632,10 @@ FLAGS
 
        Multi-node cluster flags
 
+         --min-num-workers=MIN_NUM_WORKERS
+            The minimum number of workers nodes to provision for cluster create
+            operations to succeed.
+
          --num-secondary-workers=NUM_SECONDARY_WORKERS
             The number of secondary worker nodes in the cluster.
 
diff --git a/gcloud/beta/filestore/backups/create b/gcloud/beta/filestore/backups/create
index 522f00da6..1e3775bda 100644
--- a/gcloud/beta/filestore/backups/create
+++ b/gcloud/beta/filestore/backups/create
@@ -6,7 +6,7 @@ SYNOPSIS
         --instance=INSTANCE --region=REGION
         (--instance-location=INSTANCE_LOCATION | --instance-zone=INSTANCE_ZONE)
         [--async] [--description=DESCRIPTION] [--kms-key=KMS_KEY]
-        [--labels=KEY=VALUE] [GCLOUD_WIDE_FLAG ...]
+        [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (BETA) Create a Filestore backup of an instance file share.
@@ -61,7 +61,7 @@ OPTIONAL FLAGS
         CMEK for backup in the form of
         projects/{project}/locations/{location}/keyRings/{key-ring}/cryptoKeys/{crypto-key}
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
 GCLOUD WIDE FLAGS
diff --git a/gcloud/beta/filestore/instances/snapshots/create b/gcloud/beta/filestore/instances/snapshots/create
index b522d0fcf..922d28233 100644
--- a/gcloud/beta/filestore/instances/snapshots/create
+++ b/gcloud/beta/filestore/instances/snapshots/create
@@ -7,7 +7,8 @@ SYNOPSIS
         --instance=INSTANCE
         (--instance-location=INSTANCE_LOCATION
           | --instance-region=INSTANCE_REGION) [--async]
-        [--description=DESCRIPTION] [--labels=KEY=VALUE] [GCLOUD_WIDE_FLAG ...]
+        [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (BETA) Create a Filestore snapshot of an instance.
@@ -49,7 +50,7 @@ OPTIONAL FLAGS
      --description=DESCRIPTION
         Description of the snapshot. Limit: 2048 characters.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
 GCLOUD WIDE FLAGS
diff --git a/gcloud/beta/firestore/indexes/composite/create b/gcloud/beta/firestore/indexes/composite/create
index 9ae5d8e20..eabf8967d 100644
--- a/gcloud/beta/firestore/indexes/composite/create
+++ b/gcloud/beta/firestore/indexes/composite/create
@@ -3,7 +3,9 @@ NAME
         index
 
 SYNOPSIS
-    gcloud beta firestore indexes composite create --field-config=FIELD_CONFIG
+    gcloud beta firestore indexes composite create
+        --field-config=[array-config=ARRAY-CONFIG],
+          [field-path=FIELD-PATH],[order=ORDER]
         (--collection-group=COLLECTION_GROUP : --database=DATABASE)
         [--api-scope=API_SCOPE; default="any-api"] [--async]
         [--query-scope=QUERY_SCOPE; default="collection"]
@@ -28,7 +30,7 @@ EXAMPLES
             --field-config=field-path=timestamp,order=descending
 
 REQUIRED FLAGS
-     --field-config=FIELD_CONFIG
+     --field-config=[array-config=ARRAY-CONFIG],[field-path=FIELD-PATH],[order=ORDER]
         Configuration for a field.
 
         This flag must be repeated to provide the ordered list of field
diff --git a/gcloud/beta/firestore/indexes/fields/update b/gcloud/beta/firestore/indexes/fields/update
index df0b8be50..f2e8847bb 100644
--- a/gcloud/beta/firestore/indexes/fields/update
+++ b/gcloud/beta/firestore/indexes/fields/update
@@ -5,8 +5,8 @@ NAME
 SYNOPSIS
     gcloud beta firestore indexes fields update
         (FIELD : --collection-group=COLLECTION_GROUP --database=DATABASE)
-        (--clear-exemption | --disable-indexes | --index=KEY=VALUE) [--async]
-        [GCLOUD_WIDE_FLAG ...]
+        (--clear-exemption | --disable-indexes | --index=[KEY=VALUE,...])
+        [--async] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (BETA) Update the index configuration of the given field.
@@ -88,7 +88,7 @@ REQUIRED FLAGS
        --disable-indexes
           If provided, the field will no longer be indexed at all.
 
-       --index=KEY=VALUE
+       --index=[KEY=VALUE,...]
           An index for the field.
 
           This flag can be repeated to provide multiple indexes. Any existing
diff --git a/gcloud/beta/healthcare/consent-stores/check-data-access b/gcloud/beta/healthcare/consent-stores/check-data-access
index dfec7ec81..0ce4ec116 100644
--- a/gcloud/beta/healthcare/consent-stores/check-data-access
+++ b/gcloud/beta/healthcare/consent-stores/check-data-access
@@ -5,7 +5,7 @@ NAME
 SYNOPSIS
     gcloud beta healthcare consent-stores check-data-access
         (CONSENT_STORE : --dataset=DATASET --location=LOCATION)
-        --data-id=DATA_ID [--request-attributes=[REQUEST_ATTRIBUTES,...]]
+        --data-id=DATA_ID [--request-attributes=[KEY=VALUE,...]]
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -68,7 +68,7 @@ REQUIRED FLAGS
         The unique identifier of the data to check access for.
 
 OPTIONAL FLAGS
-     --request-attributes=[REQUEST_ATTRIBUTES,...]
+     --request-attributes=[KEY=VALUE,...]
         Comma-separated list of request attributes associated with this access
         request. Each attribute has the form "KEY=VALUE".
 
diff --git a/gcloud/beta/healthcare/consent-stores/evaluate-user-consents b/gcloud/beta/healthcare/consent-stores/evaluate-user-consents
index 18cb1d767..32b2f39ae 100644
--- a/gcloud/beta/healthcare/consent-stores/evaluate-user-consents
+++ b/gcloud/beta/healthcare/consent-stores/evaluate-user-consents
@@ -7,9 +7,9 @@ SYNOPSIS
         (CONSENT_STORE : --dataset=DATASET --location=LOCATION)
         --user-id=USER_ID [--consent-list=[CONSENT_LIST,...]]
         [--page-size=PAGE_SIZE] [--page-token=PAGE_TOKEN]
-        [--request-attributes=[REQUEST_ATTRIBUTES,...]]
-        [--resource-attributes=[RESOURCE_ATTRIBUTES,...]]
-        [--response-view=RESPONSE_VIEW] [GCLOUD_WIDE_FLAG ...]
+        [--request-attributes=[KEY=VALUE,...]]
+        [--resource-attributes=[KEY=VALUE,...]] [--response-view=RESPONSE_VIEW]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (BETA) Check if each matching user data mapping in the given Cloud
@@ -84,11 +84,11 @@ OPTIONAL FLAGS
      --page-token=PAGE_TOKEN
         Token to retrieve the next page of results.
 
-     --request-attributes=[REQUEST_ATTRIBUTES,...]
+     --request-attributes=[KEY=VALUE,...]
         Comma-separated list of request attributes associated with this access
         request. Each attribute has the form "KEY=VALUE".
 
-     --resource-attributes=[RESOURCE_ATTRIBUTES,...]
+     --resource-attributes=[KEY=VALUE,...]
         Comma-separated list of resource attributes associated with this access
         request. Each attribute has the form "KEY=VALUE". If no values are
         specified, then all data types are queried.
diff --git a/gcloud/beta/healthcare/consent-stores/query-accessible-data b/gcloud/beta/healthcare/consent-stores/query-accessible-data
index e212b4a08..3471de318 100644
--- a/gcloud/beta/healthcare/consent-stores/query-accessible-data
+++ b/gcloud/beta/healthcare/consent-stores/query-accessible-data
@@ -5,10 +5,8 @@ NAME
 SYNOPSIS
     gcloud beta healthcare consent-stores query-accessible-data
         (CONSENT_STORE : --dataset=DATASET --location=LOCATION)
-        --gcs-uri=GCS_URI [--async]
-        [--request-attributes=[REQUEST_ATTRIBUTES,...]]
-        [--resource-attributes=[RESOURCE_ATTRIBUTES,...]]
-        [GCLOUD_WIDE_FLAG ...]
+        --gcs-uri=GCS_URI [--async] [--request-attributes=[KEY=VALUE,...]]
+        [--resource-attributes=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (BETA) Queries all data IDs that are consented for a given use in the given
@@ -79,11 +77,11 @@ OPTIONAL FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
-     --request-attributes=[REQUEST_ATTRIBUTES,...]
+     --request-attributes=[KEY=VALUE,...]
         Comma-separated list of request attributes associated with this access
         request. Each attribute has the form "KEY=VALUE".
 
-     --resource-attributes=[RESOURCE_ATTRIBUTES,...]
+     --resource-attributes=[KEY=VALUE,...]
         Comma-separated list of resources attributes associated with the type
         of data being requested. Each attribute has the form "KEY=VALUE". If no
         values are specified, then all data types are included in the output.
diff --git a/gcloud/beta/iam/service-accounts/keys/create b/gcloud/beta/iam/service-accounts/keys/create
index d81607a85..ebf6cb9c0 100644
--- a/gcloud/beta/iam/service-accounts/keys/create
+++ b/gcloud/beta/iam/service-accounts/keys/create
@@ -1,6 +1,5 @@
 NAME
-    gcloud beta iam service-accounts keys create - create a private key for a
-        service account
+    gcloud beta iam service-accounts keys create - create a service account key
 
 SYNOPSIS
     gcloud beta iam service-accounts keys create OUTPUT-FILE
@@ -12,7 +11,7 @@ DESCRIPTION
     PERMISSION_DENIED error.
 
 EXAMPLES
-    To create a new private key for a service account, and save a copy of it
+    To create a new service account key and save the private portion of the key
     locally, run:
 
         $ gcloud beta iam service-accounts keys create key.json \
diff --git a/gcloud/beta/iam/service-accounts/keys/delete b/gcloud/beta/iam/service-accounts/keys/delete
index 6e519c23b..f8573a948 100644
--- a/gcloud/beta/iam/service-accounts/keys/delete
+++ b/gcloud/beta/iam/service-accounts/keys/delete
@@ -1,6 +1,5 @@
 NAME
-    gcloud beta iam service-accounts keys delete - delete a user-managed key
-        from a service account
+    gcloud beta iam service-accounts keys delete - delete a service account key
 
 SYNOPSIS
     gcloud beta iam service-accounts keys delete KEY-ID
diff --git a/gcloud/beta/iam/service-accounts/keys/disable b/gcloud/beta/iam/service-accounts/keys/disable
index 24b127510..de5770fc5 100644
--- a/gcloud/beta/iam/service-accounts/keys/disable
+++ b/gcloud/beta/iam/service-accounts/keys/disable
@@ -1,13 +1,13 @@
 NAME
-    gcloud beta iam service-accounts keys disable - disable a public key
-        related to an IAM service account
+    gcloud beta iam service-accounts keys disable - disable a service account
+        key
 
 SYNOPSIS
     gcloud beta iam service-accounts keys disable
         (IAM_KEY : --iam-account=IAM_ACCOUNT) [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (BETA) Disable a public key related to an IAM service account.
+    (BETA) Disable a service account key.
 
     If the service account does not exist, this command returns a
     PERMISSION_DENIED error.
diff --git a/gcloud/beta/iam/service-accounts/keys/enable b/gcloud/beta/iam/service-accounts/keys/enable
index 2482e59aa..55b00794e 100644
--- a/gcloud/beta/iam/service-accounts/keys/enable
+++ b/gcloud/beta/iam/service-accounts/keys/enable
@@ -1,13 +1,12 @@
 NAME
-    gcloud beta iam service-accounts keys enable - enable a public key related
-        to an IAM service account
+    gcloud beta iam service-accounts keys enable - enable a service account key
 
 SYNOPSIS
     gcloud beta iam service-accounts keys enable
         (IAM_KEY : --iam-account=IAM_ACCOUNT) [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (BETA) Enable a public key related to an IAM service account.
+    (BETA) Enable a service account key.
 
     If the service account does not exist, this command returns a
     PERMISSION_DENIED error.
diff --git a/gcloud/beta/iam/service-accounts/keys/help b/gcloud/beta/iam/service-accounts/keys/help
index 6e7dc1a81..385b9d8e1 100644
--- a/gcloud/beta/iam/service-accounts/keys/help
+++ b/gcloud/beta/iam/service-accounts/keys/help
@@ -16,16 +16,16 @@ COMMANDS
     COMMAND is one of the following:
 
      create
-        (BETA) Create a private key for a service account.
+        (BETA) Create a service account key.
 
      delete
-        (BETA) Delete a user-managed key from a service account.
+        (BETA) Delete a service account key.
 
      disable
-        (BETA) Disable a public key related to an IAM service account.
+        (BETA) Disable a service account key.
 
      enable
-        (BETA) Enable a public key related to an IAM service account.
+        (BETA) Enable a service account key.
 
      get-public-key
         (BETA) Get the public key for a service account key pair.
diff --git a/gcloud/beta/iam/workforce-pools/providers/create-oidc b/gcloud/beta/iam/workforce-pools/providers/create-oidc
index 82f11662c..5488c0639 100644
--- a/gcloud/beta/iam/workforce-pools/providers/create-oidc
+++ b/gcloud/beta/iam/workforce-pools/providers/create-oidc
@@ -5,7 +5,7 @@ NAME
 SYNOPSIS
     gcloud beta iam workforce-pools providers create-oidc
         (PROVIDER : --location=LOCATION --workforce-pool=WORKFORCE_POOL)
-        --attribute-mapping=[ATTRIBUTE_MAPPING,...] --client-id=CLIENT_ID
+        --attribute-mapping=[KEY=VALUE,...] --client-id=CLIENT_ID
         --issuer-uri=ISSUER_URI
         (--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR
           --web-sso-response-type=WEB_SSO_RESPONSE_TYPE
@@ -73,7 +73,7 @@ POSITIONAL ARGUMENTS
           ▸ provide the argument --workforce-pool on the command line.
 
 REQUIRED FLAGS
-     --attribute-mapping=[ATTRIBUTE_MAPPING,...]
+     --attribute-mapping=[KEY=VALUE,...]
         Maps claims from the authentication credentials issued by the Identity
         Provider into Google Cloud IAM attributes, e.g. subject, segment.
 
diff --git a/gcloud/beta/iam/workforce-pools/providers/update-oidc b/gcloud/beta/iam/workforce-pools/providers/update-oidc
index 494c85f08..94f6716d8 100644
--- a/gcloud/beta/iam/workforce-pools/providers/update-oidc
+++ b/gcloud/beta/iam/workforce-pools/providers/update-oidc
@@ -6,7 +6,7 @@ SYNOPSIS
     gcloud beta iam workforce-pools providers update-oidc
         (PROVIDER : --location=LOCATION --workforce-pool=WORKFORCE_POOL)
         [--async] [--attribute-condition=ATTRIBUTE_CONDITION]
-        [--attribute-mapping=[ATTRIBUTE_MAPPING,...]] [--client-id=CLIENT_ID]
+        [--attribute-mapping=[KEY=VALUE,...]] [--client-id=CLIENT_ID]
         [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME]
         [--issuer-uri=ISSUER_URI]
         [--web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...]]
@@ -105,7 +105,7 @@ FLAGS
 
             "'admins' in google.groups"
 
-     --attribute-mapping=[ATTRIBUTE_MAPPING,...]
+     --attribute-mapping=[KEY=VALUE,...]
         Maps claims from the authentication credentials issued by the Identity
         Provider into Google Cloud IAM attributes, e.g. subject, segment.
 
diff --git a/gcloud/beta/iam/workload-identity-pools/providers/create-aws b/gcloud/beta/iam/workload-identity-pools/providers/create-aws
index 0e2065e7f..e30f5e735 100644
--- a/gcloud/beta/iam/workload-identity-pools/providers/create-aws
+++ b/gcloud/beta/iam/workload-identity-pools/providers/create-aws
@@ -7,9 +7,8 @@ SYNOPSIS
         (PROVIDER : --location=LOCATION
           --workload-identity-pool=WORKLOAD_IDENTITY_POOL)
         --account-id=ACCOUNT_ID [--attribute-condition=ATTRIBUTE_CONDITION]
-        [--attribute-mapping=[ATTRIBUTE_MAPPING,...]]
-        [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME]
-        [GCLOUD_WIDE_FLAG ...]
+        [--attribute-mapping=[KEY=VALUE,...]] [--description=DESCRIPTION]
+        [--disabled] [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (BETA) Create a new AWS workload identity pool provider.
@@ -103,7 +102,7 @@ OPTIONAL FLAGS
 
             "'admins' in google.groups"
 
-     --attribute-mapping=[ATTRIBUTE_MAPPING,...]
+     --attribute-mapping=[KEY=VALUE,...]
         Maps attributes from authentication credentials issued by an external
         identity provider to Google Cloud attributes, such as subject and
         segment.
diff --git a/gcloud/beta/iam/workload-identity-pools/providers/create-oidc b/gcloud/beta/iam/workload-identity-pools/providers/create-oidc
index 8ca30da70..e2d61d1c3 100644
--- a/gcloud/beta/iam/workload-identity-pools/providers/create-oidc
+++ b/gcloud/beta/iam/workload-identity-pools/providers/create-oidc
@@ -6,7 +6,7 @@ SYNOPSIS
     gcloud beta iam workload-identity-pools providers create-oidc
         (PROVIDER : --location=LOCATION
           --workload-identity-pool=WORKLOAD_IDENTITY_POOL)
-        --attribute-mapping=[ATTRIBUTE_MAPPING,...] --issuer-uri=ISSUER_URI
+        --attribute-mapping=[KEY=VALUE,...] --issuer-uri=ISSUER_URI
         [--allowed-audiences=[ALLOWED_AUDIENCES,...]]
         [--attribute-condition=ATTRIBUTE_CONDITION] [--description=DESCRIPTION]
         [--disabled] [--display-name=DISPLAY_NAME]
@@ -76,7 +76,7 @@ POSITIONAL ARGUMENTS
             line.
 
 REQUIRED FLAGS
-     --attribute-mapping=[ATTRIBUTE_MAPPING,...]
+     --attribute-mapping=[KEY=VALUE,...]
         Maps attributes from authentication credentials issued by an external
         identity provider to Google Cloud attributes, such as subject and
         segment.
diff --git a/gcloud/beta/iam/workload-identity-pools/providers/update-aws b/gcloud/beta/iam/workload-identity-pools/providers/update-aws
index 0495f0955..328f66311 100644
--- a/gcloud/beta/iam/workload-identity-pools/providers/update-aws
+++ b/gcloud/beta/iam/workload-identity-pools/providers/update-aws
@@ -7,9 +7,8 @@ SYNOPSIS
         (PROVIDER : --location=LOCATION
           --workload-identity-pool=WORKLOAD_IDENTITY_POOL)
         [--account-id=ACCOUNT_ID] [--attribute-condition=ATTRIBUTE_CONDITION]
-        [--attribute-mapping=[ATTRIBUTE_MAPPING,...]]
-        [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME]
-        [GCLOUD_WIDE_FLAG ...]
+        [--attribute-mapping=[KEY=VALUE,...]] [--description=DESCRIPTION]
+        [--disabled] [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (BETA) Update an AWS workload identity pool provider.
@@ -102,7 +101,7 @@ FLAGS
 
             "'admins' in google.groups"
 
-     --attribute-mapping=[ATTRIBUTE_MAPPING,...]
+     --attribute-mapping=[KEY=VALUE,...]
         Maps attributes from authentication credentials issued by an external
         identity provider to Google Cloud attributes, such as subject and
         segment.
diff --git a/gcloud/beta/iam/workload-identity-pools/providers/update-oidc b/gcloud/beta/iam/workload-identity-pools/providers/update-oidc
index ece9aec4b..e02b0962a 100644
--- a/gcloud/beta/iam/workload-identity-pools/providers/update-oidc
+++ b/gcloud/beta/iam/workload-identity-pools/providers/update-oidc
@@ -8,10 +8,9 @@ SYNOPSIS
           --workload-identity-pool=WORKLOAD_IDENTITY_POOL)
         [--allowed-audiences=[ALLOWED_AUDIENCES,...]]
         [--attribute-condition=ATTRIBUTE_CONDITION]
-        [--attribute-mapping=[ATTRIBUTE_MAPPING,...]]
-        [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME]
-        [--issuer-uri=ISSUER_URI] [--jwk-json-path=JWK_JSON_PATH]
-        [GCLOUD_WIDE_FLAG ...]
+        [--attribute-mapping=[KEY=VALUE,...]] [--description=DESCRIPTION]
+        [--disabled] [--display-name=DISPLAY_NAME] [--issuer-uri=ISSUER_URI]
+        [--jwk-json-path=JWK_JSON_PATH] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (BETA) Update an OIDC workload identity pool provider.
@@ -117,7 +116,7 @@ FLAGS
 
             "'admins' in google.groups"
 
-     --attribute-mapping=[ATTRIBUTE_MAPPING,...]
+     --attribute-mapping=[KEY=VALUE,...]
         Maps attributes from authentication credentials issued by an external
         identity provider to Google Cloud attributes, such as subject and
         segment.
diff --git a/gcloud/beta/identity/groups/create b/gcloud/beta/identity/groups/create
index 04af5f7ad..d75bd1c3a 100644
--- a/gcloud/beta/identity/groups/create
+++ b/gcloud/beta/identity/groups/create
@@ -4,7 +4,8 @@ NAME
 SYNOPSIS
     gcloud beta identity groups create EMAIL --organization=ORGANIZATION
         [--description=DESCRIPTION] [--display-name=DISPLAY_NAME]
-        [--dynamic-user-query=DYNAMIC_USER_QUERY] [--posix-group=POSIX_GROUP]
+        [--dynamic-user-query=DYNAMIC_USER_QUERY]
+        [--posix-group=[gid=GID],[name=NAME]]
         [--with-initial-owner=WITH_INITIAL_OWNER]
         [--group-type=GROUP_TYPE; default="discussion" | --labels=LABELS]
         [GCLOUD_WIDE_FLAG ...]
@@ -64,7 +65,7 @@ OPTIONAL FLAGS
         Example of a query:
         --dynamic-user-query="user.organizations.exists(org,org.title=='SWE')"
 
-     --posix-group=POSIX_GROUP
+     --posix-group=[gid=GID],[name=NAME]
         Group ID (gid) and name of the POSIX group that you want to associate
         with the specified Cloud Identity group. You can specify multiple POSIX
         groups with multiple instances of this flag.
diff --git a/gcloud/beta/identity/groups/update b/gcloud/beta/identity/groups/update
index 2882f98e2..52f452506 100644
--- a/gcloud/beta/identity/groups/update
+++ b/gcloud/beta/identity/groups/update
@@ -4,7 +4,7 @@ NAME
 SYNOPSIS
     gcloud beta identity groups update EMAIL
         [--dynamic-user-query=DYNAMIC_USER_QUERY] [--labels=LABELS]
-        [--add-posix-group=POSIX_GROUP | --clear-posix-groups
+        [--add-posix-group=[gid=GID],[name=NAME] | --clear-posix-groups
           | --remove-posix-groups=[POSIX_GROUP,...]]
         [--clear-description | --description=DESCRIPTION]
         [--clear-display-name | --display-name=DISPLAY_NAME]
@@ -65,7 +65,7 @@ FLAGS
 
      At most one of these can be specified:
 
-       --add-posix-group=POSIX_GROUP
+       --add-posix-group=[gid=GID],[name=NAME]
           Group id (gid) and a name for a POSIX group that you want to add to
           the specified Cloud Identity group. You can specify multiple POSIX
           groups to add with multiple instances of this flag.
diff --git a/gcloud/beta/memcache/instances/create b/gcloud/beta/memcache/instances/create
index c51f7652d..7f40305f4 100644
--- a/gcloud/beta/memcache/instances/create
+++ b/gcloud/beta/memcache/instances/create
@@ -6,7 +6,7 @@ SYNOPSIS
     gcloud beta memcache instances create (INSTANCE : --region=REGION)
         --node-count=NODE_COUNT --node-cpu=NODE_CPU --node-memory=NODE_MEMORY
         [--async] [--authorized-network=AUTHORIZED_NETWORK]
-        [--display-name=DISPLAY_NAME] [--labels=KEY=VALUE]
+        [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]]
         [--maintenance-window-day=MAINTENANCE_WINDOW_DAY]
         [--maintenance-window-duration=MAINTENANCE_WINDOW_DURATION]
         [--maintenance-window-start-time=MAINTENANCE_WINDOW_START_TIME]
@@ -90,7 +90,7 @@ OPTIONAL FLAGS
      --display-name=DISPLAY_NAME
         An arbitrary and optional user provided name for the instance.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
      --maintenance-window-day=MAINTENANCE_WINDOW_DAY
diff --git a/gcloud/beta/memcache/instances/update b/gcloud/beta/memcache/instances/update
index 7ff0d86d1..4970bbb33 100644
--- a/gcloud/beta/memcache/instances/update
+++ b/gcloud/beta/memcache/instances/update
@@ -5,7 +5,8 @@ NAME
 SYNOPSIS
     gcloud beta memcache instances update (INSTANCE : --region=REGION)
         (--parameters=KEY=VALUE | --display-name=DISPLAY_NAME
-          --labels=KEY=VALUE --node-count=NODE_COUNT --maintenance-window-any
+          --labels=[KEY=VALUE,...]
+          --node-count=NODE_COUNT --maintenance-window-any
           | --maintenance-window-day=MAINTENANCE_WINDOW_DAY
           --maintenance-window-duration=MAINTENANCE_WINDOW_DURATION
           --maintenance-window-start-time=MAINTENANCE_WINDOW_START_TIME)
@@ -142,7 +143,7 @@ REQUIRED FLAGS
        --display-name=DISPLAY_NAME
           An arbitrary and optional user provided name for the instance.
 
-       --labels=KEY=VALUE
+       --labels=[KEY=VALUE,...]
           List of label KEY=VALUE pairs to add.
 
        --node-count=NODE_COUNT
diff --git a/gcloud/beta/metastore/operations/cancel b/gcloud/beta/metastore/operations/cancel
index 64bd8daed..88d832147 100644
--- a/gcloud/beta/metastore/operations/cancel
+++ b/gcloud/beta/metastore/operations/cancel
@@ -56,8 +56,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud metastore operations cancel
 
         $ gcloud alpha metastore operations cancel
 
diff --git a/gcloud/beta/metastore/services/alter-table-properties b/gcloud/beta/metastore/services/alter-table-properties
index 5a1b0ab2b..1e1dc472a 100644
--- a/gcloud/beta/metastore/services/alter-table-properties
+++ b/gcloud/beta/metastore/services/alter-table-properties
@@ -4,7 +4,7 @@ NAME
 
 SYNOPSIS
     gcloud beta metastore services alter-table-properties
-        (SERVICE : --location=LOCATION) --properties=PROPERTIES
+        (SERVICE : --location=LOCATION) --properties=[KEY=VALUE,...]
         --table-name=TABLE_NAME --update-mask=UPDATE_MASK [--async]
         [GCLOUD_WIDE_FLAG ...]
 
@@ -62,7 +62,7 @@ POSITIONAL ARGUMENTS
           ▸ set the property metastore/location.
 
 REQUIRED FLAGS
-     --properties=PROPERTIES
+     --properties=[KEY=VALUE,...]
         A string where field names are separated by a comma. Describes the
         desired values to mutate. If update-mask is empty, the properties will
         not update. Otherwise, the properties only alter the values whose
diff --git a/gcloud/beta/metastore/services/create b/gcloud/beta/metastore/services/create
index 9d86a8b00..ea0a99038 100644
--- a/gcloud/beta/metastore/services/create
+++ b/gcloud/beta/metastore/services/create
@@ -14,7 +14,7 @@ SYNOPSIS
           | --auxiliary-versions-from-file=AUXILIARY_VERSIONS_FROM_FILE]
         [--consumer-subnetworks=[CONSUMER_SUBNETWORKS,...] | --network=NETWORK
           | --network-config-from-file=NETWORK_CONFIG_FROM_FILE]
-        [--hive-metastore-configs=KEY=VALUE
+        [--hive-metastore-configs=[KEY=VALUE,...]
           | --hive-metastore-configs-from-file=HIVE_METASTORE_CONFIGS_FROM_FILE]
         [--instance-size=INSTANCE_SIZE | --scaling-factor=SCALING_FACTOR
           | --tier=TIER]
@@ -225,7 +225,7 @@ FLAGS
 
      At most one of these can be specified:
 
-       --hive-metastore-configs=KEY=VALUE
+       --hive-metastore-configs=[KEY=VALUE,...]
           A mapping of Hive metastore configuration key-value pairs to apply to
           the Hive metastore.
 
diff --git a/gcloud/beta/metastore/services/update b/gcloud/beta/metastore/services/update
index 2c509f2e4..564449d71 100644
--- a/gcloud/beta/metastore/services/update
+++ b/gcloud/beta/metastore/services/update
@@ -14,7 +14,7 @@ SYNOPSIS
           --maintenance-window-hour=MAINTENANCE_WINDOW_HOUR]
         [--update-auxiliary-versions-from-file=UPDATE_AUXILIARY_VERSIONS_FROM_FILE | --add-auxiliary-versions=[ADD_AUXILIARY_VERSIONS,
           ...] --clear-auxiliary-versions]
-        [--update-hive-metastore-configs-from-file=UPDATE_HIVE_METASTORE_CONFIGS_FROM_FILE | --update-hive-metastore-configs=[UPDATE_HIVE_METASTORE_CONFIGS,
+        [--update-hive-metastore-configs-from-file=UPDATE_HIVE_METASTORE_CONFIGS_FROM_FILE | --update-hive-metastore-configs=[KEY=VALUE,
           ...] --clear-hive-metastore-configs
           | --remove-hive-metastore-configs=[REMOVE_HIVE_METASTORE_CONFIGS,
           ...]] [GCLOUD_WIDE_FLAG ...]
@@ -265,7 +265,7 @@ FLAGS
        Modify the Hive metastore configuration properties by passing key-value
        pairs in through the flags.
 
-         --update-hive-metastore-configs=[UPDATE_HIVE_METASTORE_CONFIGS,...]
+         --update-hive-metastore-configs=[KEY=VALUE,...]
             Comma-separated list of Hive metastore configurations. Each
             configuration has the form "NAME=VALUE".
 
diff --git a/gcloud/beta/ml/translate/batch-translate-text b/gcloud/beta/ml/translate/batch-translate-text
index 54b5b96fd..142dbcd78 100644
--- a/gcloud/beta/ml/translate/batch-translate-text
+++ b/gcloud/beta/ml/translate/batch-translate-text
@@ -4,9 +4,9 @@ NAME
 
 SYNOPSIS
     gcloud beta ml translate batch-translate-text --destination=DESTINATION
-        --source=[SOURCE,...] --source-language=SOURCE_LANGUAGE
+        --source=[FILE_PATH[=FILE_TYPE],...] --source-language=SOURCE_LANGUAGE
         --target-language-codes=[TARGET_LANGUAGE_CODES,...]
-        [--glossaries=[GLOSSARIES,...]] [--models=[MODELS,...]]
+        [--glossaries=[KEY=VALUE,...]] [--models=[KEY=VALUE,...]]
         [--zone=ZONE; default="global"] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -27,7 +27,7 @@ REQUIRED FLAGS
         Location to which the results should be written. Must be a Google Cloud
         Storage URI.
 
-     --source=[SOURCE,...]
+     --source=[FILE_PATH[=FILE_TYPE],...]
         Comma-separated list of entries of the form FILE_PATH[=FILE_TYPE]
         specifying source files and files types for the translation. FILE_PATH
         must be a Google Cloud Storage URI. FILE_TYPE defaults to 'text/html'
@@ -45,11 +45,11 @@ REQUIRED FLAGS
         language codes here.
 
 OPTIONAL FLAGS
-     --glossaries=[GLOSSARIES,...]
+     --glossaries=[KEY=VALUE,...]
         Glossaries to be applied for translation. Comma-separated dictionary
         where map's key is target language code, map's value is glossary name.
 
-     --models=[MODELS,...]
+     --models=[KEY=VALUE,...]
         Models to use for translation. Comma-separated dictionary where map's
         key is target language code, map's value is model name. Value can be a
         built-in general model, or an AutoML Translation model.
diff --git a/gcloud/beta/netapp/active-directories/create b/gcloud/beta/netapp/active-directories/create
index a308b16a3..ff2aae56e 100644
--- a/gcloud/beta/netapp/active-directories/create
+++ b/gcloud/beta/netapp/active-directories/create
@@ -143,8 +143,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp active-directories create
 
         $ gcloud alpha netapp active-directories create
 
diff --git a/gcloud/beta/netapp/active-directories/delete b/gcloud/beta/netapp/active-directories/delete
index 667f697c5..da0bda291 100644
--- a/gcloud/beta/netapp/active-directories/delete
+++ b/gcloud/beta/netapp/active-directories/delete
@@ -70,8 +70,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp active-directories delete
 
         $ gcloud alpha netapp active-directories delete
 
diff --git a/gcloud/beta/netapp/active-directories/describe b/gcloud/beta/netapp/active-directories/describe
index 531c8456b..868575041 100644
--- a/gcloud/beta/netapp/active-directories/describe
+++ b/gcloud/beta/netapp/active-directories/describe
@@ -59,8 +59,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp active-directories describe
 
         $ gcloud alpha netapp active-directories describe
 
diff --git a/gcloud/beta/netapp/active-directories/help b/gcloud/beta/netapp/active-directories/help
index 942f26246..eb0e9820e 100644
--- a/gcloud/beta/netapp/active-directories/help
+++ b/gcloud/beta/netapp/active-directories/help
@@ -32,8 +32,10 @@ COMMANDS
         (BETA) Update a Cloud NetApp Active Directory.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp active-directories
 
         $ gcloud alpha netapp active-directories
 
diff --git a/gcloud/beta/netapp/active-directories/list b/gcloud/beta/netapp/active-directories/list
index 28d754a69..7fae7bd2a 100644
--- a/gcloud/beta/netapp/active-directories/list
+++ b/gcloud/beta/netapp/active-directories/list
@@ -79,8 +79,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp active-directories list
 
         $ gcloud alpha netapp active-directories list
 
diff --git a/gcloud/beta/netapp/active-directories/update b/gcloud/beta/netapp/active-directories/update
index 0d28d5a1c..bff50c323 100644
--- a/gcloud/beta/netapp/active-directories/update
+++ b/gcloud/beta/netapp/active-directories/update
@@ -166,8 +166,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp active-directories update
 
         $ gcloud alpha netapp active-directories update
 
diff --git a/gcloud/beta/netapp/help b/gcloud/beta/netapp/help
index dfc5f4e38..593eebf8f 100644
--- a/gcloud/beta/netapp/help
+++ b/gcloud/beta/netapp/help
@@ -45,8 +45,10 @@ GROUPS
         (BETA) Create and manage Cloud NetApp Volumes.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp
 
         $ gcloud alpha netapp
 
diff --git a/gcloud/beta/netapp/kms-configs/create b/gcloud/beta/netapp/kms-configs/create
index 08237c389..f33ee46bf 100644
--- a/gcloud/beta/netapp/kms-configs/create
+++ b/gcloud/beta/netapp/kms-configs/create
@@ -125,5 +125,8 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice.
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud netapp kms-configs create
 
diff --git a/gcloud/beta/netapp/kms-configs/delete b/gcloud/beta/netapp/kms-configs/delete
index 1b95e06a8..65fa06a74 100644
--- a/gcloud/beta/netapp/kms-configs/delete
+++ b/gcloud/beta/netapp/kms-configs/delete
@@ -11,7 +11,7 @@ DESCRIPTION
 
 EXAMPLES
     The following command deletes a KMS Config instance named KMS_CONFIG in the
-    default netapp/location
+    default netapp/location.
 
         $ gcloud beta netapp kms-configs delete KMS_CONFIG
 
@@ -68,5 +68,8 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice.
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud netapp kms-configs delete
 
diff --git a/gcloud/beta/netapp/kms-configs/describe b/gcloud/beta/netapp/kms-configs/describe
index e43568f3c..2c6984c73 100644
--- a/gcloud/beta/netapp/kms-configs/describe
+++ b/gcloud/beta/netapp/kms-configs/describe
@@ -7,11 +7,11 @@ SYNOPSIS
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (BETA) Describe a KMS (Key Management System) Config
+    (BETA) Describe a KMS (Key Management System) Config.
 
 EXAMPLES
     The following command gets metadata using describe for a KMS Config
-    instance named KMS_CONFIG in the default netapp/location
+    instance named KMS_CONFIG in the default netapp/location.
 
         $ gcloud beta netapp kms-configs describe KMS_CONFIG
 
@@ -64,5 +64,8 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice.
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud netapp kms-configs describe
 
diff --git a/gcloud/beta/netapp/kms-configs/encrypt b/gcloud/beta/netapp/kms-configs/encrypt
index fa38ef5ad..49a6e0fa5 100644
--- a/gcloud/beta/netapp/kms-configs/encrypt
+++ b/gcloud/beta/netapp/kms-configs/encrypt
@@ -9,7 +9,7 @@ SYNOPSIS
 
 DESCRIPTION
     (BETA) Encrypt the existing volumes with the desired KMS (Key Management
-    System) Config using Customer Managed Encryption Keys (CMEK)
+    System) Config using Customer Managed Encryption Keys (CMEK).
 
 EXAMPLES
     The following command encrypts the existing volumes with the desired KMS
@@ -66,5 +66,8 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice.
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud netapp kms-configs encrypt
 
diff --git a/gcloud/beta/netapp/kms-configs/help b/gcloud/beta/netapp/kms-configs/help
index 432269ba9..14677e7d2 100644
--- a/gcloud/beta/netapp/kms-configs/help
+++ b/gcloud/beta/netapp/kms-configs/help
@@ -39,5 +39,8 @@ COMMANDS
         (BETA) Verify that the Cloud NetApp Volumes KMS Config is reachable.
 
 NOTES
-    This command is currently in beta and might change without notice.
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud netapp kms-configs
 
diff --git a/gcloud/beta/netapp/kms-configs/list b/gcloud/beta/netapp/kms-configs/list
index c741f6db6..f0ef700cb 100644
--- a/gcloud/beta/netapp/kms-configs/list
+++ b/gcloud/beta/netapp/kms-configs/list
@@ -8,7 +8,7 @@ SYNOPSIS
 
 DESCRIPTION
     (BETA) Lists KMS (Key Management System) Configs to encrypt Cloud NetApp
-    Volumes, Storage Pools etc. using Customer Managed Encryption Keys (CMEK)
+    Volumes, Storage Pools etc. using Customer Managed Encryption Keys (CMEK).
 
 EXAMPLES
     The following command lists all KMS Config instance in the default
@@ -84,5 +84,8 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice.
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud netapp kms-configs list
 
diff --git a/gcloud/beta/netapp/kms-configs/update b/gcloud/beta/netapp/kms-configs/update
index 3bf8db95d..89e003386 100644
--- a/gcloud/beta/netapp/kms-configs/update
+++ b/gcloud/beta/netapp/kms-configs/update
@@ -11,11 +11,11 @@ SYNOPSIS
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (BETA) Updates a KMS (Key Management System) Config
+    (BETA) Updates a KMS (Key Management System) Config.
 
 EXAMPLES
     The following command updates a KMS Config instance named KMS_CONFIG with
-    all possible arguments
+    all possible arguments:
 
         $ gcloud beta netapp kms-configs update KMS_CONFIG \
           --location=us-central1 --kms-location=europe-southwest1 \
@@ -151,5 +151,8 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice.
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud netapp kms-configs update
 
diff --git a/gcloud/beta/netapp/kms-configs/verify b/gcloud/beta/netapp/kms-configs/verify
index 7fdf7f2a4..e444f36e3 100644
--- a/gcloud/beta/netapp/kms-configs/verify
+++ b/gcloud/beta/netapp/kms-configs/verify
@@ -8,7 +8,7 @@ SYNOPSIS
 
 DESCRIPTION
     (BETA) Verifies that the Cloud NetApp Volumes KMS (Key Management System)
-    Config is reachable
+    Config is reachable.
 
 EXAMPLES
     The following command verifies that the KMS Config instance named
@@ -60,5 +60,8 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice.
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud netapp kms-configs verify
 
diff --git a/gcloud/beta/netapp/locations/describe b/gcloud/beta/netapp/locations/describe
index 53cda9f44..f69d8fc38 100644
--- a/gcloud/beta/netapp/locations/describe
+++ b/gcloud/beta/netapp/locations/describe
@@ -42,8 +42,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp locations describe
 
         $ gcloud alpha netapp locations describe
 
diff --git a/gcloud/beta/netapp/locations/help b/gcloud/beta/netapp/locations/help
index d97d0f8d5..3e6324cdf 100644
--- a/gcloud/beta/netapp/locations/help
+++ b/gcloud/beta/netapp/locations/help
@@ -23,8 +23,10 @@ COMMANDS
         (BETA) List all Cloud NetApp Files locations.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp locations
 
         $ gcloud alpha netapp locations
 
diff --git a/gcloud/beta/netapp/locations/list b/gcloud/beta/netapp/locations/list
index 3dcd73ece..6552d6a62 100644
--- a/gcloud/beta/netapp/locations/list
+++ b/gcloud/beta/netapp/locations/list
@@ -55,8 +55,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp locations list
 
         $ gcloud alpha netapp locations list
 
diff --git a/gcloud/beta/netapp/operations/describe b/gcloud/beta/netapp/operations/describe
index cd55018ca..d71a9ed18 100644
--- a/gcloud/beta/netapp/operations/describe
+++ b/gcloud/beta/netapp/operations/describe
@@ -57,8 +57,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp operations describe
 
         $ gcloud alpha netapp operations describe
 
diff --git a/gcloud/beta/netapp/operations/help b/gcloud/beta/netapp/operations/help
index 2b0073eb4..5d6d42f05 100644
--- a/gcloud/beta/netapp/operations/help
+++ b/gcloud/beta/netapp/operations/help
@@ -23,8 +23,10 @@ COMMANDS
         (BETA) List Cloud NetApp Files operations.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp operations
 
         $ gcloud alpha netapp operations
 
diff --git a/gcloud/beta/netapp/operations/list b/gcloud/beta/netapp/operations/list
index 2c1817dc4..3c6210b85 100644
--- a/gcloud/beta/netapp/operations/list
+++ b/gcloud/beta/netapp/operations/list
@@ -78,8 +78,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp operations list
 
         $ gcloud alpha netapp operations list
 
diff --git a/gcloud/beta/netapp/storage-pools/create b/gcloud/beta/netapp/storage-pools/create
index 329123b03..17106d6e1 100644
--- a/gcloud/beta/netapp/storage-pools/create
+++ b/gcloud/beta/netapp/storage-pools/create
@@ -169,8 +169,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp storage-pools create
 
         $ gcloud alpha netapp storage-pools create
 
diff --git a/gcloud/beta/netapp/storage-pools/delete b/gcloud/beta/netapp/storage-pools/delete
index 429b71324..66e64edce 100644
--- a/gcloud/beta/netapp/storage-pools/delete
+++ b/gcloud/beta/netapp/storage-pools/delete
@@ -68,8 +68,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp storage-pools delete
 
         $ gcloud alpha netapp storage-pools delete
 
diff --git a/gcloud/beta/netapp/storage-pools/describe b/gcloud/beta/netapp/storage-pools/describe
index fe8d7cbf5..41ba97cd4 100644
--- a/gcloud/beta/netapp/storage-pools/describe
+++ b/gcloud/beta/netapp/storage-pools/describe
@@ -59,8 +59,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp storage-pools describe
 
         $ gcloud alpha netapp storage-pools describe
 
diff --git a/gcloud/beta/netapp/storage-pools/help b/gcloud/beta/netapp/storage-pools/help
index a51ae97aa..3a7d74ca5 100644
--- a/gcloud/beta/netapp/storage-pools/help
+++ b/gcloud/beta/netapp/storage-pools/help
@@ -32,8 +32,10 @@ COMMANDS
         (BETA) Update a Cloud NetApp Storage Pool.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp storage-pools
 
         $ gcloud alpha netapp storage-pools
 
diff --git a/gcloud/beta/netapp/storage-pools/list b/gcloud/beta/netapp/storage-pools/list
index 2023797f6..9ccdd0144 100644
--- a/gcloud/beta/netapp/storage-pools/list
+++ b/gcloud/beta/netapp/storage-pools/list
@@ -78,8 +78,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp storage-pools list
 
         $ gcloud alpha netapp storage-pools list
 
diff --git a/gcloud/beta/netapp/storage-pools/update b/gcloud/beta/netapp/storage-pools/update
index 7dc7beecd..e82ee51c5 100644
--- a/gcloud/beta/netapp/storage-pools/update
+++ b/gcloud/beta/netapp/storage-pools/update
@@ -128,8 +128,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp storage-pools update
 
         $ gcloud alpha netapp storage-pools update
 
diff --git a/gcloud/beta/netapp/volumes/create b/gcloud/beta/netapp/volumes/create
index 81eb6cc46..563f2e433 100644
--- a/gcloud/beta/netapp/volumes/create
+++ b/gcloud/beta/netapp/volumes/create
@@ -234,8 +234,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp volumes create
 
         $ gcloud alpha netapp volumes create
 
diff --git a/gcloud/beta/netapp/volumes/delete b/gcloud/beta/netapp/volumes/delete
index 6cde097ab..fa58b7d82 100644
--- a/gcloud/beta/netapp/volumes/delete
+++ b/gcloud/beta/netapp/volumes/delete
@@ -68,8 +68,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp volumes delete
 
         $ gcloud alpha netapp volumes delete
 
diff --git a/gcloud/beta/netapp/volumes/describe b/gcloud/beta/netapp/volumes/describe
index c9f6ece4e..1ddcd7e1c 100644
--- a/gcloud/beta/netapp/volumes/describe
+++ b/gcloud/beta/netapp/volumes/describe
@@ -55,8 +55,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp volumes describe
 
         $ gcloud alpha netapp volumes describe
 
diff --git a/gcloud/beta/netapp/volumes/help b/gcloud/beta/netapp/volumes/help
index b640f8268..d35e156c1 100644
--- a/gcloud/beta/netapp/volumes/help
+++ b/gcloud/beta/netapp/volumes/help
@@ -43,8 +43,10 @@ COMMANDS
         (BETA) Update a Cloud NetApp Volume.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp volumes
 
         $ gcloud alpha netapp volumes
 
diff --git a/gcloud/beta/netapp/volumes/list b/gcloud/beta/netapp/volumes/list
index 125808dc5..1cf6dca6d 100644
--- a/gcloud/beta/netapp/volumes/list
+++ b/gcloud/beta/netapp/volumes/list
@@ -78,8 +78,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp volumes list
 
         $ gcloud alpha netapp volumes list
 
diff --git a/gcloud/beta/netapp/volumes/replications/create b/gcloud/beta/netapp/volumes/replications/create
index da4da8bc5..6b1c739e4 100644
--- a/gcloud/beta/netapp/volumes/replications/create
+++ b/gcloud/beta/netapp/volumes/replications/create
@@ -13,11 +13,11 @@ SYNOPSIS
         [--volume=VOLUME] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (BETA) Create a Cloud NetApp Volume Replication
+    (BETA) Create a Cloud NetApp Volume Replication.
 
 EXAMPLES
     The following command creates a Replication named NAME using the required
-    arguments
+    arguments:
 
         $ gcloud beta netapp volumes replications create NAME \
           --location=us-central1 --volume=vol1 \
@@ -117,5 +117,8 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice.
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud netapp volumes replications create
 
diff --git a/gcloud/beta/netapp/volumes/replications/delete b/gcloud/beta/netapp/volumes/replications/delete
index dfaec8305..fe2d4e442 100644
--- a/gcloud/beta/netapp/volumes/replications/delete
+++ b/gcloud/beta/netapp/volumes/replications/delete
@@ -8,11 +8,11 @@ SYNOPSIS
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (BETA) Delete a Cloud NetApp Volume Replication
+    (BETA) Delete a Cloud NetApp Volume Replication.
 
 EXAMPLES
     The following command deletes a Replication named NAME using the required
-    arguments
+    arguments:
 
         $ gcloud beta netapp volumes replications delete NAME \
           --location=us-central1 --volume=vol1
@@ -99,5 +99,8 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice.
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud netapp volumes replications delete
 
diff --git a/gcloud/beta/netapp/volumes/replications/describe b/gcloud/beta/netapp/volumes/replications/describe
index 0508b64a4..32a07f4ab 100644
--- a/gcloud/beta/netapp/volumes/replications/describe
+++ b/gcloud/beta/netapp/volumes/replications/describe
@@ -89,5 +89,8 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice.
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud netapp volumes replications describe
 
diff --git a/gcloud/beta/netapp/volumes/replications/help b/gcloud/beta/netapp/volumes/replications/help
index c95055adb..20d1d4233 100644
--- a/gcloud/beta/netapp/volumes/replications/help
+++ b/gcloud/beta/netapp/volumes/replications/help
@@ -41,5 +41,8 @@ COMMANDS
         (BETA) Update a Cloud NetApp Volume Replication.
 
 NOTES
-    This command is currently in beta and might change without notice.
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud netapp volumes replications
 
diff --git a/gcloud/beta/netapp/volumes/replications/list b/gcloud/beta/netapp/volumes/replications/list
index fef5dde1c..2faa99459 100644
--- a/gcloud/beta/netapp/volumes/replications/list
+++ b/gcloud/beta/netapp/volumes/replications/list
@@ -9,11 +9,11 @@ SYNOPSIS
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (BETA) Lists Cloud NetApp Volume Replications
+    (BETA) Lists Cloud NetApp Volume Replications.
 
 EXAMPLES
     The following command lists all Replications in the given location and
-    volume
+    volume:
 
         $ gcloud beta netapp volumes replications list \
           --location=us-central1 --volume=vol1
@@ -105,5 +105,8 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice.
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud netapp volumes replications list
 
diff --git a/gcloud/beta/netapp/volumes/replications/resume b/gcloud/beta/netapp/volumes/replications/resume
index dbf898138..49921f9d6 100644
--- a/gcloud/beta/netapp/volumes/replications/resume
+++ b/gcloud/beta/netapp/volumes/replications/resume
@@ -8,11 +8,11 @@ SYNOPSIS
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (BETA) Resume a Cloud NetApp Volume Replication
+    (BETA) Resume a Cloud NetApp Volume Replication.
 
 EXAMPLES
     The following command resumes a Replication named NAME using the required
-    arguments
+    arguments:
 
         $ gcloud beta netapp volumes replications resume NAME \
           --location=us-central1 --volume=vol1
@@ -99,5 +99,8 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice.
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud netapp volumes replications resume
 
diff --git a/gcloud/beta/netapp/volumes/replications/reverse b/gcloud/beta/netapp/volumes/replications/reverse
index d5f035606..b7654ad9e 100644
--- a/gcloud/beta/netapp/volumes/replications/reverse
+++ b/gcloud/beta/netapp/volumes/replications/reverse
@@ -8,11 +8,11 @@ SYNOPSIS
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (BETA) Reverse a Cloud NetApp Volume Replication
+    (BETA) Reverse a Cloud NetApp Volume Replication.
 
 EXAMPLES
     The following command reverses a Replication named NAME using the required
-    arguments
+    arguments:
 
         $ gcloud beta netapp volumes replications reverse NAME \
           --location=us-central1 --volume=vol1
@@ -99,5 +99,8 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice.
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud netapp volumes replications reverse
 
diff --git a/gcloud/beta/netapp/volumes/replications/stop b/gcloud/beta/netapp/volumes/replications/stop
index 250103918..67125296e 100644
--- a/gcloud/beta/netapp/volumes/replications/stop
+++ b/gcloud/beta/netapp/volumes/replications/stop
@@ -8,11 +8,11 @@ SYNOPSIS
         [--volume=VOLUME] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (BETA) Stop a Cloud NetApp Volume Replication
+    (BETA) Stop a Cloud NetApp Volume Replication.
 
 EXAMPLES
     The following command stops a Replication named NAME using the required
-    arguments
+    arguments:
 
         $ gcloud beta netapp volumes replications stop NAME \
           --location=us-central1 --volume=vol1
@@ -105,5 +105,8 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice.
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud netapp volumes replications stop
 
diff --git a/gcloud/beta/netapp/volumes/replications/update b/gcloud/beta/netapp/volumes/replications/update
index c076c7eef..8a0486c9d 100644
--- a/gcloud/beta/netapp/volumes/replications/update
+++ b/gcloud/beta/netapp/volumes/replications/update
@@ -12,11 +12,11 @@ SYNOPSIS
 
 DESCRIPTION
     (BETA) Update a Cloud NetApp Volume Replication and its specified
-    parameters
+    parameters.
 
 EXAMPLES
     The following command updates a Replication named NAME and its specified
-    parameters
+    parameters:
 
         $ gcloud beta netapp volumes replications update NAME \
           --location=us-central1 --volume=vol1 \
@@ -134,5 +134,8 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice.
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud netapp volumes replications update
 
diff --git a/gcloud/beta/netapp/volumes/revert b/gcloud/beta/netapp/volumes/revert
index ab4b4392b..eb437348a 100644
--- a/gcloud/beta/netapp/volumes/revert
+++ b/gcloud/beta/netapp/volumes/revert
@@ -91,8 +91,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp volumes revert
 
         $ gcloud alpha netapp volumes revert
 
diff --git a/gcloud/beta/netapp/volumes/snapshots/create b/gcloud/beta/netapp/volumes/snapshots/create
index 4d8eac2c4..1ac57a32e 100644
--- a/gcloud/beta/netapp/volumes/snapshots/create
+++ b/gcloud/beta/netapp/volumes/snapshots/create
@@ -8,11 +8,11 @@ SYNOPSIS
         [--labels=[KEY=VALUE,...]] [--volume=VOLUME] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (BETA) Create a Cloud NetApp Volume Snapshot
+    (BETA) Create a Cloud NetApp Volume Snapshot.
 
 EXAMPLES
     The following command creates a Snapshot named NAME using the required
-    arguments
+    arguments:
 
         $ gcloud beta netapp volumes snapshots create NAME \
           --location=us-central1 --volume=vol1
@@ -103,8 +103,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp volumes snapshots create
 
         $ gcloud alpha netapp volumes snapshots create
 
diff --git a/gcloud/beta/netapp/volumes/snapshots/delete b/gcloud/beta/netapp/volumes/snapshots/delete
index e1bf228df..43a1e5c03 100644
--- a/gcloud/beta/netapp/volumes/snapshots/delete
+++ b/gcloud/beta/netapp/volumes/snapshots/delete
@@ -8,11 +8,11 @@ SYNOPSIS
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (BETA) Delete a Cloud NetApp Volume Snapshot
+    (BETA) Delete a Cloud NetApp Volume Snapshot.
 
 EXAMPLES
     The following command deletes a Snapshot named NAME in the given location
-    and volume
+    and volume:
 
         $ gcloud beta netapp volumes snapshots delete NAME \
           --location=us-central1 --volume=vol1
@@ -97,8 +97,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp volumes snapshots delete
 
         $ gcloud alpha netapp volumes snapshots delete
 
diff --git a/gcloud/beta/netapp/volumes/snapshots/describe b/gcloud/beta/netapp/volumes/snapshots/describe
index 7baf28c14..91e9d0b58 100644
--- a/gcloud/beta/netapp/volumes/snapshots/describe
+++ b/gcloud/beta/netapp/volumes/snapshots/describe
@@ -8,11 +8,11 @@ SYNOPSIS
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (BETA) Describe a Cloud NetApp Volume Snapshot
+    (BETA) Describe a Cloud NetApp Volume Snapshot.
 
 EXAMPLES
     The following command describes a Snapshot named NAME in the given location
-    and volume
+    and volume:
 
         $ gcloud beta netapp volumes snapshots describe NAME \
           --location=us-central1 --volume=vol1
@@ -88,8 +88,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp volumes snapshots describe
 
         $ gcloud alpha netapp volumes snapshots describe
 
diff --git a/gcloud/beta/netapp/volumes/snapshots/help b/gcloud/beta/netapp/volumes/snapshots/help
index 68b8791c4..5ab332227 100644
--- a/gcloud/beta/netapp/volumes/snapshots/help
+++ b/gcloud/beta/netapp/volumes/snapshots/help
@@ -32,8 +32,10 @@ COMMANDS
         (BETA) Update a Cloud NetApp Volume Snapshot.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp volumes snapshots
 
         $ gcloud alpha netapp volumes snapshots
 
diff --git a/gcloud/beta/netapp/volumes/snapshots/list b/gcloud/beta/netapp/volumes/snapshots/list
index 23ef8d1f3..6254e2838 100644
--- a/gcloud/beta/netapp/volumes/snapshots/list
+++ b/gcloud/beta/netapp/volumes/snapshots/list
@@ -9,10 +9,10 @@ SYNOPSIS
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (BETA) Lists Cloud NetApp Volume Snapshots
+    (BETA) Lists Cloud NetApp Volume Snapshots.
 
 EXAMPLES
-    The following command lists all Snapshots in the given location and volume
+    The following command lists all Snapshots in the given location and volume:
 
         $ gcloud beta netapp volumes snapshots list --location=us-central1 \
           --volume=vol1
@@ -104,8 +104,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp volumes snapshots list
 
         $ gcloud alpha netapp volumes snapshots list
 
diff --git a/gcloud/beta/netapp/volumes/snapshots/update b/gcloud/beta/netapp/volumes/snapshots/update
index 692cc1c3f..47e26a503 100644
--- a/gcloud/beta/netapp/volumes/snapshots/update
+++ b/gcloud/beta/netapp/volumes/snapshots/update
@@ -9,11 +9,11 @@ SYNOPSIS
         [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    (BETA) Update a Cloud NetApp Volume Snapshot and its specified parameters
+    (BETA) Update a Cloud NetApp Volume Snapshot and its specified parameters.
 
 EXAMPLES
     The following command updates a Snapshot named NAME and its specified
-    parameters
+    parameters:
 
         $ gcloud beta netapp volumes snapshots update NAME \
           --location=us-central1 --description="new" \
@@ -126,8 +126,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp volumes snapshots update
 
         $ gcloud alpha netapp volumes snapshots update
 
diff --git a/gcloud/beta/netapp/volumes/update b/gcloud/beta/netapp/volumes/update
index f646b9f43..37d2caa66 100644
--- a/gcloud/beta/netapp/volumes/update
+++ b/gcloud/beta/netapp/volumes/update
@@ -244,8 +244,10 @@ GCLOUD WIDE FLAGS
     Run $ gcloud help for details.
 
 NOTES
-    This command is currently in beta and might change without notice. This
-    variant is also available:
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud netapp volumes update
 
         $ gcloud alpha netapp volumes update
 
diff --git a/gcloud/beta/network-management/connectivity-tests/create b/gcloud/beta/network-management/connectivity-tests/create
index c57c599ad..e6079abf0 100644
--- a/gcloud/beta/network-management/connectivity-tests/create
+++ b/gcloud/beta/network-management/connectivity-tests/create
@@ -18,7 +18,7 @@ SYNOPSIS
           --source-ip-address=SOURCE_IP_ADDRESS) [--async]
         [--description=DESCRIPTION] [--destination-network=DESTINATION_NETWORK]
         [--destination-port=DESTINATION_PORT]
-        [--destination-project=DESTINATION_PROJECT] [--labels=KEY=VALUE]
+        [--destination-project=DESTINATION_PROJECT] [--labels=[KEY=VALUE,...]]
         [--other-projects=[OTHER_PROJECTS,...]] [--protocol=PROTOCOL]
         [--source-network=SOURCE_NETWORK]
         [--source-network-type=SOURCE_NETWORK_TYPE; default="gcp-network"]
@@ -120,7 +120,7 @@ OPTIONAL FLAGS
      --destination-project=DESTINATION_PROJECT
         Project ID of the destination endpoint.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
      --other-projects=[OTHER_PROJECTS,...]
diff --git a/gcloud/beta/network-management/connectivity-tests/update b/gcloud/beta/network-management/connectivity-tests/update
index 72d36b292..016606855 100644
--- a/gcloud/beta/network-management/connectivity-tests/update
+++ b/gcloud/beta/network-management/connectivity-tests/update
@@ -7,7 +7,7 @@ SYNOPSIS
         [--async] [--description=DESCRIPTION]
         [--destination-network=DESTINATION_NETWORK]
         [--destination-port=DESTINATION_PORT]
-        [--destination-project=DESTINATION_PROJECT] [--labels=KEY=VALUE]
+        [--destination-project=DESTINATION_PROJECT] [--labels=[KEY=VALUE,...]]
         [--other-projects=[OTHER_PROJECTS,...]] [--protocol=PROTOCOL]
         [--source-network=SOURCE_NETWORK]
         [--source-network-type=SOURCE_NETWORK_TYPE; default="gcp-network"]
@@ -85,7 +85,7 @@ FLAGS
      --destination-project=DESTINATION_PROJECT
         Project ID of the destination endpoint.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
      --other-projects=[OTHER_PROJECTS,...]
diff --git a/gcloud/beta/network-security/address-groups/create b/gcloud/beta/network-security/address-groups/create
index cf899e7ab..fcc2156d5 100644
--- a/gcloud/beta/network-security/address-groups/create
+++ b/gcloud/beta/network-security/address-groups/create
@@ -6,7 +6,7 @@ SYNOPSIS
     gcloud beta network-security address-groups create
         (ADDRESS_GROUP : --location=LOCATION) --capacity=CAPACITY --type=TYPE
         [--async] [--description=DESCRIPTION] [--items=[ITEMS,...]]
-        [--labels=KEY=VALUE] [GCLOUD_WIDE_FLAG ...]
+        [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (BETA) Create a new address group with the given name.
@@ -69,7 +69,7 @@ OPTIONAL FLAGS
      --items=[ITEMS,...]
         Items of the address group.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
 GCLOUD WIDE FLAGS
diff --git a/gcloud/beta/network-security/org-address-groups/create b/gcloud/beta/network-security/org-address-groups/create
index 42490a590..df99291c9 100644
--- a/gcloud/beta/network-security/org-address-groups/create
+++ b/gcloud/beta/network-security/org-address-groups/create
@@ -6,7 +6,7 @@ SYNOPSIS
     gcloud beta network-security org-address-groups create
         (ADDRESS_GROUP : --location=LOCATION --organization=ORGANIZATION)
         --capacity=CAPACITY --type=TYPE [--async] [--description=DESCRIPTION]
-        [--items=[ITEMS,...]] [--labels=KEY=VALUE] [GCLOUD_WIDE_FLAG ...]
+        [--items=[ITEMS,...]] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (BETA) Create a new address group with the given name.
@@ -70,7 +70,7 @@ OPTIONAL FLAGS
      --items=[ITEMS,...]
         Items of the address group.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
 GCLOUD WIDE FLAGS
diff --git a/gcloud/beta/recommender/recommendations/list b/gcloud/beta/recommender/recommendations/list
index b86f43873..916cb92bc 100644
--- a/gcloud/beta/recommender/recommendations/list
+++ b/gcloud/beta/recommender/recommendations/list
@@ -48,10 +48,10 @@ REQUIRED FLAGS
 
 FLAGS
      --recommender=RECOMMENDER
-        Recommender to list recommendations for. Supported recommenders can be
-        found here: https://cloud.google.com/recommender/docs/recommenders. For
-        alpha and beta users: If no recommender is specified, recommendations
-        for all supported recommenders are listed.
+        Recommender to list recommendations for. If no recommender is
+        specified, recommendations for all supported recommenders is listed.
+        Supported recommenders can be found here:
+        https://cloud.google.com/recommender/docs/recommenders
 
 LIST COMMAND FLAGS
      --filter=EXPRESSION
diff --git a/gcloud/beta/redis/instances/create b/gcloud/beta/redis/instances/create
index 258e11d9d..3beb2d7b5 100644
--- a/gcloud/beta/redis/instances/create
+++ b/gcloud/beta/redis/instances/create
@@ -14,10 +14,10 @@ SYNOPSIS
         [--persistence-mode=PERSISTENCE_MODE]
         [--rdb-snapshot-period=RDB_SNAPSHOT_PERIOD]
         [--rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME]
-        [--read-replicas-mode=READ_REPLICAS_MODE] [--redis-config=KEY=VALUE]
-        [--redis-version=VERSION] [--replica-count=REPLICA_COUNT]
-        [--reserved-ip-range=RESERVED_IP_RANGE] [--size=SIZE; default=1]
-        [--tier=TIER; default="basic"]
+        [--read-replicas-mode=READ_REPLICAS_MODE]
+        [--redis-config=[KEY=VALUE,...]] [--redis-version=VERSION]
+        [--replica-count=REPLICA_COUNT] [--reserved-ip-range=RESERVED_IP_RANGE]
+        [--size=SIZE; default=1] [--tier=TIER; default="basic"]
         [--transit-encryption-mode=TRANSIT_ENCRYPTION_MODE] [--zone=ZONE]
         [GCLOUD_WIDE_FLAG ...]
 
@@ -157,7 +157,7 @@ FLAGS
             provided and the instance can scale up and down the number of
             replicas.
 
-     --redis-config=KEY=VALUE
+     --redis-config=[KEY=VALUE,...]
         A list of Redis config KEY=VALUE pairs to set on the instance according
         to http://redis.io/topics/config. Currently, the only supported
         parameters are:
diff --git a/gcloud/beta/run/jobs/executions/cancel b/gcloud/beta/run/jobs/executions/cancel
new file mode 100644
index 000000000..bfb61bb3d
--- /dev/null
+++ b/gcloud/beta/run/jobs/executions/cancel
@@ -0,0 +1,58 @@
+NAME
+    gcloud beta run jobs executions cancel - cancel an execution
+
+SYNOPSIS
+    gcloud beta run jobs executions cancel EXECUTION [--[no-]async]
+        [--region=REGION] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Cancel an execution.
+
+EXAMPLES
+    To cancel an execution:
+
+        $ gcloud beta run jobs executions cancel my-execution
+
+POSITIONAL ARGUMENTS
+     Execution resource - Execution to cancel. This represents a Cloud
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument EXECUTION on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       EXECUTION
+          ID of the Execution or fully qualified identifier for the Execution.
+
+          To set the executions attribute:
+          ▸ provide the argument EXECUTION on the command line.
+
+FLAGS
+     --[no-]async
+        Return immediately, without waiting for the operation in progress to
+        complete. Defaults to --no-async. Use --async to enable and --no-async
+        to disable.
+
+     --region=REGION
+        Region in which the resource can be found. Alternatively, set the
+        property [run/region].
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud alpha run jobs executions cancel
+
diff --git a/gcloud/beta/run/jobs/executions/help b/gcloud/beta/run/jobs/executions/help
index 15aad0d6f..95095cdd2 100644
--- a/gcloud/beta/run/jobs/executions/help
+++ b/gcloud/beta/run/jobs/executions/help
@@ -37,6 +37,9 @@ GROUPS
 COMMANDS
     COMMAND is one of the following:
 
+     cancel
+        (BETA) Cancel an execution.
+
      delete
         (BETA) Delete an execution.
 
diff --git a/gcloud/beta/scc/assets/update-marks b/gcloud/beta/scc/assets/update-marks
index 7b8f3030d..542f3532a 100644
--- a/gcloud/beta/scc/assets/update-marks
+++ b/gcloud/beta/scc/assets/update-marks
@@ -4,7 +4,7 @@ NAME
 
 SYNOPSIS
     gcloud beta scc assets update-marks (ASSET : --organization=ORGANIZATION)
-        [--security-marks=[SECURITY_MARKS,...]] [--start-time=START_TIME]
+        [--security-marks=[KEY=VALUE,...]] [--start-time=START_TIME]
         [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -73,7 +73,7 @@ POSITIONAL ARGUMENTS
             line..
 
 FLAGS
-     --security-marks=[SECURITY_MARKS,...]
+     --security-marks=[KEY=VALUE,...]
         SecurityMarks resource to be passed as the request body. It's a
         key=value pair separated by comma (,). For example:
         --security-marks="key1=val1,key2=val2".
diff --git a/gcloud/beta/scc/findings/create b/gcloud/beta/scc/findings/create
index ac620b4e1..22b077273 100644
--- a/gcloud/beta/scc/findings/create
+++ b/gcloud/beta/scc/findings/create
@@ -7,7 +7,7 @@ SYNOPSIS
         (FINDING : --organization=ORGANIZATION --source=SOURCE)
         --category=CATEGORY --event-time=EVENT_TIME
         --resource-name=RESOURCE_NAME [--external-uri=EXTERNAL_URI]
-        [--source-properties=[SOURCE_PROPERTIES,...]] [--state=STATE]
+        [--source-properties=[KEY=VALUE,...]] [--state=STATE]
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -108,7 +108,7 @@ OPTIONAL FLAGS
         finding can be found. This field is guaranteed to be either empty or a
         well formed URL.
 
-     --source-properties=[SOURCE_PROPERTIES,...]
+     --source-properties=[KEY=VALUE,...]
         Source specific properties. These properties are managed by the source
         that writes the finding. The key names in the source_properties map
         must be between 1 and 255 characters, and must start with a letter and
diff --git a/gcloud/beta/scc/findings/update b/gcloud/beta/scc/findings/update
index 02ea57c64..dec2053b1 100644
--- a/gcloud/beta/scc/findings/update
+++ b/gcloud/beta/scc/findings/update
@@ -6,7 +6,7 @@ SYNOPSIS
     gcloud beta scc findings update
         (FINDING : --organization=ORGANIZATION --source=SOURCE)
         [--event-time=EVENT_TIME] [--external-uri=EXTERNAL_URI]
-        [--source-properties=[SOURCE_PROPERTIES,...]] [--state=STATE]
+        [--source-properties=[KEY=VALUE,...]] [--state=STATE]
         [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -98,7 +98,7 @@ FLAGS
         finding can be found. This field is guaranteed to be either empty or a
         well formed URL.
 
-     --source-properties=[SOURCE_PROPERTIES,...]
+     --source-properties=[KEY=VALUE,...]
         Source specific properties. These properties are managed by the source
         that writes the finding. The key names in the source_properties map
         must be between 1 and 255 characters, and must start with a letter and
diff --git a/gcloud/beta/scc/findings/update-marks b/gcloud/beta/scc/findings/update-marks
index c07e2aa64..3040fc7fd 100644
--- a/gcloud/beta/scc/findings/update-marks
+++ b/gcloud/beta/scc/findings/update-marks
@@ -5,7 +5,7 @@ NAME
 SYNOPSIS
     gcloud beta scc findings update-marks
         (FINDING : --organization=ORGANIZATION --source=SOURCE)
-        [--security-marks=[SECURITY_MARKS,...]] [--start-time=START_TIME]
+        [--security-marks=[KEY=VALUE,...]] [--start-time=START_TIME]
         [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -86,7 +86,7 @@ POSITIONAL ARGUMENTS
           ▸ provide the argument --source on the command line.
 
 FLAGS
-     --security-marks=[SECURITY_MARKS,...]
+     --security-marks=[KEY=VALUE,...]
         SecurityMarks resource to be passed as the request body. It's a
         key=value pair separated by comma (,). For example:
         --security-marks="key1=val1,key2=val2".
diff --git a/gcloud/beta/scheduler/jobs/create/app-engine b/gcloud/beta/scheduler/jobs/create/app-engine
index f36269950..3ed5e8f28 100644
--- a/gcloud/beta/scheduler/jobs/create/app-engine
+++ b/gcloud/beta/scheduler/jobs/create/app-engine
@@ -5,7 +5,7 @@ NAME
 SYNOPSIS
     gcloud beta scheduler jobs create app-engine (JOB : --location=LOCATION)
         --schedule=SCHEDULE [--attempt-deadline=ATTEMPT_DEADLINE]
-        [--description=DESCRIPTION] [--headers=HEADERS]
+        [--description=DESCRIPTION] [--headers=[KEY=VALUE,...]]
         [--http-method=HTTP_METHOD; default="post"]
         [--max-backoff=MAX_BACKOFF; default="1h"]
         [--max-doublings=MAX_DOUBLINGS; default=16]
@@ -91,7 +91,7 @@ OPTIONAL FLAGS
      --description=DESCRIPTION
         Human-readable description of the job.
 
-     --headers=HEADERS
+     --headers=[KEY=VALUE,...]
         KEY=VALUE pairs of HTTP headers to include in the request. Cannot be
         repeated. For example: --headers
         Accept-Language=en-us,Accept=text/plain
diff --git a/gcloud/beta/scheduler/jobs/create/http b/gcloud/beta/scheduler/jobs/create/http
index 0ab9c925d..3f0e7edf0 100644
--- a/gcloud/beta/scheduler/jobs/create/http
+++ b/gcloud/beta/scheduler/jobs/create/http
@@ -5,7 +5,7 @@ NAME
 SYNOPSIS
     gcloud beta scheduler jobs create http (JOB : --location=LOCATION)
         --schedule=SCHEDULE --uri=URI [--attempt-deadline=ATTEMPT_DEADLINE]
-        [--description=DESCRIPTION] [--headers=HEADERS]
+        [--description=DESCRIPTION] [--headers=[KEY=VALUE,...]]
         [--http-method=HTTP_METHOD; default="post"]
         [--max-backoff=MAX_BACKOFF; default="1h"]
         [--max-doublings=MAX_DOUBLINGS; default=16]
@@ -101,7 +101,7 @@ OPTIONAL FLAGS
      --description=DESCRIPTION
         Human-readable description of the job.
 
-     --headers=HEADERS
+     --headers=[KEY=VALUE,...]
         KEY=VALUE pairs of HTTP headers to include in the request. Cannot be
         repeated. For example: --headers
         Accept-Language=en-us,Accept=text/plain
diff --git a/gcloud/beta/scheduler/jobs/update/app-engine b/gcloud/beta/scheduler/jobs/update/app-engine
index cd2bb4e4e..28646f2c3 100644
--- a/gcloud/beta/scheduler/jobs/update/app-engine
+++ b/gcloud/beta/scheduler/jobs/update/app-engine
@@ -8,7 +8,7 @@ SYNOPSIS
         [--http-method=HTTP_METHOD; default="post"] [--schedule=SCHEDULE]
         [--version=VERSION]
         [--clear-headers | --remove-headers=[REMOVE_HEADERS,...]
-          --update-headers=[UPDATE_HEADERS,...]]
+          --update-headers=[KEY=VALUE,...]]
         [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="1h"]
         [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=16]
         [--clear-max-retry-attempts | --max-retry-attempts=MAX_RETRY_ATTEMPTS]
@@ -108,7 +108,7 @@ FLAGS
           KEY1,KEY2 list of HTTP headers to remove from the request.
           --remove-headers Accept-Language,Accept
 
-       --update-headers=[UPDATE_HEADERS,...]
+       --update-headers=[KEY=VALUE,...]
           KEY=VALUE pairs of HTTP headers to include in the request. Cannot be
           repeated. For example: --update-headers
           Accept-Language=en-us,Accept=text/plain
diff --git a/gcloud/beta/scheduler/jobs/update/http b/gcloud/beta/scheduler/jobs/update/http
index e8201f551..348615aaf 100644
--- a/gcloud/beta/scheduler/jobs/update/http
+++ b/gcloud/beta/scheduler/jobs/update/http
@@ -13,7 +13,7 @@ SYNOPSIS
           | [--oidc-service-account-email=OIDC_SERVICE_ACCOUNT_EMAIL
           : --oidc-token-audience=OIDC_TOKEN_AUDIENCE]]
         [--clear-headers | --remove-headers=[REMOVE_HEADERS,...]
-          --update-headers=[UPDATE_HEADERS,...]]
+          --update-headers=[KEY=VALUE,...]]
         [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="1h"]
         [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=16]
         [--clear-max-retry-attempts | --max-retry-attempts=MAX_RETRY_ATTEMPTS]
@@ -163,7 +163,7 @@ FLAGS
           KEY1,KEY2 list of HTTP headers to remove from the request.
           --remove-headers Accept-Language,Accept
 
-       --update-headers=[UPDATE_HEADERS,...]
+       --update-headers=[KEY=VALUE,...]
           KEY=VALUE pairs of HTTP headers to include in the request. Cannot be
           repeated. For example: --update-headers
           Accept-Language=en-us,Accept=text/plain
diff --git a/gcloud/beta/scheduler/jobs/update/pubsub b/gcloud/beta/scheduler/jobs/update/pubsub
index fc85e9ab2..e41bf665a 100644
--- a/gcloud/beta/scheduler/jobs/update/pubsub
+++ b/gcloud/beta/scheduler/jobs/update/pubsub
@@ -6,7 +6,7 @@ SYNOPSIS
     gcloud beta scheduler jobs update pubsub (JOB : --location=LOCATION)
         [--description=DESCRIPTION] [--schedule=SCHEDULE] [--topic=TOPIC]
         [--clear-attributes | --remove-attributes=[REMOVE_ATTRIBUTES,...]
-          --update-attributes=[UPDATE_ATTRIBUTES,...]]
+          --update-attributes=[KEY=VALUE,...]]
         [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="1h"]
         [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=16]
         [--clear-max-retry-attempts | --max-retry-attempts=MAX_RETRY_ATTEMPTS]
@@ -95,7 +95,7 @@ FLAGS
           Comma-separated list of attribute keys to remove with the form
           "KEY1,KEY2".
 
-       --update-attributes=[UPDATE_ATTRIBUTES,...]
+       --update-attributes=[KEY=VALUE,...]
           Comma-separated list of attributes. Each attribute has the form
           "NAME=VALUE". You can specify up to 100 attributes.
 
diff --git a/gcloud/beta/workstations/clusters/create b/gcloud/beta/workstations/clusters/create
index 86188a4a9..a71ea7931 100644
--- a/gcloud/beta/workstations/clusters/create
+++ b/gcloud/beta/workstations/clusters/create
@@ -3,7 +3,7 @@ NAME
 
 SYNOPSIS
     gcloud beta workstations clusters create (CLUSTER : --region=REGION)
-        [--async] [--enable-private-endpoint] [--labels=[LABELS,...]]
+        [--async] [--enable-private-endpoint] [--labels=[KEY=VALUE,...]]
         [--network=NETWORK] [--subnetwork=SUBNETWORK] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -64,7 +64,7 @@ FLAGS
         workstations from public networks, but requires additional
         configuration. Learn more: https://cloud.google.com/workstations/docs.
 
-     --labels=[LABELS,...]
+     --labels=[KEY=VALUE,...]
         Labels that are applied to the cluster and propagated to the underlying
         Compute Engine resources.
 
diff --git a/gcloud/beta/workstations/create b/gcloud/beta/workstations/create
index aed15fde0..6e3cc6ce4 100644
--- a/gcloud/beta/workstations/create
+++ b/gcloud/beta/workstations/create
@@ -4,7 +4,7 @@ NAME
 SYNOPSIS
     gcloud beta workstations create
         (WORKSTATION : --cluster=CLUSTER --config=CONFIG --region=REGION)
-        [--async] [--labels=[LABELS,...]] [GCLOUD_WIDE_FLAG ...]
+        [--async] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (BETA) Create a workstation.
@@ -67,7 +67,7 @@ FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
-     --labels=[LABELS,...]
+     --labels=[KEY=VALUE,...]
         Labels that are applied to the workstation and propagated to the
         underlying Compute Engine resources.
 
diff --git a/gcloud/billing/accounts/add-iam-policy-binding b/gcloud/billing/accounts/add-iam-policy-binding
new file mode 100644
index 000000000..b06ae674b
--- /dev/null
+++ b/gcloud/billing/accounts/add-iam-policy-binding
@@ -0,0 +1,72 @@
+NAME
+    gcloud billing accounts add-iam-policy-binding - add an IAM policy binding
+        to a Cloud Billing account
+
+SYNOPSIS
+    gcloud billing accounts add-iam-policy-binding ACCOUNT --member=PRINCIPAL
+        --role=ROLE [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Add an IAM policy binding to the IAM policy of a Cloud Billing account. A
+    binding consists of a member and a role.
+
+EXAMPLES
+    To add someone@example.com as a Billing Account Administrator for billing
+    account 123456-789876-543210, run:
+
+        $ gcloud billing accounts add-iam-policy-binding \
+            123456-789876-543210 --member='user:someone@example.com' \
+            --role='roles/billing.admin'
+
+POSITIONAL ARGUMENTS
+     Account resource - Name of the Cloud Billing account for which to add the
+     IAM policy binding. This represents a Cloud resource.
+
+     This must be specified.
+
+       ACCOUNT
+          ID of the account or fully qualified identifier for the account.
+
+          To set the account attribute:
+          ▸ provide the argument account on the command line.
+
+REQUIRED FLAGS
+     --member=PRINCIPAL
+        The principal to add the binding for. Should be of the form
+        user|group|serviceAccount:email or domain:domain.
+
+        Examples: user:test-user@gmail.com, group:admins@example.com,
+        serviceAccount:test123@example.domain.com, or
+        domain:example.domain.com.
+
+        Some resources also accept the following special values:
+        ◆ allUsers - Special identifier that represents anyone who is on the
+          internet, with or without a Google account.
+        ◆ allAuthenticatedUsers - Special identifier that represents anyone
+          who is authenticated with a Google account or a service account.
+
+     --role=ROLE
+        Role name to assign to the principal. The role name is the complete
+        path of a predefined role, such as roles/logging.viewer, or the role ID
+        for a custom role, such as
+        organizations/{ORGANIZATION_ID}/roles/logging.viewer.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the cloudbilling/v1 API. The full documentation for this
+    API can be found at: https://cloud.google.com/billing/docs/apis
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha billing accounts add-iam-policy-binding
+
+        $ gcloud beta billing accounts add-iam-policy-binding
+
diff --git a/gcloud/billing/accounts/describe b/gcloud/billing/accounts/describe
new file mode 100644
index 000000000..be03fda23
--- /dev/null
+++ b/gcloud/billing/accounts/describe
@@ -0,0 +1,44 @@
+NAME
+    gcloud billing accounts describe - show metadata for a billing account
+
+SYNOPSIS
+    gcloud billing accounts describe ACCOUNT_ID [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command shows info for a billing account, given its ID.
+
+    This call can fail for the following reasons:
+
+      ▪ The account specified does not exist.
+      ▪ The active user does not have permission to access the given account.
+
+EXAMPLES
+    To see details for billing account 0X0X0X-0X0X0X-0X0X0X, run:
+
+        $ gcloud billing accounts describe 0X0X0X-0X0X0X-0X0X0X
+
+POSITIONAL ARGUMENTS
+     ACCOUNT_ID
+        Specify a billing account ID. Billing account IDs are of the form
+        0X0X0X-0X0X0X-0X0X0X. To see available IDs, run $ gcloud billing
+        accounts list.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the cloudbilling/v1 API. The full documentation for this
+    API can be found at: https://cloud.google.com/billing/v1/getting-started
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha billing accounts describe
+
+        $ gcloud beta billing accounts describe
+
diff --git a/gcloud/billing/accounts/get-iam-policy b/gcloud/billing/accounts/get-iam-policy
new file mode 100644
index 000000000..6f74a9008
--- /dev/null
+++ b/gcloud/billing/accounts/get-iam-policy
@@ -0,0 +1,79 @@
+NAME
+    gcloud billing accounts get-iam-policy - get the IAM policy for a Cloud
+        Billing account
+
+SYNOPSIS
+    gcloud billing accounts get-iam-policy ACCOUNT [--filter=EXPRESSION]
+        [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    gcloud billing accounts get-iam-policy displays the IAM policy associated
+    with a Cloud Billing account. If formatted as JSON, the output can be
+    edited and used as a policy file for set-iam-policy. The output includes an
+    "etag" field identifying the version emitted and allowing detection of
+    concurrent policy updates; see $ {parent} set-iam-policy for additional
+    details.
+
+EXAMPLES
+    To print the IAM policy for a given Cloud Billing account, run:
+
+        $ gcloud billing accounts get-iam-policy my-account
+
+POSITIONAL ARGUMENTS
+     Account resource - The Cloud Billing account for which to display the IAM
+     policy. This represents a Cloud resource.
+
+     This must be specified.
+
+       ACCOUNT
+          ID of the account or fully qualified identifier for the account.
+
+          To set the account attribute:
+          ▸ provide the argument account on the command line.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the cloudbilling/v1 API. The full documentation for this
+    API can be found at: https://cloud.google.com/billing/docs/apis
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha billing accounts get-iam-policy
+
+        $ gcloud beta billing accounts get-iam-policy
+
diff --git a/gcloud/billing/accounts/help b/gcloud/billing/accounts/help
new file mode 100644
index 000000000..a890f8d8e
--- /dev/null
+++ b/gcloud/billing/accounts/help
@@ -0,0 +1,42 @@
+NAME
+    gcloud billing accounts - manage billing accounts
+
+SYNOPSIS
+    gcloud billing accounts COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Manage billing accounts.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     add-iam-policy-binding
+        Add an IAM policy binding to a Cloud Billing account.
+
+     describe
+        Show metadata for a billing account.
+
+     get-iam-policy
+        Get the IAM policy for a Cloud Billing account.
+
+     list
+        List all active billing accounts.
+
+     remove-iam-policy-binding
+        Remove an IAM policy binding from a Cloud Billing account.
+
+     set-iam-policy
+        Set the IAM policy for a Cloud Billing account.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha billing accounts
+
+        $ gcloud beta billing accounts
+
diff --git a/gcloud/billing/accounts/list b/gcloud/billing/accounts/list
new file mode 100644
index 000000000..f714e5ec8
--- /dev/null
+++ b/gcloud/billing/accounts/list
@@ -0,0 +1,69 @@
+NAME
+    gcloud billing accounts list - list all active billing accounts
+
+SYNOPSIS
+    gcloud billing accounts list [--filter=EXPRESSION] [--limit=LIMIT]
+        [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    gcloud billing accounts list lists all billing accounts and subaccounts
+    owned by the currently authenticated user. Subaccounts have a non-empty
+    MASTER_ACCOUNT_ID value.
+
+EXAMPLES
+    To list only open billing accounts, run:
+
+        $ gcloud billing accounts list --filter=open=true
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the cloudbilling/v1 API. The full documentation for this
+    API can be found at: https://cloud.google.com/billing/v1/getting-started
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha billing accounts list
+
+        $ gcloud beta billing accounts list
+
diff --git a/gcloud/billing/accounts/remove-iam-policy-binding b/gcloud/billing/accounts/remove-iam-policy-binding
new file mode 100644
index 000000000..b4b1647fe
--- /dev/null
+++ b/gcloud/billing/accounts/remove-iam-policy-binding
@@ -0,0 +1,73 @@
+NAME
+    gcloud billing accounts remove-iam-policy-binding - remove an IAM policy
+        binding from a Cloud Billing account
+
+SYNOPSIS
+    gcloud billing accounts remove-iam-policy-binding ACCOUNT
+        --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Remove an IAM policy binding to the IAM policy from a Cloud Billing
+    account. A binding consists of a member and a role.
+
+EXAMPLES
+    To remove someone@example.com as a Billing Account Administrator from
+    billing account 123456-789876-543210, run:
+
+        $ gcloud billing accounts remove-iam-policy-binding \
+            123456-789876-543210 --member='user:someone@example.com' \
+            --role='roles/billing.admin'
+
+POSITIONAL ARGUMENTS
+     Account resource - Name of the Cloud Billing account for which to remove
+     the IAM policy binding. This represents a Cloud resource.
+
+     This must be specified.
+
+       ACCOUNT
+          ID of the account or fully qualified identifier for the account.
+
+          To set the account attribute:
+          ▸ provide the argument account on the command line.
+
+REQUIRED FLAGS
+     --member=PRINCIPAL
+        The principal to remove the binding for. Should be of the form
+        user|group|serviceAccount:email or domain:domain.
+
+        Examples: user:test-user@gmail.com, group:admins@example.com,
+        serviceAccount:test123@example.domain.com, or
+        domain:example.domain.com.
+
+        Deleted principals have an additional deleted: prefix and a ?uid=UID
+        suffix, where UID is a unique identifier for the principal. Example:
+        deleted:user:test-user@gmail.com?uid=123456789012345678901.
+
+        Some resources also accept the following special values:
+        ◆ allUsers - Special identifier that represents anyone who is on the
+          internet, with or without a Google account.
+        ◆ allAuthenticatedUsers - Special identifier that represents anyone
+          who is authenticated with a Google account or a service account.
+
+     --role=ROLE
+        The role to remove the principal from.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the cloudbilling/v1 API. The full documentation for this
+    API can be found at: https://cloud.google.com/billing/docs/apis
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha billing accounts remove-iam-policy-binding
+
+        $ gcloud beta billing accounts remove-iam-policy-binding
+
diff --git a/gcloud/billing/accounts/set-iam-policy b/gcloud/billing/accounts/set-iam-policy
new file mode 100644
index 000000000..536b04a61
--- /dev/null
+++ b/gcloud/billing/accounts/set-iam-policy
@@ -0,0 +1,64 @@
+NAME
+    gcloud billing accounts set-iam-policy - set the IAM policy for a Cloud
+        Billing account
+
+SYNOPSIS
+    gcloud billing accounts set-iam-policy ACCOUNT POLICY_FILE
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    gcloud billing accounts set-iam-policy sets the IAM policy for a Cloud
+    Billing account given an account ID and a JSON or YAML file that describes
+    the IAM policy.
+
+    Note: Setting the IAM policy for a Cloud Billing account replaces existing
+    IAM bindings for that account.
+
+EXAMPLES
+    The following command reads an IAM policy defined in the JSON file
+    policy.json and sets it for a Billing account ID 123456-789876-543210:
+
+        $ gcloud billing accounts set-iam-policy 123456-789876-543210 \
+            policy.json
+
+    See https://cloud.google.com/iam/docs/managing-policies for policy file
+    format and content details.
+
+POSITIONAL ARGUMENTS
+     Account resource - The Cloud Billing account for which to display the IAM
+     policy. This represents a Cloud resource.
+
+     This must be specified.
+
+       ACCOUNT
+          ID of the account or fully qualified identifier for the account.
+
+          To set the account attribute:
+          ▸ provide the argument account on the command line.
+
+     POLICY_FILE
+        Path to a local JSON or YAML formatted file containing a valid policy.
+
+        The output of the get-iam-policy command is a valid file, as is any
+        JSON or YAML file conforming to the structure of a Policy
+        (https://cloud.google.com/iam/reference/rest/v1/Policy).
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the cloudbilling/v1 API. The full documentation for this
+    API can be found at: https://cloud.google.com/billing/docs/apis
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha billing accounts set-iam-policy
+
+        $ gcloud beta billing accounts set-iam-policy
+
diff --git a/gcloud/billing/budgets/create b/gcloud/billing/budgets/create
index 1a5a6a906..ed26b0b07 100644
--- a/gcloud/billing/budgets/create
+++ b/gcloud/billing/budgets/create
@@ -8,14 +8,14 @@ SYNOPSIS
         [--credit-types-treatment=CREDIT_TYPES_TREATMENT]
         [--disable-default-iam-recipients]
         [--filter-credit-types=[FILTER_CREDIT_TYPES,...]]
-        [--filter-labels=FILTER_LABELS]
+        [--filter-labels=[KEY=VALUE,...]]
         [--filter-projects=[FILTER_PROJECTS,...]]
         [--filter-services=[FILTER_SERVICES,...]]
         [--filter-subaccounts=[FILTER_SUBACCOUNTS,...]]
         [--notifications-rule-monitoring-notification-channels=[NOTIFICATIONS_RULE_MONITORING_NOTIFICATION_CHANNELS,
           ...]]
         [--notifications-rule-pubsub-topic=NOTIFICATIONS_RULE_PUBSUB_TOPIC]
-        [--threshold-rule=THRESHOLD_RULE]
+        [--threshold-rule=[basis=BASIS],[percent=PERCENT]]
         [--calendar-period=CALENDAR_PERIOD
           | [--start-date=START_DATE : --end-date=END_DATE]]
         [GCLOUD_WIDE_FLAG ...]
@@ -84,7 +84,7 @@ OPTIONAL FLAGS
         specified, then --credit-types-treatment must be
         include-specified-credits.
 
-     --filter-labels=FILTER_LABELS
+     --filter-labels=[KEY=VALUE,...]
         Single label and value pair specifying that usage from only this set of
         labeled resources should be included in the budget. Currently, multiple
         entries or multiple values per entry are not allowed. If omitted, the
@@ -124,7 +124,7 @@ OPTIONAL FLAGS
         Name of the Cloud Pub/Sub topic where budget related messages will be
         published, in the form projects/{project_id}/topics/{topic_id}.
 
-     --threshold-rule=THRESHOLD_RULE
+     --threshold-rule=[basis=BASIS],[percent=PERCENT]
         Rule that triggers alerts (notifications of thresholds being crossed)
         when spend exceeds the specified percentages of the budget. This flag
         can be repeated to provide multiple thresholds above which an alert is
diff --git a/gcloud/billing/budgets/update b/gcloud/billing/budgets/update
index b0ed557ec..af3bb3780 100644
--- a/gcloud/billing/budgets/update
+++ b/gcloud/billing/budgets/update
@@ -6,7 +6,7 @@ SYNOPSIS
         [--credit-types-treatment=CREDIT_TYPES_TREATMENT]
         [--disable-default-iam-recipients] [--display-name=DISPLAY_NAME]
         [--filter-credit-types=[FILTER_CREDIT_TYPES,...]]
-        [--filter-labels=FILTER_LABELS]
+        [--filter-labels=[KEY=VALUE,...]]
         [--filter-projects=[FILTER_PROJECTS,...]]
         [--filter-services=[FILTER_SERVICES,...]]
         [--filter-subaccounts=[FILTER_SUBACCOUNTS,...]]
@@ -17,8 +17,8 @@ SYNOPSIS
         [--calendar-period=CALENDAR_PERIOD
           | [--start-date=START_DATE : --end-date=END_DATE]]
         [--threshold-rules-from-file=THRESHOLD_RULES_FROM_FILE
-          | --add-threshold-rule=ADD_THRESHOLD_RULE --clear-threshold-rules]
-        [GCLOUD_WIDE_FLAG ...]
+          | --add-threshold-rule=[basis=BASIS],[percent=PERCENT]
+          --clear-threshold-rules] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     Update a budget.
@@ -84,7 +84,7 @@ FLAGS
         specified, then --credit-types-treatment must be
         include-specified-credits.
 
-     --filter-labels=FILTER_LABELS
+     --filter-labels=[KEY=VALUE,...]
         Single label and value pair specifying that usage from only this set of
         labeled resources should be included in the budget. Currently, multiple
         entries or multiple values per entry are not allowed. If omitted, the
@@ -160,7 +160,7 @@ FLAGS
           in the file will replace the rules in the budget. This can be used to
           add or remove specific threshold rules.
 
-       --add-threshold-rule=ADD_THRESHOLD_RULE
+       --add-threshold-rule=[basis=BASIS],[percent=PERCENT]
           Rule that triggers alerts (notifications of thresholds being crossed)
           when spend exceeds the specified percentages of the budget. This flag
           can be repeated to provide multiple thresholds above which an alert
diff --git a/gcloud/billing/help b/gcloud/billing/help
index f72f0f37a..5fa8399b2 100644
--- a/gcloud/billing/help
+++ b/gcloud/billing/help
@@ -10,12 +10,12 @@ DESCRIPTION
 EXAMPLES
     To list billing accounts associated with the current user, run:
 
-        $ gcloud beta billing accounts list
+        $ gcloud billing accounts list
 
     To link one of the billing accounts 0X0X0X-0X0X0X-0X0X0X with a project
     my-project, run:
 
-        $ gcloud beta billing projects link my-project \
+        $ gcloud billing projects link my-project \
             --billing-account 0X0X0X-0X0X0X-0X0X0X
 
 GCLOUD WIDE FLAGS
@@ -26,9 +26,15 @@ GCLOUD WIDE FLAGS
 GROUPS
     GROUP is one of the following:
 
+     accounts
+        Manage billing accounts.
+
      budgets
         Manage the budgets of your billing accounts.
 
+     projects
+        Manage the billing account configuration of your projects.
+
 NOTES
     These variants are also available:
 
diff --git a/gcloud/billing/projects/describe b/gcloud/billing/projects/describe
new file mode 100644
index 000000000..aa5f550b0
--- /dev/null
+++ b/gcloud/billing/projects/describe
@@ -0,0 +1,43 @@
+NAME
+    gcloud billing projects describe - show detailed billing information for a
+        project
+
+SYNOPSIS
+    gcloud billing projects describe PROJECT_ID [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command shows billing info for a project, given its ID.
+
+    This call can fail for the following reasons:
+
+      ▪ The project specified does not exist.
+      ▪ The active user does not have permission to access the given project.
+
+EXAMPLES
+    To see detailed billing information for a project my-project, run:
+
+        $ gcloud billing projects describe my-project
+
+POSITIONAL ARGUMENTS
+     PROJECT_ID
+        Specify a project id.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the cloudbilling/v1 API. The full documentation for this
+    API can be found at: https://cloud.google.com/billing/v1/getting-started
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha billing projects describe
+
+        $ gcloud beta billing projects describe
+
diff --git a/gcloud/billing/projects/help b/gcloud/billing/projects/help
new file mode 100644
index 000000000..cf23c32bf
--- /dev/null
+++ b/gcloud/billing/projects/help
@@ -0,0 +1,37 @@
+NAME
+    gcloud billing projects - manage the billing account configuration of your
+        projects
+
+SYNOPSIS
+    gcloud billing projects COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Manage the billing account configuration of your projects.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     describe
+        Show detailed billing information for a project.
+
+     link
+        Link a project with a billing account.
+
+     list
+        List all active projects associated with the specified billing account.
+
+     unlink
+        Unlink the account (if any) linked with a project.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha billing projects
+
+        $ gcloud beta billing projects
+
diff --git a/gcloud/billing/projects/link b/gcloud/billing/projects/link
new file mode 100644
index 000000000..1b47d3b48
--- /dev/null
+++ b/gcloud/billing/projects/link
@@ -0,0 +1,61 @@
+NAME
+    gcloud billing projects link - link a project with a billing account
+
+SYNOPSIS
+    gcloud billing projects link PROJECT_ID --billing-account=ACCOUNT_ID
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command sets or updates the billing account associated with a project.
+
+    Billing is enabled on a project when the project is linked to a valid,
+    active Cloud Billing account. The billing account accrues charges for the
+    usage of resources in all of the linked projects. If the project is already
+    linked to a billing account, this command moves the project to the billing
+    account you specify, updating the billing account that is linked to the
+    project.
+
+    Note that associating a project with a closed billing account has the same
+    effect as disabling billing on the project: any paid resources in use by
+    the project are shut down, and your application stops functioning. Unless
+    you want to disable billing, you should always specify a valid, active
+    Cloud Billing account when you run this command. Learn how to confirm the
+    status of a Cloud Billing account at
+    https://cloud.google.com/billing/docs/how-to/verify-billing-enabled#billing_account_status
+
+EXAMPLES
+    To link a billing account 0X0X0X-0X0X0X-0X0X0X with a project my-project,
+    run:
+
+        $ gcloud billing projects link my-project \
+            --billing-account=0X0X0X-0X0X0X-0X0X0X
+
+POSITIONAL ARGUMENTS
+     PROJECT_ID
+        Specify a project id.
+
+REQUIRED FLAGS
+     --billing-account=ACCOUNT_ID
+        Specify a billing account ID. Billing account IDs are of the form
+        0X0X0X-0X0X0X-0X0X0X. To see available IDs, run $ gcloud billing
+        accounts list.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the cloudbilling/v1 API. The full documentation for this
+    API can be found at: https://cloud.google.com/billing/v1/getting-started
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha billing projects link
+
+        $ gcloud beta billing projects link
+
diff --git a/gcloud/billing/projects/list b/gcloud/billing/projects/list
new file mode 100644
index 000000000..c1899841c
--- /dev/null
+++ b/gcloud/billing/projects/list
@@ -0,0 +1,65 @@
+NAME
+    gcloud billing projects list - list all active projects associated with the
+        specified billing account
+
+SYNOPSIS
+    gcloud billing projects list --billing-account=ACCOUNT_ID
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    gcloud billing projects list ACCOUNT_ID -- lists all active projects, for
+    the specified billing account id.
+
+EXAMPLES
+    To list projects linked to billing account 0X0X0X-0X0X0X-0X0X0X, run:
+
+        $ gcloud billing projects list --billing-account=0X0X0X-0X0X0X-0X0X0X
+
+REQUIRED FLAGS
+     --billing-account=ACCOUNT_ID
+        Specify a billing account ID. Billing account IDs are of the form
+        0X0X0X-0X0X0X-0X0X0X. To see available IDs, run $ gcloud billing
+        accounts list.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha billing projects list
+
+        $ gcloud beta billing projects list
+
diff --git a/gcloud/billing/projects/unlink b/gcloud/billing/projects/unlink
new file mode 100644
index 000000000..8efa36abe
--- /dev/null
+++ b/gcloud/billing/projects/unlink
@@ -0,0 +1,45 @@
+NAME
+    gcloud billing projects unlink - unlink the account (if any) linked with a
+        project
+
+SYNOPSIS
+    gcloud billing projects unlink PROJECT_ID [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command unlinks a project from its associated billing account. This
+    action disables billing on the project. Any billable resources and services
+    in use in your project are stopped, and your application stops functioning.
+    Any costs accrued prior to disabling billing on the project are charged to
+    the previously associated billing account.
+
+    Note: To link a project to a different billing account, use the billing
+    projects link command. You do not need to unlink the project first.
+
+EXAMPLES
+    To unlink the project my-project from its linked billing account, run:
+
+        $ gcloud billing projects unlink my-project
+
+POSITIONAL ARGUMENTS
+     PROJECT_ID
+        Specify a project id.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the cloudbilling/v1 API. The full documentation for this
+    API can be found at: https://cloud.google.com/billing/v1/getting-started
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha billing projects unlink
+
+        $ gcloud beta billing projects unlink
+
diff --git a/gcloud/compute/routers/get-nat-ip-info b/gcloud/compute/routers/get-nat-ip-info
new file mode 100644
index 000000000..31dacff74
--- /dev/null
+++ b/gcloud/compute/routers/get-nat-ip-info
@@ -0,0 +1,69 @@
+NAME
+    gcloud compute routers get-nat-ip-info - display NAT IP information in a
+        router
+
+SYNOPSIS
+    gcloud compute routers get-nat-ip-info NAME [--nat-name=NAT_NAME]
+        [--region=REGION] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+        $ gcloud compute routers get-nat-ip-info
+
+    shows a mapping of IP:[usage, mode] allocated to each NAT via the specified
+    router.
+
+EXAMPLES
+    To show NAT IP information from all NATs in router 'r1' in region
+    'us-central1', run:
+
+        $ gcloud compute routers get-nat-ip-info r1 --region=us-central1
+
+    To show NAT IP information for a specific NAT 'nat1' in router 'r1' in
+    region 'us-central1', run:
+
+        $ gcloud compute routers get-nat-ip-info r1 --region=us-central1 \
+          --nat-name="nat1"
+
+POSITIONAL ARGUMENTS
+     NAME
+        Name of the router to get NAT IP info.
+
+FLAGS
+     --nat-name=NAT_NAME
+        The NAT name to filter out NAT IP information
+
+     --region=REGION
+        Region of the router to get NAT IP info. If not specified, you might be
+        prompted to select a region (interactive mode only).
+
+        To avoid prompting when this flag is omitted, you can set the
+        compute/region property:
+
+            $ gcloud config set compute/region REGION
+
+        A list of regions can be fetched by running:
+
+            $ gcloud compute regions list
+
+        To unset the property, run:
+
+            $ gcloud config unset compute/region
+
+        Alternatively, the region can be stored in the environment variable
+        CLOUDSDK_COMPUTE_REGION.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha compute routers get-nat-ip-info
+
+        $ gcloud beta compute routers get-nat-ip-info
+
diff --git a/gcloud/compute/routers/help b/gcloud/compute/routers/help
index 9d181228e..85d7d3e2f 100644
--- a/gcloud/compute/routers/help
+++ b/gcloud/compute/routers/help
@@ -43,6 +43,9 @@ COMMANDS
      describe
         Describe a Compute Engine router.
 
+     get-nat-ip-info
+        Display NAT IP information in a router.
+
      get-nat-mapping-info
         Display NAT Mapping information in a router.
 
diff --git a/gcloud/compute/tpus/tpu-vm/create b/gcloud/compute/tpus/tpu-vm/create
index 72d3ec2db..9d8bb472c 100644
--- a/gcloud/compute/tpus/tpu-vm/create
+++ b/gcloud/compute/tpus/tpu-vm/create
@@ -3,9 +3,9 @@ NAME
 
 SYNOPSIS
     gcloud compute tpus tpu-vm create (TPU : --zone=ZONE) --version=VERSION
-        [--async] [--data-disk=DATA_DISK] [--description=DESCRIPTION]
-        [--internal-ips] [--labels=[LABELS,...]] [--metadata=[METADATA,...]]
-        [--metadata-from-file=[METADATA_FROM_FILE,...]]
+        [--async] [--data-disk=[mode=MODE],[source=SOURCE]]
+        [--description=DESCRIPTION] [--internal-ips] [--labels=[KEY=VALUE,...]]
+        [--metadata=[KEY=VALUE,...]] [--metadata-from-file=[KEY=VALUE,...]]
         [--network=NETWORK; default="default"] [--preemptible] [--range=RANGE]
         [--reserved] [--scopes=[SCOPES,...]]
         [--service-account=SERVICE_ACCOUNT] [--shielded-secure-boot]
@@ -81,7 +81,7 @@ OPTIONAL FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
-     --data-disk=DATA_DISK
+     --data-disk=[mode=MODE],[source=SOURCE]
         Additional data disks for the TPU VM.
 
         This flag must be repeated to provide multiple data disks. For example:
@@ -110,15 +110,15 @@ OPTIONAL FLAGS
         default is that external IP addresses will be associated with the TPU
         workers.
 
-     --labels=[LABELS,...]
+     --labels=[KEY=VALUE,...]
         Resource labels to represent user-provided metadata. See
         https://cloud.google.com/compute/docs/labeling-resources for details.
 
-     --metadata=[METADATA,...]
+     --metadata=[KEY=VALUE,...]
         List of comma-separated metadata key-value pairs for the Cloud TPU VM
         node. Example: --metadata='key1=value1,key2=value2'
 
-     --metadata-from-file=[METADATA_FROM_FILE,...]
+     --metadata-from-file=[KEY=VALUE,...]
         Same as --metadata except the value for the entry will be read from a
         local file. Example: --metadata-from-file='key1=value1.txt'
 
diff --git a/gcloud/container/aws/node-pools/create b/gcloud/container/aws/node-pools/create
index 90e07adec..bc0450f22 100644
--- a/gcloud/container/aws/node-pools/create
+++ b/gcloud/container/aws/node-pools/create
@@ -120,7 +120,7 @@ OPTIONAL FLAGS
         complete.
 
      --node-labels=NODE_LABEL,[NODE_LABEL,...]
-        Labels assigned to nodes of the node pool.
+        Labels assigned to the node pool's nodes.
 
      --node-taints=NODE_TAINT,[NODE_TAINT,...]
         Taints assigned to nodes of the node pool. Node taint is of format
diff --git a/gcloud/container/aws/node-pools/update b/gcloud/container/aws/node-pools/update
index d64a55640..8711eee56 100644
--- a/gcloud/container/aws/node-pools/update
+++ b/gcloud/container/aws/node-pools/update
@@ -16,6 +16,7 @@ SYNOPSIS
         [--clear-autoscaling-metrics
           | --autoscaling-metrics=[AUTOSCALING_METRIC,...]
           --autoscaling-metrics-granularity=AUTOSCALING_METRICS_GRANULARITY]
+        [--clear-node-labels | --node-labels=NODE_LABEL,[NODE_LABEL,...]]
         [--clear-proxy-config | --proxy-secret-arn=PROXY_SECRET_ARN
           --proxy-secret-version-id=PROXY_SECRET_VERSION_ID]
         [--clear-security-group-ids
@@ -142,6 +143,16 @@ FLAGS
             Frequency at which EC2 Auto Scaling sends aggregated data to AWS
             CloudWatch. The only valid value is "1Minute".
 
+     Node labels
+
+     At most one of these can be specified:
+
+       --clear-node-labels
+          Clear the labels assigned to the node pool's nodes.
+
+       --node-labels=NODE_LABEL,[NODE_LABEL,...]
+          Labels assigned to the node pool's nodes.
+
      Proxy config
 
      At most one of these can be specified:
diff --git a/gcloud/container/azure/node-pools/create b/gcloud/container/azure/node-pools/create
index 6e9773345..05939eb7e 100644
--- a/gcloud/container/azure/node-pools/create
+++ b/gcloud/container/azure/node-pools/create
@@ -119,7 +119,7 @@ OPTIONAL FLAGS
         data.
 
      --node-labels=NODE_LABEL,[NODE_LABEL,...]
-        Labels assigned to nodes of the node pool.
+        Labels assigned to the node pool's nodes.
 
      --node-taints=NODE_TAINT,[NODE_TAINT,...]
         Taints assigned to nodes of the node pool. Node taint is of format
diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create
index 17087ada5..63b35e887 100644
--- a/gcloud/container/clusters/create
+++ b/gcloud/container/clusters/create
@@ -755,14 +755,15 @@ FLAGS
      --monitoring=[COMPONENT,...]
         Set the components that have monitoring enabled. Valid component values
         are: SYSTEM, WORKLOAD (Deprecated), NONE, API_SERVER,
-        CONTROLLER_MANAGER, SCHEDULER
+        CONTROLLER_MANAGER, SCHEDULER, DAEMONSET, DEPLOYMENT, HPA, POD,
+        STATEFULSET, STORAGE
 
         For more information, see
         https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics
 
         Examples:
 
-            $ gcloud container clusters create --monitoring=SYSTEM,API_SERVER
+            $ gcloud container clusters create --monitoring=SYSTEM,API_SERVER,POD
             $ gcloud container clusters create --monitoring=NONE
 
      --network=NETWORK
diff --git a/gcloud/container/clusters/create-auto b/gcloud/container/clusters/create-auto
index e15f6c280..802ae7c7d 100644
--- a/gcloud/container/clusters/create-auto
+++ b/gcloud/container/clusters/create-auto
@@ -222,7 +222,8 @@ FLAGS
      --monitoring=[COMPONENT,...]
         Set the components that have monitoring enabled. Valid component values
         are: SYSTEM, WORKLOAD (Deprecated), NONE, API_SERVER,
-        CONTROLLER_MANAGER, SCHEDULER
+        CONTROLLER_MANAGER, SCHEDULER, DAEMONSET, DEPLOYMENT, HPA, POD,
+        STATEFULSET, STORAGE
 
         For more information, see
         https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics
@@ -230,7 +231,7 @@ FLAGS
         Examples:
 
             $ gcloud container clusters create-auto \
-                --monitoring=SYSTEM,API_SERVER
+                --monitoring=SYSTEM,API_SERVER,POD
             $ gcloud container clusters create-auto --monitoring=NONE
 
      --network=NETWORK
diff --git a/gcloud/container/clusters/update b/gcloud/container/clusters/update
index 72cbe81be..996d770b9 100644
--- a/gcloud/container/clusters/update
+++ b/gcloud/container/clusters/update
@@ -1078,14 +1078,15 @@ REQUIRED FLAGS
        --monitoring=[COMPONENT,...]
           Set the components that have monitoring enabled. Valid component
           values are: SYSTEM, WORKLOAD (Deprecated), NONE, API_SERVER,
-          CONTROLLER_MANAGER, SCHEDULER
+          CONTROLLER_MANAGER, SCHEDULER, DAEMONSET, DEPLOYMENT, HPA, POD,
+          STATEFULSET, STORAGE
 
           For more information, see
           https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics
 
           Examples:
 
-              $ gcloud container clusters update --monitoring=SYSTEM,API_SERVER
+              $ gcloud container clusters update --monitoring=SYSTEM,API_SERVER,POD
               $ gcloud container clusters update --monitoring=NONE
 
        At most one of these can be specified:
diff --git a/gcloud/container/fleet/create b/gcloud/container/fleet/create
new file mode 100644
index 000000000..7b80da9e1
--- /dev/null
+++ b/gcloud/container/fleet/create
@@ -0,0 +1,76 @@
+NAME
+    gcloud container fleet create - create a fleet
+
+SYNOPSIS
+    gcloud container fleet create [--async] [--display-name=DISPLAY_NAME]
+        [--labels=[KEY=VALUE,...]]
+        [--security-posture=SECURITY_POSTURE
+          --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project specified already has a fleet.
+      ▪ The active account does not have permission to access the given
+        project.
+
+EXAMPLES
+    To create a fleet in project example-foo-bar-1 with display name my-fleet,
+    run:
+
+        $ gcloud container fleet create --display-name=my-fleet \
+            --project=example-foo-bar-1
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --display-name=DISPLAY_NAME
+        Display name of the fleet to be created (optional). 4-30 characters,
+        alphanumeric and [ '"!-] only.
+
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     Default cluster configurations to apply across the fleet.
+
+       Security posture config.
+
+         --security-posture=SECURITY_POSTURE
+            To apply basic security posture to the clusters of the fleet,
+
+                $ gcloud container fleet create --security-posture=basic
+
+            SECURITY_POSTURE must be one of: disabled, basic, enterprise.
+
+         --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING
+            To apply basic vulnerability scanning to the clusters of the fleet,
+
+                $ gcloud container fleet create \
+                    --workload-vulnerability-scanning=disabled
+
+            WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, basic,
+            enterprise.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet create
+
+        $ gcloud beta container fleet create
+
diff --git a/gcloud/container/fleet/delete b/gcloud/container/fleet/delete
new file mode 100644
index 000000000..3494d013f
--- /dev/null
+++ b/gcloud/container/fleet/delete
@@ -0,0 +1,38 @@
+NAME
+    gcloud container fleet delete - delete a fleet
+
+SYNOPSIS
+    gcloud container fleet delete [--async] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project specified already has a fleet.
+      ▪ The active account does not have permission to access the given
+        project.
+
+EXAMPLES
+    To delete a fleet in project example-foo-bar-1, run:
+
+        $ gcloud container fleet delete --project=example-foo-bar-1
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet delete
+
+        $ gcloud beta container fleet delete
+
diff --git a/gcloud/container/fleet/describe b/gcloud/container/fleet/describe
new file mode 100644
index 000000000..aa43130b5
--- /dev/null
+++ b/gcloud/container/fleet/describe
@@ -0,0 +1,33 @@
+NAME
+    gcloud container fleet describe - show fleet info
+
+SYNOPSIS
+    gcloud container fleet describe [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project specified does not have a fleet.
+      ▪ The active account does not have permission to access the given
+        project.
+
+EXAMPLES
+    To print metadata for the fleet in project example-foo-bar-1, run:
+
+        $ gcloud container fleet describe --project=example-foo-bar-1
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet describe
+
+        $ gcloud beta container fleet describe
+
diff --git a/gcloud/container/fleet/help b/gcloud/container/fleet/help
index c582defd1..f55082174 100644
--- a/gcloud/container/fleet/help
+++ b/gcloud/container/fleet/help
@@ -70,6 +70,27 @@ GROUPS
      multi-cluster-services
         Manage Multi-cluster Services Feature.
 
+     scopes
+        Manage scopes of all your GKE fleets.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        Create a fleet.
+
+     delete
+        Delete a fleet.
+
+     describe
+        Show fleet info.
+
+     list
+        List fleets visible to the user in an organization.
+
+     update
+        Update a fleet.
+
 NOTES
     These variants are also available:
 
diff --git a/gcloud/container/fleet/list b/gcloud/container/fleet/list
new file mode 100644
index 000000000..dfb0416c5
--- /dev/null
+++ b/gcloud/container/fleet/list
@@ -0,0 +1,72 @@
+NAME
+    gcloud container fleet list - list fleets visible to the user in an
+        organization
+
+SYNOPSIS
+    gcloud container fleet list [--organization=ORGANIZATION_ID]
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The org or project specified does not exist.
+      ▪ The user does not have access to the project specified.
+
+EXAMPLES
+    The following command lists fleets in organization 12345:
+
+        $ gcloud container fleet list --organization=12345
+
+COMMONLY USED FLAGS
+     --organization=ORGANIZATION_ID
+        ID (number) for the organization to list fleets from. If neither
+        --organization nor --project are provided, defaults to the organization
+        of the active project.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet list
+
+        $ gcloud beta container fleet list
+
diff --git a/gcloud/container/fleet/memberships/bindings/create b/gcloud/container/fleet/memberships/bindings/create
new file mode 100644
index 000000000..e3c02042a
--- /dev/null
+++ b/gcloud/container/fleet/memberships/bindings/create
@@ -0,0 +1,104 @@
+NAME
+    gcloud container fleet memberships bindings create - create a Membership
+        Binding
+
+SYNOPSIS
+    gcloud container fleet memberships bindings create
+        (BINDING : --location=LOCATION --membership=MEMBERSHIP) --scope=SCOPE
+        [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The Membership Binding already exists.
+      ▪ The caller does not have permission to access the given Membership.
+      ▪ The Scope or the Membership does not exist.
+      ▪ The caller did not specify the location (--location) if referring to
+        location other than global.
+
+EXAMPLES
+    To create a membership binding BINDING_NAME in global membership
+    MEMBERSHIP_NAME for scope SCOPE_NAME, run:
+
+        $ gcloud container fleet memberships bindings create BINDING_NAME \
+            --membership=MEMBERSHIP_NAME --scope=SCOPE_NAME
+
+    To create a Binding BINDING_NAME associated with regional membership
+    MEMBERSHIP_NAME, provide the location LOCATION_NAME for the Membership
+    where the Binding belongs along with membership name and associated Scope
+    SCOPE_NAME.
+
+        $ gcloud container fleet memberships bindings create BINDING_NAME \
+            --membership=MEMBERSHIP_NAME --scope=SCOPE_NAME \
+            --location=LOCATION_NAME
+
+POSITIONAL ARGUMENTS
+     Binding resource - The group of arguments defining a Membership Binding.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument BINDING on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       BINDING
+          ID of the binding or fully qualified identifier for the binding.
+
+          To set the binding attribute:
+          ▸ provide the argument BINDING on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the binding.
+
+          To set the location attribute:
+          ▸ provide the argument BINDING on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --membership=MEMBERSHIP
+          Name of the binding.
+
+          To set the membership attribute:
+          ▸ provide the argument BINDING on the command line with a fully
+            specified name;
+          ▸ provide the argument --membership on the command line.
+
+REQUIRED FLAGS
+     --scope=SCOPE
+        ID of the scope or fully qualified identifier for the scope.
+
+        To set the scope attribute:
+        ◆ provide the argument --scope on the command line.
+
+OPTIONAL FLAGS
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet memberships bindings create
+
+        $ gcloud beta container fleet memberships bindings create
+
diff --git a/gcloud/container/fleet/memberships/bindings/delete b/gcloud/container/fleet/memberships/bindings/delete
new file mode 100644
index 000000000..bd78aa40a
--- /dev/null
+++ b/gcloud/container/fleet/memberships/bindings/delete
@@ -0,0 +1,86 @@
+NAME
+    gcloud container fleet memberships bindings delete - delete a Membership
+        Binding
+
+SYNOPSIS
+    gcloud container fleet memberships bindings delete
+        (BINDING : --location=LOCATION --membership=MEMBERSHIP)
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The Membership specified does not exist.
+      ▪ The Membership Binding specified does not exist.
+      ▪ The caller does not have permission to access the given Membership.
+      ▪ The caller did not specify the location (--location) if referring to
+        location other than global.
+
+EXAMPLES
+    To delete Membership Binding BINDING_NAME in global Membership
+    MEMBERSHIP_NAME for a global membership:
+
+        $ gcloud container fleet memberships bindings delete BINDING_NAME \
+            --membership=MEMBERSHIP_NAME
+
+    To delete a Binding BINDING_NAME associated with regional membership
+    MEMBERSHIP_NAME, provide the location LOCATION_NAME for the Membership
+    where the Binding belongs along with the membership name.
+
+        $ gcloud container fleet memberships bindings delete BINDING_NAME \
+            --membership=MEMBERSHIP_NAME --location=LOCATION_NAME
+
+POSITIONAL ARGUMENTS
+     Binding resource - The group of arguments defining a Membership Binding.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument BINDING on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       BINDING
+          ID of the binding or fully qualified identifier for the binding.
+
+          To set the binding attribute:
+          ▸ provide the argument BINDING on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the binding.
+
+          To set the location attribute:
+          ▸ provide the argument BINDING on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --membership=MEMBERSHIP
+          Name of the binding.
+
+          To set the membership attribute:
+          ▸ provide the argument BINDING on the command line with a fully
+            specified name;
+          ▸ provide the argument --membership on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet memberships bindings delete
+
+        $ gcloud beta container fleet memberships bindings delete
+
diff --git a/gcloud/container/fleet/memberships/bindings/describe b/gcloud/container/fleet/memberships/bindings/describe
new file mode 100644
index 000000000..9b7ec3276
--- /dev/null
+++ b/gcloud/container/fleet/memberships/bindings/describe
@@ -0,0 +1,87 @@
+NAME
+    gcloud container fleet memberships bindings describe - show
+        Membership-Binding info
+
+SYNOPSIS
+    gcloud container fleet memberships bindings describe
+        (BINDING : --location=LOCATION --membership=MEMBERSHIP)
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The Membership specified does not exist.
+      ▪ The Membership Binding specified does not exist in the project.
+      ▪ The caller does not have permission to access the Membership Binding.
+      ▪ The caller did not specify the location (--location) if referring to
+        location other than global.
+
+EXAMPLES
+    To print metadata for the membership Binding BINDING_NAME in a global
+    membership MEMBERSHIP_NAME, run:
+
+        $ gcloud container fleet memberships bindings describe \
+            BINDING_NAME --membership=MEMBERSHIP_NAME
+
+    To print metadata for the Binding BINDING_NAME associated with regional
+    membership MEMBERSHIP_NAME, provide the location LOCATION_NAME for the
+    Membership where the Binding belongs along with membership name.
+
+        $ gcloud container fleet memberships bindings describe \
+            BINDING_NAME --membership=MEMBERSHIP_NAME \
+            --location=LOCATION_NAME
+
+POSITIONAL ARGUMENTS
+     Binding resource - The group of arguments defining a Membership Binding.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument BINDING on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       BINDING
+          ID of the binding or fully qualified identifier for the binding.
+
+          To set the binding attribute:
+          ▸ provide the argument BINDING on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the binding.
+
+          To set the location attribute:
+          ▸ provide the argument BINDING on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --membership=MEMBERSHIP
+          Name of the binding.
+
+          To set the membership attribute:
+          ▸ provide the argument BINDING on the command line with a fully
+            specified name;
+          ▸ provide the argument --membership on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet memberships bindings describe
+
+        $ gcloud beta container fleet memberships bindings describe
+
diff --git a/gcloud/container/fleet/memberships/bindings/help b/gcloud/container/fleet/memberships/bindings/help
new file mode 100644
index 000000000..fffe76984
--- /dev/null
+++ b/gcloud/container/fleet/memberships/bindings/help
@@ -0,0 +1,46 @@
+NAME
+    gcloud container fleet memberships bindings - membership Bindings for
+        permissions
+
+SYNOPSIS
+    gcloud container fleet memberships bindings COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command group allows for manipulation of bindings associated with
+    membership-scope.
+
+EXAMPLES
+    Manage Bindings:
+
+        $ gcloud container fleet memberships bindings --help
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        Create a Membership Binding.
+
+     delete
+        Delete a Membership Binding.
+
+     describe
+        Show Membership-Binding info.
+
+     list
+        List Bindings in a Membership.
+
+     update
+        Update the Binding in a Membership.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet memberships bindings
+
+        $ gcloud beta container fleet memberships bindings
+
diff --git a/gcloud/container/fleet/memberships/bindings/list b/gcloud/container/fleet/memberships/bindings/list
new file mode 100644
index 000000000..4e9a24663
--- /dev/null
+++ b/gcloud/container/fleet/memberships/bindings/list
@@ -0,0 +1,85 @@
+NAME
+    gcloud container fleet memberships bindings list - list Bindings in a
+        Membership
+
+SYNOPSIS
+    gcloud container fleet memberships bindings list --membership=MEMBERSHIP
+        [--location=LOCATION; default="global"] [--filter=EXPRESSION]
+        [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The Membership specified does not exist.
+      ▪ The user does not have access to the Membership specified.
+      ▪ The caller did not specify the location (--location) if referring to
+        location other than global.
+
+EXAMPLES
+    The following command lists Bindings in global Membership MEMBERSHIP_NAME:
+
+        $ gcloud container fleet memberships bindings list \
+            --membership=MEMBERSHIP_NAME
+
+    To list all the bindings associated with regional membership
+    MEMBERSHIP_NAME, provide the location LOCATION_NAME for the Membership
+    where the Binding belongs along with membership name.
+
+        $ gcloud container fleet memberships bindings list BINDING_NAME \
+            --membership=MEMBERSHIP_NAME --location=LOCATION_NAME
+
+REQUIRED FLAGS
+     --membership=MEMBERSHIP
+        Name of the Membership to list Bindings from.
+
+FLAGS
+     --location=LOCATION; default="global"
+        Name of the Membership location to list Bindings from.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet memberships bindings list
+
+        $ gcloud beta container fleet memberships bindings list
+
diff --git a/gcloud/container/fleet/memberships/bindings/update b/gcloud/container/fleet/memberships/bindings/update
new file mode 100644
index 000000000..4eeae2fe3
--- /dev/null
+++ b/gcloud/container/fleet/memberships/bindings/update
@@ -0,0 +1,127 @@
+NAME
+    gcloud container fleet memberships bindings update - update the Binding in
+        a Membership
+
+SYNOPSIS
+    gcloud container fleet memberships bindings update
+        (BINDING : --location=LOCATION --membership=MEMBERSHIP) --scope=SCOPE
+        [--update-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The Membership specified does not exist.
+      ▪ The Binding does not exist in the Membership.
+      ▪ The caller does not have permission to access the Membership/Binding.
+      ▪ The Scope specified does not exist.
+      ▪ The caller did not specify the location (--location) if referring to
+        location other than global.
+
+EXAMPLES
+    To update the binding BINDING_NAME in global membership MEMBERSHIP_NAME in
+    the active project:
+
+        $ gcloud container fleet memberships bindings update BINDING_NAME \
+            --membership=MEMBERSHIP_NAME
+
+    To update a Binding BINDING_NAME associated with regional membership
+    MEMBERSHIP_NAME, provide the location LOCATION_NAME for the Membership
+    where the Binding belongs along with membership name and associated Scope
+    SCOPE_NAME.
+
+        $ gcloud container fleet memberships bindings update BINDING_NAME \
+            --membership=MEMBERSHIP_NAME --scope=SCOPE_NAME \
+            --location=LOCATION_NAME
+
+POSITIONAL ARGUMENTS
+     Binding resource - The group of arguments defining a Membership Binding.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument BINDING on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       BINDING
+          ID of the binding or fully qualified identifier for the binding.
+
+          To set the binding attribute:
+          ▸ provide the argument BINDING on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the binding.
+
+          To set the location attribute:
+          ▸ provide the argument BINDING on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --membership=MEMBERSHIP
+          Name of the binding.
+
+          To set the membership attribute:
+          ▸ provide the argument BINDING on the command line with a fully
+            specified name;
+          ▸ provide the argument --membership on the command line.
+
+REQUIRED FLAGS
+     --scope=SCOPE
+        ID of the scope or fully qualified identifier for the scope.
+
+        To set the scope attribute:
+        ◆ provide the argument --scope on the command line.
+
+OPTIONAL FLAGS
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud container fleet memberships bindings update --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud container fleet memberships bindings update \
+                --clear-labels --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet memberships bindings update
+
+        $ gcloud beta container fleet memberships bindings update
+
diff --git a/gcloud/container/fleet/memberships/help b/gcloud/container/fleet/memberships/help
index 93ce17e3a..593f13caa 100644
--- a/gcloud/container/fleet/memberships/help
+++ b/gcloud/container/fleet/memberships/help
@@ -14,6 +14,12 @@ GCLOUD WIDE FLAGS
 
     Run $ gcloud help for details.
 
+GROUPS
+    GROUP is one of the following:
+
+     bindings
+        Membership Bindings for permissions.
+
 COMMANDS
     COMMAND is one of the following:
 
diff --git a/gcloud/container/fleet/scopes/add-iam-policy-binding b/gcloud/container/fleet/scopes/add-iam-policy-binding
new file mode 100644
index 000000000..4678ade5e
--- /dev/null
+++ b/gcloud/container/fleet/scopes/add-iam-policy-binding
@@ -0,0 +1,88 @@
+NAME
+    gcloud container fleet scopes add-iam-policy-binding - add IAM policy
+        binding to a Fleet Scope
+
+SYNOPSIS
+    gcloud container fleet scopes add-iam-policy-binding SCOPE
+        --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Add an IAM policy binding to the IAM policy of a Fleet Scope. One binding
+    consists of a member, and a role.
+
+EXAMPLES
+    To add an IAM policy binding for the role of 'roles/gkehub.scopeUser' for
+    the user 'test-user@gmail.com' with scope 'my-scope', run:
+
+        $ gcloud container fleet scopes add-iam-policy-binding my-scope \
+            --member='user:test-user@gmail.com' \
+            --role='roles/gkehub.scopeUser'
+
+    See https://cloud.google.com/iam/docs/managing-policies for details of
+    policy role and member types.
+
+POSITIONAL ARGUMENTS
+     Scope resource - The scope for which to add IAM policy binding to. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     To set the location attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+REQUIRED FLAGS
+     --member=PRINCIPAL
+        The principal to add the binding for. Should be of the form
+        user|group|serviceAccount:email or domain:domain.
+
+        Examples: user:test-user@gmail.com, group:admins@example.com,
+        serviceAccount:test123@example.domain.com, or
+        domain:example.domain.com.
+
+        Some resources also accept the following special values:
+        ◆ allUsers - Special identifier that represents anyone who is on the
+          internet, with or without a Google account.
+        ◆ allAuthenticatedUsers - Special identifier that represents anyone
+          who is authenticated with a Google account or a service account.
+
+     --role=ROLE
+        Role name to assign to the principal. The role name is the complete
+        path of a predefined role, such as roles/logging.viewer, or the role ID
+        for a custom role, such as
+        organizations/{ORGANIZATION_ID}/roles/logging.viewer.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1 API. The full documentation for this API
+    can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet scopes add-iam-policy-binding
+
+        $ gcloud beta container fleet scopes add-iam-policy-binding
+
diff --git a/gcloud/container/fleet/scopes/create b/gcloud/container/fleet/scopes/create
new file mode 100644
index 000000000..87a054891
--- /dev/null
+++ b/gcloud/container/fleet/scopes/create
@@ -0,0 +1,76 @@
+NAME
+    gcloud container fleet scopes create - create a new fleet scope
+
+SYNOPSIS
+    gcloud container fleet scopes create SCOPE [--async]
+        [--labels=[KEY=VALUE,...]] [--namespace-labels=[KEY=VALUE,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Create a Fleet Scope resource.
+
+EXAMPLES
+    Create a new scope SCOPE_NAME in the active project's fleet:
+
+        $ gcloud container fleet scopes create SCOPE_NAME
+
+POSITIONAL ARGUMENTS
+     Scope resource - The fleet scope resourse to be created. This represents a
+     Cloud resource. (NOTE) Some attributes are not given arguments in this
+     group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     To set the location attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     --namespace-labels=[KEY=VALUE,...]
+        List of scope-level label KEY=VALUE pairs to add.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1 API. The full documentation for this API
+    can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet scopes create
+
+        $ gcloud beta container fleet scopes create
+
diff --git a/gcloud/container/fleet/scopes/delete b/gcloud/container/fleet/scopes/delete
new file mode 100644
index 000000000..8ffd040e9
--- /dev/null
+++ b/gcloud/container/fleet/scopes/delete
@@ -0,0 +1,78 @@
+NAME
+    gcloud container fleet scopes delete - delete a fleet scope
+
+SYNOPSIS
+    gcloud container fleet scopes delete (SCOPE : --location=LOCATION)
+        [--async] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command deletes a Fleet Scope resource .
+
+EXAMPLES
+    First retrieve the ID of the scope using the command below. The output of
+    this command lists all the fleet's scopes, with their unique IDs in the
+    Names column:
+
+        $ gcloud container fleet scopes list
+
+    Delete a scope from the active project's fleet:
+
+        $ gcloud container fleet scopes delete SCOPE_NAME
+
+POSITIONAL ARGUMENTS
+     Scope resource - The fleet scope to delete. The arguments in this group
+     can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location name.
+
+          To set the location attribute:
+          ▸ provide the argument scope on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ global is the only supported location.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1 API. The full documentation for this API
+    can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet scopes delete
+
+        $ gcloud beta container fleet scopes delete
+
diff --git a/gcloud/container/fleet/scopes/describe b/gcloud/container/fleet/scopes/describe
new file mode 100644
index 000000000..810f4a394
--- /dev/null
+++ b/gcloud/container/fleet/scopes/describe
@@ -0,0 +1,72 @@
+NAME
+    gcloud container fleet scopes describe - describe a fleet scope
+
+SYNOPSIS
+    gcloud container fleet scopes describe (SCOPE : --location=LOCATION)
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Describe a Fleet Scope.
+
+EXAMPLES
+    First retrieve the ID of the scope using the command below. The output of
+    this command lists all the fleet's members, with their unique IDs in the
+    Names column:
+
+        $ gcloud container fleet scopes list
+
+    Then describe it:
+
+        $ gcloud container fleet scopes describe SCOPE_NAME
+
+POSITIONAL ARGUMENTS
+     Scope resource - The scope to describe. The arguments in this group can be
+     used to specify the attributes of this resource. (NOTE) Some attributes
+     are not given arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location name.
+
+          To set the location attribute:
+          ▸ provide the argument scope on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ global is the only supported location.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1 API. The full documentation for this API
+    can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet scopes describe
+
+        $ gcloud beta container fleet scopes describe
+
diff --git a/gcloud/container/fleet/scopes/get-iam-policy b/gcloud/container/fleet/scopes/get-iam-policy
new file mode 100644
index 000000000..bedf13db3
--- /dev/null
+++ b/gcloud/container/fleet/scopes/get-iam-policy
@@ -0,0 +1,87 @@
+NAME
+    gcloud container fleet scopes get-iam-policy - get the IAM policy for a
+        Fleet Scope
+
+SYNOPSIS
+    gcloud container fleet scopes get-iam-policy SCOPE [--filter=EXPRESSION]
+        [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command gets the IAM policy for a scope.
+
+EXAMPLES
+    To print the IAM policy for a given scope, run:
+
+        $ gcloud container fleet scopes get-iam-policy my-scope
+
+POSITIONAL ARGUMENTS
+     Scope resource - The scope for which to display the IAM policy. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     To set the location attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1 API. The full documentation for this API
+    can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet scopes get-iam-policy
+
+        $ gcloud beta container fleet scopes get-iam-policy
+
diff --git a/gcloud/container/fleet/scopes/help b/gcloud/container/fleet/scopes/help
new file mode 100644
index 000000000..d8fa491be
--- /dev/null
+++ b/gcloud/container/fleet/scopes/help
@@ -0,0 +1,57 @@
+NAME
+    gcloud container fleet scopes - manage scopes of all your GKE fleets
+
+SYNOPSIS
+    gcloud container fleet scopes GROUP | COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Manage scopes of all your GKE fleets.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+GROUPS
+    GROUP is one of the following:
+
+     namespaces
+        Fleet namespaces are the fleet equivalent of k8s cluster namespaces.
+
+     rbacrolebindings
+        Fleet scope RBAC RoleBindings for permissions.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     add-iam-policy-binding
+        Add IAM policy binding to a Fleet Scope.
+
+     create
+        Create a new fleet scope.
+
+     delete
+        Delete a fleet scope.
+
+     describe
+        Describe a fleet scope.
+
+     get-iam-policy
+        Get the IAM policy for a Fleet Scope.
+
+     list
+        List fleet scopes.
+
+     remove-iam-policy-binding
+        Remove IAM policy binding of a Fleet Scope.
+
+     update
+        Update a scope.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet scopes
+
+        $ gcloud beta container fleet scopes
+
diff --git a/gcloud/container/fleet/scopes/list b/gcloud/container/fleet/scopes/list
new file mode 100644
index 000000000..bd885e6ac
--- /dev/null
+++ b/gcloud/container/fleet/scopes/list
@@ -0,0 +1,68 @@
+NAME
+    gcloud container fleet scopes list - list fleet scopes
+
+SYNOPSIS
+    gcloud container fleet scopes list [--filter=EXPRESSION] [--limit=LIMIT]
+        [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    List scopes in a fleet.
+
+EXAMPLES
+    List scopes in the active project's fleet:
+
+        $ gcloud container fleet scopes list
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1 API. The full documentation for this API
+    can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet scopes list
+
+        $ gcloud beta container fleet scopes list
+
diff --git a/gcloud/container/fleet/scopes/namespaces/create b/gcloud/container/fleet/scopes/namespaces/create
new file mode 100644
index 000000000..c16a02830
--- /dev/null
+++ b/gcloud/container/fleet/scopes/namespaces/create
@@ -0,0 +1,88 @@
+NAME
+    gcloud container fleet scopes namespaces create - create a fleet namespace
+
+SYNOPSIS
+    gcloud container fleet scopes namespaces create (NAMESPACE : --scope=SCOPE)
+        [--labels=[KEY=VALUE,...]] [--namespace-labels=[KEY=VALUE,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project has a fleet namespace with the same name.
+      ▪ The caller does not have permission to access the given project.
+
+EXAMPLES
+    To create a fleet namespace with name NAMESPACE in the active project, run:
+
+        $ gcloud container fleet scopes namespaces create NAMESPACE
+
+    To create a fleet namespace in fleet scope SCOPE in project PROJECT_ID with
+    name NAMESPACE, run:
+
+        $ gcloud container fleet scopes namespaces create NAMESPACE \
+            --scope=SCOPE --project=PROJECT_ID
+
+POSITIONAL ARGUMENTS
+     Namespace resource - The group of arguments defining the Fleet Namespace.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       NAMESPACE
+          ID of the namespace or fully qualified identifier for the namespace.
+
+          To set the namespace attribute:
+          ▸ provide the argument NAMESPACE on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --scope=SCOPE
+          the
+
+          To set the scope attribute:
+          ▸ provide the argument NAMESPACE on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+FLAGS
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     --namespace-labels=[KEY=VALUE,...]
+        List of namespace-level label KEY=VALUE pairs to add.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet scopes namespaces create
+
+        $ gcloud beta container fleet scopes namespaces create
+
diff --git a/gcloud/container/fleet/scopes/namespaces/delete b/gcloud/container/fleet/scopes/namespaces/delete
new file mode 100644
index 000000000..7c4f3bddd
--- /dev/null
+++ b/gcloud/container/fleet/scopes/namespaces/delete
@@ -0,0 +1,75 @@
+NAME
+    gcloud container fleet scopes namespaces delete - delete a fleet namespace
+
+SYNOPSIS
+    gcloud container fleet scopes namespaces delete (NAMESPACE : --scope=SCOPE)
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The namespace specified does not exist.
+      ▪ The caller does not have permission to access the given project or
+        namespace.
+
+EXAMPLES
+    To delete fleet namespace NAMESPACE in the active project:
+
+        $ gcloud container fleet scopes namespaces delete NAMESPACE
+
+    To delete fleet namespace NAMESPACE in project PROJECT_ID:
+
+        $ gcloud container fleet scopes namespaces delete NAMESPACE \
+            --project=PROJECT_ID
+
+POSITIONAL ARGUMENTS
+     Namespace resource - The group of arguments defining the Fleet Namespace.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       NAMESPACE
+          ID of the namespace or fully qualified identifier for the namespace.
+
+          To set the namespace attribute:
+          ▸ provide the argument NAMESPACE on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --scope=SCOPE
+          the
+
+          To set the scope attribute:
+          ▸ provide the argument NAMESPACE on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet scopes namespaces delete
+
+        $ gcloud beta container fleet scopes namespaces delete
+
diff --git a/gcloud/container/fleet/scopes/namespaces/describe b/gcloud/container/fleet/scopes/namespaces/describe
new file mode 100644
index 000000000..3e272449c
--- /dev/null
+++ b/gcloud/container/fleet/scopes/namespaces/describe
@@ -0,0 +1,76 @@
+NAME
+    gcloud container fleet scopes namespaces describe - show fleet namespace
+        info
+
+SYNOPSIS
+    gcloud container fleet scopes namespaces describe
+        (NAMESPACE : --scope=SCOPE) [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The namespace specified does not exist in the project.
+      ▪ The caller does not have permission to access the project or
+        namespace.
+
+EXAMPLES
+    To print metadata for the namespace NAMESPACE in the active project, run:
+
+        $ gcloud container fleet scopes namespaces describe NAMESPACE
+
+    To print metadata for the namespace NAMESPACE in project PROJECT_ID, run:
+
+        $ gcloud container fleet scopes namespaces describe NAMESPACE \
+            --project=PROJECT_ID
+
+POSITIONAL ARGUMENTS
+     Namespace resource - The group of arguments defining the Fleet Namespace.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       NAMESPACE
+          ID of the namespace or fully qualified identifier for the namespace.
+
+          To set the namespace attribute:
+          ▸ provide the argument NAMESPACE on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --scope=SCOPE
+          the
+
+          To set the scope attribute:
+          ▸ provide the argument NAMESPACE on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet scopes namespaces describe
+
+        $ gcloud beta container fleet scopes namespaces describe
+
diff --git a/gcloud/container/fleet/scopes/namespaces/get-credentials b/gcloud/container/fleet/scopes/namespaces/get-credentials
new file mode 100644
index 000000000..953b3fbf6
--- /dev/null
+++ b/gcloud/container/fleet/scopes/namespaces/get-credentials
@@ -0,0 +1,59 @@
+NAME
+    gcloud container fleet scopes namespaces get-credentials - fetch
+        credentials for a membership with a particular namespace
+
+SYNOPSIS
+    gcloud container fleet scopes namespaces get-credentials NAMESPACE
+        [--membership=MEMBERSHIP] [--membership-location=MEMBERSHIP_LOCATION]
+        [--set-namespace-in-config=SET_NAMESPACE_IN_CONFIG]
+        [GCLOUD_WIDE_FLAG ...]
+
+EXAMPLES
+    Get the Connect Gateway kubeconfig for global membership MEMBERSHIP, using
+    namespace NAMESPACE in the config:
+
+        $ gcloud container fleet scopes namespaces get-credentials \
+            NAMESPACE --membership=MEMBERSHIP --membership-location=global \
+            --set-namespace-in-config=true
+
+    Get the Connect Gateway kubeconfig for global membership MEMBERSHIP:
+
+        $ gcloud container fleet scopes namespaces get-credentials \
+            NAMESPACE --membership=MEMBERSHIP --membership-location=global
+
+POSITIONAL ARGUMENTS
+     NAMESPACE
+        Name of the namespace for which to get access to memberships.
+
+FLAGS
+     --membership=MEMBERSHIP
+        Membership ID to get credentials from. If not provided, a prompt will
+        offer a list of memberships in the fleet.
+
+     --membership-location=MEMBERSHIP_LOCATION
+        The location of the membership resource, e.g. us-central1. If not
+        specified, defaults to global.
+
+     --set-namespace-in-config=SET_NAMESPACE_IN_CONFIG
+        If true, the default namespace for the context in the generated
+        kubeconfig will be set to the Fleet namespace (i.e. the name given as
+        the positional argument in this command).
+
+        Otherwise, no default namespace will be set, functioning the same as
+        gcloud container fleet memberships get-credentials.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet scopes namespaces get-credentials
+
+        $ gcloud beta container fleet scopes namespaces get-credentials
+
diff --git a/gcloud/container/fleet/scopes/namespaces/help b/gcloud/container/fleet/scopes/namespaces/help
new file mode 100644
index 000000000..c5e893e12
--- /dev/null
+++ b/gcloud/container/fleet/scopes/namespaces/help
@@ -0,0 +1,52 @@
+NAME
+    gcloud container fleet scopes namespaces - fleet namespaces are the fleet
+        equivalent of k8s cluster namespaces
+
+SYNOPSIS
+    gcloud container fleet scopes namespaces COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command group allows for manipulation of fleet namespaces.
+
+EXAMPLES
+    Manage fleet namespaces:
+
+        $ gcloud container fleet scopes namespaces --help
+
+    Manage RBAC RoleBindings in a fleet namespace:
+
+        $ gcloud container fleet scopes namespaces rbacrolebindings --help
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        Create a fleet namespace.
+
+     delete
+        Delete a fleet namespace.
+
+     describe
+        Show fleet namespace info.
+
+     get-credentials
+        Fetch credentials for a membership with a particular namespace.
+
+     list
+        List fleet namespaces in a project.
+
+     update
+        Update a fleet namespace.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet scopes namespaces
+
+        $ gcloud beta container fleet scopes namespaces
+
diff --git a/gcloud/container/fleet/scopes/namespaces/list b/gcloud/container/fleet/scopes/namespaces/list
new file mode 100644
index 000000000..c07bbfa3d
--- /dev/null
+++ b/gcloud/container/fleet/scopes/namespaces/list
@@ -0,0 +1,94 @@
+NAME
+    gcloud container fleet scopes namespaces list - list fleet namespaces in a
+        project
+
+SYNOPSIS
+    gcloud container fleet scopes namespaces list --scope=SCOPE
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The user does not have access to the project specified.
+
+EXAMPLES
+    The following command lists namespaces in the active project:
+
+        $ gcloud container fleet scopes namespaces list
+
+    The following command lists namespaces in project PROJECT_ID:
+
+        $ gcloud container fleet scopes namespaces list --project=PROJECT_ID
+
+REQUIRED FLAGS
+     Scope resource - The group of arguments defining the Fleet Scope. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --scope on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --scope on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       --scope=SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument --scope on the command line.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet scopes namespaces list
+
+        $ gcloud beta container fleet scopes namespaces list
+
diff --git a/gcloud/container/fleet/scopes/namespaces/update b/gcloud/container/fleet/scopes/namespaces/update
new file mode 100644
index 000000000..ea0f4474a
--- /dev/null
+++ b/gcloud/container/fleet/scopes/namespaces/update
@@ -0,0 +1,139 @@
+NAME
+    gcloud container fleet scopes namespaces update - update a fleet namespace
+
+SYNOPSIS
+    gcloud container fleet scopes namespaces update (NAMESPACE : --scope=SCOPE)
+        [--update-labels=[KEY=VALUE,...]]
+        [--update-namespace-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]]
+        [--clear-namespace-labels | --remove-namespace-labels=[KEY,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The fleet namespace does not exist in the project.
+      ▪ The caller does not have permission to access the project or
+        namespace.
+
+EXAMPLES
+    To update the namespace NAMESPACE in the active project:
+
+        $ gcloud container fleet scopes namespaces update NAMESPACE
+
+    To update the namespace NAMESPACE in project PROJECT_ID:
+
+        $ gcloud container fleet scopes namespaces update NAMESPACE \
+            --project=PROJECT_ID
+
+POSITIONAL ARGUMENTS
+     Namespace resource - The group of arguments defining the Fleet Namespace.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       NAMESPACE
+          ID of the namespace or fully qualified identifier for the namespace.
+
+          To set the namespace attribute:
+          ▸ provide the argument NAMESPACE on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --scope=SCOPE
+          the
+
+          To set the scope attribute:
+          ▸ provide the argument NAMESPACE on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+FLAGS
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     --update-namespace-labels=[KEY=VALUE,...]
+        List of namespace-level label KEY=VALUE pairs to update in the cluster
+        namespace. If a label exists, its value is modified. Otherwise, a new
+        label is' created.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud container fleet scopes namespaces update --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud container fleet scopes namespaces update --clear-labels \
+                --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+     At most one of these can be specified:
+
+       --clear-namespace-labels
+          Remove all namespace-level labels from the cluster namespace. If
+          --update-namespace-labels is also specified then
+          --clear-namespace-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud container fleet scopes namespaces update namespace_name \
+                --clear-namespace-labels
+
+          To remove all existing namespace-level labels and create two new
+          labels, foo and baz:
+
+              $ gcloud container fleet scopes namespaces update namespace_name \
+                --clear-namespace-labels \
+                --update-namespace-labels foo=bar,baz=qux
+
+       --remove-namespace-labels=[KEY,...]
+          List of namespace-level label keys to remove in the cluster
+          namespace. If a label does not exist it is silently ignored. If
+          --update-namespace-labels is also specified then
+          --update-namespace-labels is applied first.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet scopes namespaces update
+
+        $ gcloud beta container fleet scopes namespaces update
+
diff --git a/gcloud/container/fleet/scopes/rbacrolebindings/create b/gcloud/container/fleet/scopes/rbacrolebindings/create
new file mode 100644
index 000000000..71e4e0751
--- /dev/null
+++ b/gcloud/container/fleet/scopes/rbacrolebindings/create
@@ -0,0 +1,105 @@
+NAME
+    gcloud container fleet scopes rbacrolebindings create - create an RBAC
+        RoleBinding
+
+SYNOPSIS
+    gcloud container fleet scopes rbacrolebindings create
+        (NAME : --location=LOCATION --scope=SCOPE) --role=ROLE
+        (--group=GROUP | --user=USER) [--labels=[KEY=VALUE,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The RBAC RoleBinding already exists.
+      ▪ The caller does not have permission to access the given scope.
+
+EXAMPLES
+    To create an admin RBAC RoleBinding RBRB in scope SCOPE for user
+    person@google.com, run:
+
+        $ gcloud container fleet scopes rbacrolebindings create RBRB \
+            --scope=SCOPE --role=admin --user=person@google.com
+
+    To create a viewer RBAC RoleBinding RBRB in scope SCOPE for group
+    people@google.com, run:
+
+        $ gcloud container fleet scopes rbacrolebindings create RBRB \
+            --scope=SCOPE --role=viewer --group=people@google.com
+
+POSITIONAL ARGUMENTS
+     Rbacrolebinding resource - The group of arguments defining an
+     RBACRoleBinding. The arguments in this group can be used to specify the
+     attributes of this resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAME on the command line with a fully specified
+        name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       NAME
+          ID of the rbacrolebinding or fully qualified identifier for the
+          rbacrolebinding.
+
+          To set the rbacrolebinding attribute:
+          ▸ provide the argument NAME on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the rbacrolebinding.
+
+          To set the location attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --scope=SCOPE
+          Name of the rbacrolebinding.
+
+          To set the scope attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+REQUIRED FLAGS
+     --role=ROLE
+        Role to assign. ROLE must be one of: admin, edit, view.
+
+     Exactly one of these must be specified:
+
+       --group=GROUP
+          Group for the RoleBinding.
+
+       --user=USER
+          User for the RoleBinding.
+
+OPTIONAL FLAGS
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet scopes rbacrolebindings create
+
+        $ gcloud beta container fleet scopes rbacrolebindings create
+
diff --git a/gcloud/container/fleet/scopes/rbacrolebindings/delete b/gcloud/container/fleet/scopes/rbacrolebindings/delete
new file mode 100644
index 000000000..1af3aad00
--- /dev/null
+++ b/gcloud/container/fleet/scopes/rbacrolebindings/delete
@@ -0,0 +1,75 @@
+NAME
+    gcloud container fleet scopes rbacrolebindings delete - delete a fleet
+        scope RBAC RoleBinding
+
+SYNOPSIS
+    gcloud container fleet scopes rbacrolebindings delete
+        (NAME : --location=LOCATION --scope=SCOPE) [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The RoleBinding specified does not exist.
+      ▪ The caller does not have permission to access the given RoleBinding.
+
+EXAMPLES
+    To delete RBAC RoleBinding RBRB in scope SCOPE in the active project:
+
+        $ gcloud container fleet scopes rbacrolebindings delete RBRB \
+            --scope=SCOPE
+
+POSITIONAL ARGUMENTS
+     Rbacrolebinding resource - The group of arguments defining an
+     RBACRoleBinding. The arguments in this group can be used to specify the
+     attributes of this resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAME on the command line with a fully specified
+        name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       NAME
+          ID of the rbacrolebinding or fully qualified identifier for the
+          rbacrolebinding.
+
+          To set the rbacrolebinding attribute:
+          ▸ provide the argument NAME on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the rbacrolebinding.
+
+          To set the location attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --scope=SCOPE
+          Name of the rbacrolebinding.
+
+          To set the scope attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet scopes rbacrolebindings delete
+
+        $ gcloud beta container fleet scopes rbacrolebindings delete
+
diff --git a/gcloud/container/fleet/scopes/rbacrolebindings/describe b/gcloud/container/fleet/scopes/rbacrolebindings/describe
new file mode 100644
index 000000000..d4e2df453
--- /dev/null
+++ b/gcloud/container/fleet/scopes/rbacrolebindings/describe
@@ -0,0 +1,75 @@
+NAME
+    gcloud container fleet scopes rbacrolebindings describe - show fleet scope
+        RBAC RoleBinding information
+
+SYNOPSIS
+    gcloud container fleet scopes rbacrolebindings describe
+        (NAME : --location=LOCATION --scope=SCOPE) [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The RoleBinding specified does not exist in the project.
+      ▪ The caller does not have permission to access the RoleBinding.
+
+EXAMPLES
+    To print metadata for RBAC RoleBinding RBRB in the scope SCOPE, run:
+
+        $ gcloud container fleet scopes rbacrolebindings describe RBRB \
+            --scope=SCOPE
+
+POSITIONAL ARGUMENTS
+     Rbacrolebinding resource - The group of arguments defining an
+     RBACRoleBinding. The arguments in this group can be used to specify the
+     attributes of this resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAME on the command line with a fully specified
+        name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       NAME
+          ID of the rbacrolebinding or fully qualified identifier for the
+          rbacrolebinding.
+
+          To set the rbacrolebinding attribute:
+          ▸ provide the argument NAME on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the rbacrolebinding.
+
+          To set the location attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --scope=SCOPE
+          Name of the rbacrolebinding.
+
+          To set the scope attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet scopes rbacrolebindings describe
+
+        $ gcloud beta container fleet scopes rbacrolebindings describe
+
diff --git a/gcloud/container/fleet/scopes/rbacrolebindings/help b/gcloud/container/fleet/scopes/rbacrolebindings/help
new file mode 100644
index 000000000..5247e4fe0
--- /dev/null
+++ b/gcloud/container/fleet/scopes/rbacrolebindings/help
@@ -0,0 +1,47 @@
+NAME
+    gcloud container fleet scopes rbacrolebindings - fleet scope RBAC
+        RoleBindings for permissions
+
+SYNOPSIS
+    gcloud container fleet scopes rbacrolebindings COMMAND
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command group allows for manipulation of fleet namespace RBAC
+    RoleBindings.
+
+EXAMPLES
+    Manage RBAC RoleBindings:
+
+        $ gcloud container fleet scopes rbacrolebindings --help
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        Create an RBAC RoleBinding.
+
+     delete
+        Delete a fleet scope RBAC RoleBinding.
+
+     describe
+        Show fleet scope RBAC RoleBinding information.
+
+     list
+        List RBAC RoleBindings in a fleet scope.
+
+     update
+        Update a fleet scope RBAC RoleBinding.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet scopes rbacrolebindings
+
+        $ gcloud beta container fleet scopes rbacrolebindings
+
diff --git a/gcloud/container/fleet/scopes/rbacrolebindings/list b/gcloud/container/fleet/scopes/rbacrolebindings/list
new file mode 100644
index 000000000..65b1d65ec
--- /dev/null
+++ b/gcloud/container/fleet/scopes/rbacrolebindings/list
@@ -0,0 +1,72 @@
+NAME
+    gcloud container fleet scopes rbacrolebindings list - list RBAC
+        RoleBindings in a fleet scope
+
+SYNOPSIS
+    gcloud container fleet scopes rbacrolebindings list --scope=SCOPE
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The scope specified does not exist.
+      ▪ The user does not have access to the specified scope.
+
+EXAMPLES
+    The following command lists RBAC RoleBindings in scope SCOPE in project
+    PROJECT_ID:
+
+        $ gcloud container fleet scopes rbacrolebindings list \
+            --scope=SCOPE --project=PROJECT_ID
+
+REQUIRED FLAGS
+     --scope=SCOPE
+        Name of the fleet scope to list RBAC RoleBindings from.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet scopes rbacrolebindings list
+
+        $ gcloud beta container fleet scopes rbacrolebindings list
+
diff --git a/gcloud/container/fleet/scopes/rbacrolebindings/update b/gcloud/container/fleet/scopes/rbacrolebindings/update
new file mode 100644
index 000000000..6a63fa479
--- /dev/null
+++ b/gcloud/container/fleet/scopes/rbacrolebindings/update
@@ -0,0 +1,128 @@
+NAME
+    gcloud container fleet scopes rbacrolebindings update - update a fleet
+        scope RBAC RoleBinding
+
+SYNOPSIS
+    gcloud container fleet scopes rbacrolebindings update
+        (NAME : --location=LOCATION --scope=SCOPE) [--role=ROLE]
+        [--update-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]]
+        [--group=GROUP | --user=USER] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The RoleBinding does not exist in the project.
+      ▪ The caller does not have permission to access the RoleBinding.
+
+EXAMPLES
+    To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to
+    the viewer role:
+
+        $ gcloud container fleet scopes rbacrolebindings update RBRB \
+            --scope=SCOPE --role=viewer
+
+    To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to
+    the user someone@google.com:
+
+        $ gcloud container fleet scopes rbacrolebindings update RBRB \
+            --scope=SCOPE --user=someone@google.com
+
+POSITIONAL ARGUMENTS
+     Rbacrolebinding resource - The group of arguments defining an
+     RBACRoleBinding. The arguments in this group can be used to specify the
+     attributes of this resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAME on the command line with a fully specified
+        name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       NAME
+          ID of the rbacrolebinding or fully qualified identifier for the
+          rbacrolebinding.
+
+          To set the rbacrolebinding attribute:
+          ▸ provide the argument NAME on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the rbacrolebinding.
+
+          To set the location attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --scope=SCOPE
+          Name of the rbacrolebinding.
+
+          To set the scope attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+FLAGS
+     --role=ROLE
+        Role for the RBACRoleBinding to update to. ROLE must be one of: admin,
+        edit, view.
+
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud container fleet scopes rbacrolebindings update \
+                --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud container fleet scopes rbacrolebindings update \
+                --clear-labels --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+     At most one of these can be specified:
+
+       --group=GROUP
+          Group for the RBACRoleBinding to update to.
+
+       --user=USER
+          User for the RBACRoleBinding to update to.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet scopes rbacrolebindings update
+
+        $ gcloud beta container fleet scopes rbacrolebindings update
+
diff --git a/gcloud/container/fleet/scopes/remove-iam-policy-binding b/gcloud/container/fleet/scopes/remove-iam-policy-binding
new file mode 100644
index 000000000..9f363a6e6
--- /dev/null
+++ b/gcloud/container/fleet/scopes/remove-iam-policy-binding
@@ -0,0 +1,89 @@
+NAME
+    gcloud container fleet scopes remove-iam-policy-binding - remove IAM policy
+        binding of a Fleet Scope
+
+SYNOPSIS
+    gcloud container fleet scopes remove-iam-policy-binding SCOPE
+        --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Remove an IAM policy binding from the IAM policy of a scope. One binding
+    consists of a member, and a role.
+
+EXAMPLES
+    To remove an IAM policy binding for the role of 'roles/gkehub.scopeUser'
+    for the user 'test-user@gmail.com' with scope 'my-scope', run:
+
+        $ gcloud container fleet scopes remove-iam-policy-binding my-scope \
+            --member='user:test-user@gmail.com' \
+            --role='roles/gkehub.scopeUser'
+
+    See https://cloud.google.com/iam/docs/managing-policies for details of
+    policy role and member types.
+
+POSITIONAL ARGUMENTS
+     Scope resource - The scope for which to remove IAM policy binding from.
+     This represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     To set the location attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+REQUIRED FLAGS
+     --member=PRINCIPAL
+        The principal to remove the binding for. Should be of the form
+        user|group|serviceAccount:email or domain:domain.
+
+        Examples: user:test-user@gmail.com, group:admins@example.com,
+        serviceAccount:test123@example.domain.com, or
+        domain:example.domain.com.
+
+        Deleted principals have an additional deleted: prefix and a ?uid=UID
+        suffix, where UID is a unique identifier for the principal. Example:
+        deleted:user:test-user@gmail.com?uid=123456789012345678901.
+
+        Some resources also accept the following special values:
+        ◆ allUsers - Special identifier that represents anyone who is on the
+          internet, with or without a Google account.
+        ◆ allAuthenticatedUsers - Special identifier that represents anyone
+          who is authenticated with a Google account or a service account.
+
+     --role=ROLE
+        The role to remove the principal from.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1 API. The full documentation for this API
+    can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet scopes remove-iam-policy-binding
+
+        $ gcloud beta container fleet scopes remove-iam-policy-binding
+
diff --git a/gcloud/container/fleet/scopes/update b/gcloud/container/fleet/scopes/update
new file mode 100644
index 000000000..d5276c94e
--- /dev/null
+++ b/gcloud/container/fleet/scopes/update
@@ -0,0 +1,227 @@
+NAME
+    gcloud container fleet scopes update - update a scope
+
+SYNOPSIS
+    gcloud container fleet scopes update (SCOPE : --location=LOCATION)
+        [--update-labels=[KEY=VALUE,...]]
+        [--update-namespace-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]]
+        [--clear-namespace-labels | --remove-namespace-labels=[KEY,...]]
+        [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING
+          --remove-upgrade-soaking-overrides
+          | --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE
+          --upgrade-selector=[name=NAME],[version=VERSION]
+          --reset-upstream-scope | --upstream-scope=UPSTREAM_SCOPE]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Update an existing Fleet Scope.
+
+EXAMPLES
+    First retrieve the ID of the scope using the command below.
+
+        $ gcloud container fleet scopes list
+
+    Update a scope.
+
+        $ gcloud container fleet scopes update SCOPE_NAME
+
+POSITIONAL ARGUMENTS
+     Scope resource - fleet scope resource. The arguments in this group can be
+     used to specify the attributes of this resource. (NOTE) Some attributes
+     are not given arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location name.
+
+          To set the location attribute:
+          ▸ provide the argument scope on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ global is the only supported location.
+
+FLAGS
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     --update-namespace-labels=[KEY=VALUE,...]
+        List of scope-level label KEY=VALUE pairs to update in the cluster
+        namespace. If a label exists, its value is modified. Otherwise, a new
+        label is' created.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud container fleet scopes update --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud container fleet scopes update --clear-labels \
+                --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+     At most one of these can be specified:
+
+       --clear-namespace-labels
+          Remove all scope-level labels from the cluster namespace. If
+          --update-namespace-labels is also specified then
+          --clear-namespace-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud container fleet scopes update scope_name \
+                --clear-namespace-labels
+
+          To remove all existing scope-level labels and create two new labels,
+          foo and baz:
+
+              $ gcloud container fleet scopes update scope_name \
+                --clear-namespace-labels \
+                --update-namespace-labels foo=bar,baz=qux
+
+       --remove-namespace-labels=[KEY,...]
+          List of scope-level label keys to remove in the cluster namespace. If
+          a label does not exist it is silently ignored. If
+          --update-namespace-labels is also specified then
+          --update-namespace-labels is applied first.
+
+     Rollout Sequencing
+
+       --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING
+          Configures the default soaking duration for each upgrade propagating
+          through the current scope to become "COMPLETE". Soaking begins after
+          all clusters in the scope are on the target version, or after 30 days
+          if all cluster upgrades are not complete. Once an upgrade state
+          becomes "COMPLETE", it will automatically be propagated to the
+          downstream scope. Max is 30 days.
+
+          See $ gcloud topic datetimes for information on duration formats.
+
+          To configure Rollout Sequencing for a given scope, SCOPE_NAME, this
+          attribute must be set. To do this while specifying a default soaking
+          duration of 7 days, run:
+
+              $ gcloud container fleet scopes update SCOPE_NAME \
+                  default-upgrade-soaking=7d
+
+       At most one of these can be specified:
+
+         --remove-upgrade-soaking-overrides
+            Removes soaking time overrides for all upgrades propagating through
+            the current scope. Consequently, all upgrades will follow the soak
+            time configured by --default-upgrade-soaking until new overrides
+            are configured with --add_upgrade_soaking_override and
+            --upgrade_selector.
+
+            To remove all soaking time overrides configured for SCOPE_NAME,
+            run:
+
+                $ gcloud container fleet scopes update SCOPE_NAME \
+                    --remove-upgrade-soaking-overrides
+
+         Upgrade soaking override.
+
+         Defines a specific soaking time override for a particular upgrade
+         propagating through the current scope that supercedes the default
+         soaking duration configured by --default-upgrade-soaking.
+
+         To set an upgrade soaking override of 12 hours for the upgrade with
+         name, k8s_control_plane, and version, 1.23.1-gke.1000, run:
+
+             $ gcloud container fleet scopes update SCOPE_NAME \
+               --add-upgrade-soaking-override=12h \
+               --upgrade-selector=name="k8s_control_plane",version="1.23.1-gke.1000"
+
+           --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE
+              Overrides the soaking time for a particular upgrade name and
+              version propagating through the current scope. Set soaking to 0
+              days to bypass soaking and fast-forward the upgrade to the
+              downstream scope.
+
+              See $ gcloud topic datetimes for information on duration formats.
+
+              This flag argument must be specified if any of the other
+              arguments in this group are specified.
+
+           --upgrade-selector=[name=NAME],[version=VERSION]
+              Name and version of the upgrade to be overridden where version is
+              a full GKE version. Currently, name can be either
+              k8s_control_plane or k8s_node.
+
+              This flag argument must be specified if any of the other
+              arguments in this group are specified.
+
+       At most one of these can be specified:
+
+         --reset-upstream-scope
+            Clears the relationship between the current scope and its upstream
+            scope in the rollout sequence.
+
+            To remove the link between SCOPE_NAME and its upstream scope, run:
+
+                $ gcloud container fleet scopes update SCOPE_NAME \
+                    --reset-upstream-scope
+
+         --upstream-scope=UPSTREAM_SCOPE
+            Full resource name of the upstream scope in the format of
+            projects/{project}/locations/{location}/scopes/{scope}. GKE will
+            finish upgrades on the upstream scope before applying the same
+            upgrades to the current scope.
+
+            To configure the upstream scope for SCOPE_NAME, run:
+
+                $ gcloud container fleet scopes update SCOPE_NAME \
+                  --upstream-scope=projects/{upstream_project}/locations/global/scopes/{upstream_scope}
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1 API. The full documentation for this API
+    can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet scopes update
+
+        $ gcloud beta container fleet scopes update
+
diff --git a/gcloud/container/fleet/update b/gcloud/container/fleet/update
new file mode 100644
index 000000000..2532bdd89
--- /dev/null
+++ b/gcloud/container/fleet/update
@@ -0,0 +1,98 @@
+NAME
+    gcloud container fleet update - update a fleet
+
+SYNOPSIS
+    gcloud container fleet update [--async] [--display-name=DISPLAY_NAME]
+        [--update-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]]
+        [--security-posture=SECURITY_POSTURE
+          --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project specified already has a fleet.
+      ▪ The active account does not have permission to access the given
+        project.
+
+EXAMPLES
+    To update the display name of the fleet in project example-foo-bar-1 to
+    updated-name, run:
+
+        $ gcloud container fleet update --display-name=updated-name \
+            --project=example-foo-bar-1
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --display-name=DISPLAY_NAME
+        Display name of the fleet to be created (optional). 4-30 characters,
+        alphanumeric and [ '"!-] only.
+
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud container fleet update --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud container fleet update --clear-labels \
+                --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+     Default cluster configurations to apply across the fleet.
+
+       Security posture config.
+
+         --security-posture=SECURITY_POSTURE
+            To apply basic security posture to the clusters of the fleet,
+
+                $ gcloud container fleet update --security-posture=basic
+
+            SECURITY_POSTURE must be one of: disabled, basic, enterprise.
+
+         --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING
+            To apply basic vulnerability scanning to the clusters of the fleet,
+
+                $ gcloud container fleet update \
+                    --workload-vulnerability-scanning=disabled
+
+            WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, basic,
+            enterprise.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container fleet update
+
+        $ gcloud beta container fleet update
+
diff --git a/gcloud/container/hub/create b/gcloud/container/hub/create
new file mode 100644
index 000000000..ca60b5ade
--- /dev/null
+++ b/gcloud/container/hub/create
@@ -0,0 +1,76 @@
+NAME
+    gcloud container hub create - create a fleet
+
+SYNOPSIS
+    gcloud container hub create [--async] [--display-name=DISPLAY_NAME]
+        [--labels=[KEY=VALUE,...]]
+        [--security-posture=SECURITY_POSTURE
+          --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project specified already has a fleet.
+      ▪ The active account does not have permission to access the given
+        project.
+
+EXAMPLES
+    To create a fleet in project example-foo-bar-1 with display name my-fleet,
+    run:
+
+        $ gcloud container hub create --display-name=my-fleet \
+            --project=example-foo-bar-1
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --display-name=DISPLAY_NAME
+        Display name of the fleet to be created (optional). 4-30 characters,
+        alphanumeric and [ '"!-] only.
+
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     Default cluster configurations to apply across the fleet.
+
+       Security posture config.
+
+         --security-posture=SECURITY_POSTURE
+            To apply basic security posture to the clusters of the fleet,
+
+                $ gcloud container hub create --security-posture=basic
+
+            SECURITY_POSTURE must be one of: disabled, basic, enterprise.
+
+         --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING
+            To apply basic vulnerability scanning to the clusters of the fleet,
+
+                $ gcloud container hub create \
+                    --workload-vulnerability-scanning=disabled
+
+            WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, basic,
+            enterprise.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub create
+
+        $ gcloud beta container hub create
+
diff --git a/gcloud/container/hub/delete b/gcloud/container/hub/delete
new file mode 100644
index 000000000..9fca44a72
--- /dev/null
+++ b/gcloud/container/hub/delete
@@ -0,0 +1,38 @@
+NAME
+    gcloud container hub delete - delete a fleet
+
+SYNOPSIS
+    gcloud container hub delete [--async] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project specified already has a fleet.
+      ▪ The active account does not have permission to access the given
+        project.
+
+EXAMPLES
+    To delete a fleet in project example-foo-bar-1, run:
+
+        $ gcloud container hub delete --project=example-foo-bar-1
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub delete
+
+        $ gcloud beta container hub delete
+
diff --git a/gcloud/container/hub/describe b/gcloud/container/hub/describe
new file mode 100644
index 000000000..c5572c448
--- /dev/null
+++ b/gcloud/container/hub/describe
@@ -0,0 +1,33 @@
+NAME
+    gcloud container hub describe - show fleet info
+
+SYNOPSIS
+    gcloud container hub describe [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project specified does not have a fleet.
+      ▪ The active account does not have permission to access the given
+        project.
+
+EXAMPLES
+    To print metadata for the fleet in project example-foo-bar-1, run:
+
+        $ gcloud container hub describe --project=example-foo-bar-1
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub describe
+
+        $ gcloud beta container hub describe
+
diff --git a/gcloud/container/hub/help b/gcloud/container/hub/help
index a2e71fe88..8d6fe568c 100644
--- a/gcloud/container/hub/help
+++ b/gcloud/container/hub/help
@@ -70,6 +70,27 @@ GROUPS
      multi-cluster-services
         Manage Multi-cluster Services Feature.
 
+     scopes
+        Manage scopes of all your GKE fleets.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        Create a fleet.
+
+     delete
+        Delete a fleet.
+
+     describe
+        Show fleet info.
+
+     list
+        List fleets visible to the user in an organization.
+
+     update
+        Update a fleet.
+
 NOTES
     These variants are also available:
 
diff --git a/gcloud/container/hub/list b/gcloud/container/hub/list
new file mode 100644
index 000000000..68e378725
--- /dev/null
+++ b/gcloud/container/hub/list
@@ -0,0 +1,72 @@
+NAME
+    gcloud container hub list - list fleets visible to the user in an
+        organization
+
+SYNOPSIS
+    gcloud container hub list [--organization=ORGANIZATION_ID]
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The org or project specified does not exist.
+      ▪ The user does not have access to the project specified.
+
+EXAMPLES
+    The following command lists fleets in organization 12345:
+
+        $ gcloud container hub list --organization=12345
+
+COMMONLY USED FLAGS
+     --organization=ORGANIZATION_ID
+        ID (number) for the organization to list fleets from. If neither
+        --organization nor --project are provided, defaults to the organization
+        of the active project.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub list
+
+        $ gcloud beta container hub list
+
diff --git a/gcloud/container/hub/memberships/bindings/create b/gcloud/container/hub/memberships/bindings/create
new file mode 100644
index 000000000..ed961ea1c
--- /dev/null
+++ b/gcloud/container/hub/memberships/bindings/create
@@ -0,0 +1,104 @@
+NAME
+    gcloud container hub memberships bindings create - create a Membership
+        Binding
+
+SYNOPSIS
+    gcloud container hub memberships bindings create
+        (BINDING : --location=LOCATION --membership=MEMBERSHIP) --scope=SCOPE
+        [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The Membership Binding already exists.
+      ▪ The caller does not have permission to access the given Membership.
+      ▪ The Scope or the Membership does not exist.
+      ▪ The caller did not specify the location (--location) if referring to
+        location other than global.
+
+EXAMPLES
+    To create a membership binding BINDING_NAME in global membership
+    MEMBERSHIP_NAME for scope SCOPE_NAME, run:
+
+        $ gcloud container hub memberships bindings create BINDING_NAME \
+            --membership=MEMBERSHIP_NAME --scope=SCOPE_NAME
+
+    To create a Binding BINDING_NAME associated with regional membership
+    MEMBERSHIP_NAME, provide the location LOCATION_NAME for the Membership
+    where the Binding belongs along with membership name and associated Scope
+    SCOPE_NAME.
+
+        $ gcloud container hub memberships bindings create BINDING_NAME \
+            --membership=MEMBERSHIP_NAME --scope=SCOPE_NAME \
+            --location=LOCATION_NAME
+
+POSITIONAL ARGUMENTS
+     Binding resource - The group of arguments defining a Membership Binding.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument BINDING on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       BINDING
+          ID of the binding or fully qualified identifier for the binding.
+
+          To set the binding attribute:
+          ▸ provide the argument BINDING on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the binding.
+
+          To set the location attribute:
+          ▸ provide the argument BINDING on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --membership=MEMBERSHIP
+          Name of the binding.
+
+          To set the membership attribute:
+          ▸ provide the argument BINDING on the command line with a fully
+            specified name;
+          ▸ provide the argument --membership on the command line.
+
+REQUIRED FLAGS
+     --scope=SCOPE
+        ID of the scope or fully qualified identifier for the scope.
+
+        To set the scope attribute:
+        ◆ provide the argument --scope on the command line.
+
+OPTIONAL FLAGS
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub memberships bindings create
+
+        $ gcloud beta container hub memberships bindings create
+
diff --git a/gcloud/container/hub/memberships/bindings/delete b/gcloud/container/hub/memberships/bindings/delete
new file mode 100644
index 000000000..e00e500fb
--- /dev/null
+++ b/gcloud/container/hub/memberships/bindings/delete
@@ -0,0 +1,86 @@
+NAME
+    gcloud container hub memberships bindings delete - delete a Membership
+        Binding
+
+SYNOPSIS
+    gcloud container hub memberships bindings delete
+        (BINDING : --location=LOCATION --membership=MEMBERSHIP)
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The Membership specified does not exist.
+      ▪ The Membership Binding specified does not exist.
+      ▪ The caller does not have permission to access the given Membership.
+      ▪ The caller did not specify the location (--location) if referring to
+        location other than global.
+
+EXAMPLES
+    To delete Membership Binding BINDING_NAME in global Membership
+    MEMBERSHIP_NAME for a global membership:
+
+        $ gcloud container hub memberships bindings delete BINDING_NAME \
+            --membership=MEMBERSHIP_NAME
+
+    To delete a Binding BINDING_NAME associated with regional membership
+    MEMBERSHIP_NAME, provide the location LOCATION_NAME for the Membership
+    where the Binding belongs along with the membership name.
+
+        $ gcloud container hub memberships bindings delete BINDING_NAME \
+            --membership=MEMBERSHIP_NAME --location=LOCATION_NAME
+
+POSITIONAL ARGUMENTS
+     Binding resource - The group of arguments defining a Membership Binding.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument BINDING on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       BINDING
+          ID of the binding or fully qualified identifier for the binding.
+
+          To set the binding attribute:
+          ▸ provide the argument BINDING on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the binding.
+
+          To set the location attribute:
+          ▸ provide the argument BINDING on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --membership=MEMBERSHIP
+          Name of the binding.
+
+          To set the membership attribute:
+          ▸ provide the argument BINDING on the command line with a fully
+            specified name;
+          ▸ provide the argument --membership on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub memberships bindings delete
+
+        $ gcloud beta container hub memberships bindings delete
+
diff --git a/gcloud/container/hub/memberships/bindings/describe b/gcloud/container/hub/memberships/bindings/describe
new file mode 100644
index 000000000..2274bdc9e
--- /dev/null
+++ b/gcloud/container/hub/memberships/bindings/describe
@@ -0,0 +1,86 @@
+NAME
+    gcloud container hub memberships bindings describe - show
+        Membership-Binding info
+
+SYNOPSIS
+    gcloud container hub memberships bindings describe
+        (BINDING : --location=LOCATION --membership=MEMBERSHIP)
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The Membership specified does not exist.
+      ▪ The Membership Binding specified does not exist in the project.
+      ▪ The caller does not have permission to access the Membership Binding.
+      ▪ The caller did not specify the location (--location) if referring to
+        location other than global.
+
+EXAMPLES
+    To print metadata for the membership Binding BINDING_NAME in a global
+    membership MEMBERSHIP_NAME, run:
+
+        $ gcloud container hub memberships bindings describe BINDING_NAME \
+            --membership=MEMBERSHIP_NAME
+
+    To print metadata for the Binding BINDING_NAME associated with regional
+    membership MEMBERSHIP_NAME, provide the location LOCATION_NAME for the
+    Membership where the Binding belongs along with membership name.
+
+        $ gcloud container hub memberships bindings describe BINDING_NAME \
+            --membership=MEMBERSHIP_NAME --location=LOCATION_NAME
+
+POSITIONAL ARGUMENTS
+     Binding resource - The group of arguments defining a Membership Binding.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument BINDING on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       BINDING
+          ID of the binding or fully qualified identifier for the binding.
+
+          To set the binding attribute:
+          ▸ provide the argument BINDING on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the binding.
+
+          To set the location attribute:
+          ▸ provide the argument BINDING on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --membership=MEMBERSHIP
+          Name of the binding.
+
+          To set the membership attribute:
+          ▸ provide the argument BINDING on the command line with a fully
+            specified name;
+          ▸ provide the argument --membership on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub memberships bindings describe
+
+        $ gcloud beta container hub memberships bindings describe
+
diff --git a/gcloud/container/hub/memberships/bindings/help b/gcloud/container/hub/memberships/bindings/help
new file mode 100644
index 000000000..dbcbf366e
--- /dev/null
+++ b/gcloud/container/hub/memberships/bindings/help
@@ -0,0 +1,46 @@
+NAME
+    gcloud container hub memberships bindings - membership Bindings for
+        permissions
+
+SYNOPSIS
+    gcloud container hub memberships bindings COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command group allows for manipulation of bindings associated with
+    membership-scope.
+
+EXAMPLES
+    Manage Bindings:
+
+        $ gcloud container hub memberships bindings --help
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        Create a Membership Binding.
+
+     delete
+        Delete a Membership Binding.
+
+     describe
+        Show Membership-Binding info.
+
+     list
+        List Bindings in a Membership.
+
+     update
+        Update the Binding in a Membership.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub memberships bindings
+
+        $ gcloud beta container hub memberships bindings
+
diff --git a/gcloud/container/hub/memberships/bindings/list b/gcloud/container/hub/memberships/bindings/list
new file mode 100644
index 000000000..af32d0eb7
--- /dev/null
+++ b/gcloud/container/hub/memberships/bindings/list
@@ -0,0 +1,85 @@
+NAME
+    gcloud container hub memberships bindings list - list Bindings in a
+        Membership
+
+SYNOPSIS
+    gcloud container hub memberships bindings list --membership=MEMBERSHIP
+        [--location=LOCATION; default="global"] [--filter=EXPRESSION]
+        [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The Membership specified does not exist.
+      ▪ The user does not have access to the Membership specified.
+      ▪ The caller did not specify the location (--location) if referring to
+        location other than global.
+
+EXAMPLES
+    The following command lists Bindings in global Membership MEMBERSHIP_NAME:
+
+        $ gcloud container hub memberships bindings list \
+            --membership=MEMBERSHIP_NAME
+
+    To list all the bindings associated with regional membership
+    MEMBERSHIP_NAME, provide the location LOCATION_NAME for the Membership
+    where the Binding belongs along with membership name.
+
+        $ gcloud container hub memberships bindings list BINDING_NAME \
+            --membership=MEMBERSHIP_NAME --location=LOCATION_NAME
+
+REQUIRED FLAGS
+     --membership=MEMBERSHIP
+        Name of the Membership to list Bindings from.
+
+FLAGS
+     --location=LOCATION; default="global"
+        Name of the Membership location to list Bindings from.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub memberships bindings list
+
+        $ gcloud beta container hub memberships bindings list
+
diff --git a/gcloud/container/hub/memberships/bindings/update b/gcloud/container/hub/memberships/bindings/update
new file mode 100644
index 000000000..331ac2c57
--- /dev/null
+++ b/gcloud/container/hub/memberships/bindings/update
@@ -0,0 +1,127 @@
+NAME
+    gcloud container hub memberships bindings update - update the Binding in a
+        Membership
+
+SYNOPSIS
+    gcloud container hub memberships bindings update
+        (BINDING : --location=LOCATION --membership=MEMBERSHIP) --scope=SCOPE
+        [--update-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The Membership specified does not exist.
+      ▪ The Binding does not exist in the Membership.
+      ▪ The caller does not have permission to access the Membership/Binding.
+      ▪ The Scope specified does not exist.
+      ▪ The caller did not specify the location (--location) if referring to
+        location other than global.
+
+EXAMPLES
+    To update the binding BINDING_NAME in global membership MEMBERSHIP_NAME in
+    the active project:
+
+        $ gcloud container hub memberships bindings update BINDING_NAME \
+            --membership=MEMBERSHIP_NAME
+
+    To update a Binding BINDING_NAME associated with regional membership
+    MEMBERSHIP_NAME, provide the location LOCATION_NAME for the Membership
+    where the Binding belongs along with membership name and associated Scope
+    SCOPE_NAME.
+
+        $ gcloud container hub memberships bindings update BINDING_NAME \
+            --membership=MEMBERSHIP_NAME --scope=SCOPE_NAME \
+            --location=LOCATION_NAME
+
+POSITIONAL ARGUMENTS
+     Binding resource - The group of arguments defining a Membership Binding.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument BINDING on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       BINDING
+          ID of the binding or fully qualified identifier for the binding.
+
+          To set the binding attribute:
+          ▸ provide the argument BINDING on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the binding.
+
+          To set the location attribute:
+          ▸ provide the argument BINDING on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --membership=MEMBERSHIP
+          Name of the binding.
+
+          To set the membership attribute:
+          ▸ provide the argument BINDING on the command line with a fully
+            specified name;
+          ▸ provide the argument --membership on the command line.
+
+REQUIRED FLAGS
+     --scope=SCOPE
+        ID of the scope or fully qualified identifier for the scope.
+
+        To set the scope attribute:
+        ◆ provide the argument --scope on the command line.
+
+OPTIONAL FLAGS
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud container hub memberships bindings update --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud container hub memberships bindings update --clear-labels \
+                --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub memberships bindings update
+
+        $ gcloud beta container hub memberships bindings update
+
diff --git a/gcloud/container/hub/memberships/help b/gcloud/container/hub/memberships/help
index ceb4730b1..27d1449a6 100644
--- a/gcloud/container/hub/memberships/help
+++ b/gcloud/container/hub/memberships/help
@@ -14,6 +14,12 @@ GCLOUD WIDE FLAGS
 
     Run $ gcloud help for details.
 
+GROUPS
+    GROUP is one of the following:
+
+     bindings
+        Membership Bindings for permissions.
+
 COMMANDS
     COMMAND is one of the following:
 
diff --git a/gcloud/container/hub/scopes/add-iam-policy-binding b/gcloud/container/hub/scopes/add-iam-policy-binding
new file mode 100644
index 000000000..df44ce766
--- /dev/null
+++ b/gcloud/container/hub/scopes/add-iam-policy-binding
@@ -0,0 +1,88 @@
+NAME
+    gcloud container hub scopes add-iam-policy-binding - add IAM policy binding
+        to a Fleet Scope
+
+SYNOPSIS
+    gcloud container hub scopes add-iam-policy-binding SCOPE --member=PRINCIPAL
+        --role=ROLE [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Add an IAM policy binding to the IAM policy of a Fleet Scope. One binding
+    consists of a member, and a role.
+
+EXAMPLES
+    To add an IAM policy binding for the role of 'roles/gkehub.scopeUser' for
+    the user 'test-user@gmail.com' with scope 'my-scope', run:
+
+        $ gcloud container hub scopes add-iam-policy-binding my-scope \
+            --member='user:test-user@gmail.com' \
+            --role='roles/gkehub.scopeUser'
+
+    See https://cloud.google.com/iam/docs/managing-policies for details of
+    policy role and member types.
+
+POSITIONAL ARGUMENTS
+     Scope resource - The scope for which to add IAM policy binding to. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     To set the location attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+REQUIRED FLAGS
+     --member=PRINCIPAL
+        The principal to add the binding for. Should be of the form
+        user|group|serviceAccount:email or domain:domain.
+
+        Examples: user:test-user@gmail.com, group:admins@example.com,
+        serviceAccount:test123@example.domain.com, or
+        domain:example.domain.com.
+
+        Some resources also accept the following special values:
+        ◆ allUsers - Special identifier that represents anyone who is on the
+          internet, with or without a Google account.
+        ◆ allAuthenticatedUsers - Special identifier that represents anyone
+          who is authenticated with a Google account or a service account.
+
+     --role=ROLE
+        Role name to assign to the principal. The role name is the complete
+        path of a predefined role, such as roles/logging.viewer, or the role ID
+        for a custom role, such as
+        organizations/{ORGANIZATION_ID}/roles/logging.viewer.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1 API. The full documentation for this API
+    can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub scopes add-iam-policy-binding
+
+        $ gcloud beta container hub scopes add-iam-policy-binding
+
diff --git a/gcloud/container/hub/scopes/create b/gcloud/container/hub/scopes/create
new file mode 100644
index 000000000..d19c81034
--- /dev/null
+++ b/gcloud/container/hub/scopes/create
@@ -0,0 +1,76 @@
+NAME
+    gcloud container hub scopes create - create a new fleet scope
+
+SYNOPSIS
+    gcloud container hub scopes create SCOPE [--async]
+        [--labels=[KEY=VALUE,...]] [--namespace-labels=[KEY=VALUE,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Create a Fleet Scope resource.
+
+EXAMPLES
+    Create a new scope SCOPE_NAME in the active project's fleet:
+
+        $ gcloud container hub scopes create SCOPE_NAME
+
+POSITIONAL ARGUMENTS
+     Scope resource - The fleet scope resourse to be created. This represents a
+     Cloud resource. (NOTE) Some attributes are not given arguments in this
+     group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     To set the location attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     --namespace-labels=[KEY=VALUE,...]
+        List of scope-level label KEY=VALUE pairs to add.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1 API. The full documentation for this API
+    can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub scopes create
+
+        $ gcloud beta container hub scopes create
+
diff --git a/gcloud/container/hub/scopes/delete b/gcloud/container/hub/scopes/delete
new file mode 100644
index 000000000..f5f177566
--- /dev/null
+++ b/gcloud/container/hub/scopes/delete
@@ -0,0 +1,78 @@
+NAME
+    gcloud container hub scopes delete - delete a fleet scope
+
+SYNOPSIS
+    gcloud container hub scopes delete (SCOPE : --location=LOCATION) [--async]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command deletes a Fleet Scope resource .
+
+EXAMPLES
+    First retrieve the ID of the scope using the command below. The output of
+    this command lists all the fleet's scopes, with their unique IDs in the
+    Names column:
+
+        $ gcloud container hub scopes list
+
+    Delete a scope from the active project's fleet:
+
+        $ gcloud container hub scopes delete SCOPE_NAME
+
+POSITIONAL ARGUMENTS
+     Scope resource - The fleet scope to delete. The arguments in this group
+     can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location name.
+
+          To set the location attribute:
+          ▸ provide the argument scope on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ global is the only supported location.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1 API. The full documentation for this API
+    can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub scopes delete
+
+        $ gcloud beta container hub scopes delete
+
diff --git a/gcloud/container/hub/scopes/describe b/gcloud/container/hub/scopes/describe
new file mode 100644
index 000000000..dd406fd6a
--- /dev/null
+++ b/gcloud/container/hub/scopes/describe
@@ -0,0 +1,72 @@
+NAME
+    gcloud container hub scopes describe - describe a fleet scope
+
+SYNOPSIS
+    gcloud container hub scopes describe (SCOPE : --location=LOCATION)
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Describe a Fleet Scope.
+
+EXAMPLES
+    First retrieve the ID of the scope using the command below. The output of
+    this command lists all the fleet's members, with their unique IDs in the
+    Names column:
+
+        $ gcloud container hub scopes list
+
+    Then describe it:
+
+        $ gcloud container hub scopes describe SCOPE_NAME
+
+POSITIONAL ARGUMENTS
+     Scope resource - The scope to describe. The arguments in this group can be
+     used to specify the attributes of this resource. (NOTE) Some attributes
+     are not given arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location name.
+
+          To set the location attribute:
+          ▸ provide the argument scope on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ global is the only supported location.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1 API. The full documentation for this API
+    can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub scopes describe
+
+        $ gcloud beta container hub scopes describe
+
diff --git a/gcloud/container/hub/scopes/get-iam-policy b/gcloud/container/hub/scopes/get-iam-policy
new file mode 100644
index 000000000..1859908e1
--- /dev/null
+++ b/gcloud/container/hub/scopes/get-iam-policy
@@ -0,0 +1,87 @@
+NAME
+    gcloud container hub scopes get-iam-policy - get the IAM policy for a Fleet
+        Scope
+
+SYNOPSIS
+    gcloud container hub scopes get-iam-policy SCOPE [--filter=EXPRESSION]
+        [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command gets the IAM policy for a scope.
+
+EXAMPLES
+    To print the IAM policy for a given scope, run:
+
+        $ gcloud container hub scopes get-iam-policy my-scope
+
+POSITIONAL ARGUMENTS
+     Scope resource - The scope for which to display the IAM policy. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     To set the location attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1 API. The full documentation for this API
+    can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub scopes get-iam-policy
+
+        $ gcloud beta container hub scopes get-iam-policy
+
diff --git a/gcloud/container/hub/scopes/help b/gcloud/container/hub/scopes/help
new file mode 100644
index 000000000..5849456ce
--- /dev/null
+++ b/gcloud/container/hub/scopes/help
@@ -0,0 +1,57 @@
+NAME
+    gcloud container hub scopes - manage scopes of all your GKE fleets
+
+SYNOPSIS
+    gcloud container hub scopes GROUP | COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Manage scopes of all your GKE fleets.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+GROUPS
+    GROUP is one of the following:
+
+     namespaces
+        Fleet namespaces are the fleet equivalent of k8s cluster namespaces.
+
+     rbacrolebindings
+        Fleet scope RBAC RoleBindings for permissions.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     add-iam-policy-binding
+        Add IAM policy binding to a Fleet Scope.
+
+     create
+        Create a new fleet scope.
+
+     delete
+        Delete a fleet scope.
+
+     describe
+        Describe a fleet scope.
+
+     get-iam-policy
+        Get the IAM policy for a Fleet Scope.
+
+     list
+        List fleet scopes.
+
+     remove-iam-policy-binding
+        Remove IAM policy binding of a Fleet Scope.
+
+     update
+        Update a scope.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub scopes
+
+        $ gcloud beta container hub scopes
+
diff --git a/gcloud/container/hub/scopes/list b/gcloud/container/hub/scopes/list
new file mode 100644
index 000000000..7e3dd99cb
--- /dev/null
+++ b/gcloud/container/hub/scopes/list
@@ -0,0 +1,68 @@
+NAME
+    gcloud container hub scopes list - list fleet scopes
+
+SYNOPSIS
+    gcloud container hub scopes list [--filter=EXPRESSION] [--limit=LIMIT]
+        [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    List scopes in a fleet.
+
+EXAMPLES
+    List scopes in the active project's fleet:
+
+        $ gcloud container hub scopes list
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1 API. The full documentation for this API
+    can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub scopes list
+
+        $ gcloud beta container hub scopes list
+
diff --git a/gcloud/container/hub/scopes/namespaces/create b/gcloud/container/hub/scopes/namespaces/create
new file mode 100644
index 000000000..58539a0cc
--- /dev/null
+++ b/gcloud/container/hub/scopes/namespaces/create
@@ -0,0 +1,88 @@
+NAME
+    gcloud container hub scopes namespaces create - create a fleet namespace
+
+SYNOPSIS
+    gcloud container hub scopes namespaces create (NAMESPACE : --scope=SCOPE)
+        [--labels=[KEY=VALUE,...]] [--namespace-labels=[KEY=VALUE,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project has a fleet namespace with the same name.
+      ▪ The caller does not have permission to access the given project.
+
+EXAMPLES
+    To create a fleet namespace with name NAMESPACE in the active project, run:
+
+        $ gcloud container hub scopes namespaces create NAMESPACE
+
+    To create a fleet namespace in fleet scope SCOPE in project PROJECT_ID with
+    name NAMESPACE, run:
+
+        $ gcloud container hub scopes namespaces create NAMESPACE \
+            --scope=SCOPE --project=PROJECT_ID
+
+POSITIONAL ARGUMENTS
+     Namespace resource - The group of arguments defining the Fleet Namespace.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       NAMESPACE
+          ID of the namespace or fully qualified identifier for the namespace.
+
+          To set the namespace attribute:
+          ▸ provide the argument NAMESPACE on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --scope=SCOPE
+          the
+
+          To set the scope attribute:
+          ▸ provide the argument NAMESPACE on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+FLAGS
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     --namespace-labels=[KEY=VALUE,...]
+        List of namespace-level label KEY=VALUE pairs to add.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub scopes namespaces create
+
+        $ gcloud beta container hub scopes namespaces create
+
diff --git a/gcloud/container/hub/scopes/namespaces/delete b/gcloud/container/hub/scopes/namespaces/delete
new file mode 100644
index 000000000..46835d7e2
--- /dev/null
+++ b/gcloud/container/hub/scopes/namespaces/delete
@@ -0,0 +1,75 @@
+NAME
+    gcloud container hub scopes namespaces delete - delete a fleet namespace
+
+SYNOPSIS
+    gcloud container hub scopes namespaces delete (NAMESPACE : --scope=SCOPE)
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The namespace specified does not exist.
+      ▪ The caller does not have permission to access the given project or
+        namespace.
+
+EXAMPLES
+    To delete fleet namespace NAMESPACE in the active project:
+
+        $ gcloud container hub scopes namespaces delete NAMESPACE
+
+    To delete fleet namespace NAMESPACE in project PROJECT_ID:
+
+        $ gcloud container hub scopes namespaces delete NAMESPACE \
+            --project=PROJECT_ID
+
+POSITIONAL ARGUMENTS
+     Namespace resource - The group of arguments defining the Fleet Namespace.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       NAMESPACE
+          ID of the namespace or fully qualified identifier for the namespace.
+
+          To set the namespace attribute:
+          ▸ provide the argument NAMESPACE on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --scope=SCOPE
+          the
+
+          To set the scope attribute:
+          ▸ provide the argument NAMESPACE on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub scopes namespaces delete
+
+        $ gcloud beta container hub scopes namespaces delete
+
diff --git a/gcloud/container/hub/scopes/namespaces/describe b/gcloud/container/hub/scopes/namespaces/describe
new file mode 100644
index 000000000..bfd6856d8
--- /dev/null
+++ b/gcloud/container/hub/scopes/namespaces/describe
@@ -0,0 +1,75 @@
+NAME
+    gcloud container hub scopes namespaces describe - show fleet namespace info
+
+SYNOPSIS
+    gcloud container hub scopes namespaces describe (NAMESPACE : --scope=SCOPE)
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The namespace specified does not exist in the project.
+      ▪ The caller does not have permission to access the project or
+        namespace.
+
+EXAMPLES
+    To print metadata for the namespace NAMESPACE in the active project, run:
+
+        $ gcloud container hub scopes namespaces describe NAMESPACE
+
+    To print metadata for the namespace NAMESPACE in project PROJECT_ID, run:
+
+        $ gcloud container hub scopes namespaces describe NAMESPACE \
+            --project=PROJECT_ID
+
+POSITIONAL ARGUMENTS
+     Namespace resource - The group of arguments defining the Fleet Namespace.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       NAMESPACE
+          ID of the namespace or fully qualified identifier for the namespace.
+
+          To set the namespace attribute:
+          ▸ provide the argument NAMESPACE on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --scope=SCOPE
+          the
+
+          To set the scope attribute:
+          ▸ provide the argument NAMESPACE on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub scopes namespaces describe
+
+        $ gcloud beta container hub scopes namespaces describe
+
diff --git a/gcloud/container/hub/scopes/namespaces/get-credentials b/gcloud/container/hub/scopes/namespaces/get-credentials
new file mode 100644
index 000000000..8980256e2
--- /dev/null
+++ b/gcloud/container/hub/scopes/namespaces/get-credentials
@@ -0,0 +1,59 @@
+NAME
+    gcloud container hub scopes namespaces get-credentials - fetch credentials
+        for a membership with a particular namespace
+
+SYNOPSIS
+    gcloud container hub scopes namespaces get-credentials NAMESPACE
+        [--membership=MEMBERSHIP] [--membership-location=MEMBERSHIP_LOCATION]
+        [--set-namespace-in-config=SET_NAMESPACE_IN_CONFIG]
+        [GCLOUD_WIDE_FLAG ...]
+
+EXAMPLES
+    Get the Connect Gateway kubeconfig for global membership MEMBERSHIP, using
+    namespace NAMESPACE in the config:
+
+        $ gcloud container hub scopes namespaces get-credentials NAMESPACE \
+            --membership=MEMBERSHIP --membership-location=global \
+            --set-namespace-in-config=true
+
+    Get the Connect Gateway kubeconfig for global membership MEMBERSHIP:
+
+        $ gcloud container hub scopes namespaces get-credentials NAMESPACE \
+            --membership=MEMBERSHIP --membership-location=global
+
+POSITIONAL ARGUMENTS
+     NAMESPACE
+        Name of the namespace for which to get access to memberships.
+
+FLAGS
+     --membership=MEMBERSHIP
+        Membership ID to get credentials from. If not provided, a prompt will
+        offer a list of memberships in the fleet.
+
+     --membership-location=MEMBERSHIP_LOCATION
+        The location of the membership resource, e.g. us-central1. If not
+        specified, defaults to global.
+
+     --set-namespace-in-config=SET_NAMESPACE_IN_CONFIG
+        If true, the default namespace for the context in the generated
+        kubeconfig will be set to the Fleet namespace (i.e. the name given as
+        the positional argument in this command).
+
+        Otherwise, no default namespace will be set, functioning the same as
+        gcloud container fleet memberships get-credentials.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub scopes namespaces get-credentials
+
+        $ gcloud beta container hub scopes namespaces get-credentials
+
diff --git a/gcloud/container/hub/scopes/namespaces/help b/gcloud/container/hub/scopes/namespaces/help
new file mode 100644
index 000000000..a27775287
--- /dev/null
+++ b/gcloud/container/hub/scopes/namespaces/help
@@ -0,0 +1,52 @@
+NAME
+    gcloud container hub scopes namespaces - fleet namespaces are the fleet
+        equivalent of k8s cluster namespaces
+
+SYNOPSIS
+    gcloud container hub scopes namespaces COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command group allows for manipulation of fleet namespaces.
+
+EXAMPLES
+    Manage fleet namespaces:
+
+        $ gcloud container hub scopes namespaces --help
+
+    Manage RBAC RoleBindings in a fleet namespace:
+
+        $ gcloud container hub scopes namespaces rbacrolebindings --help
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        Create a fleet namespace.
+
+     delete
+        Delete a fleet namespace.
+
+     describe
+        Show fleet namespace info.
+
+     get-credentials
+        Fetch credentials for a membership with a particular namespace.
+
+     list
+        List fleet namespaces in a project.
+
+     update
+        Update a fleet namespace.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub scopes namespaces
+
+        $ gcloud beta container hub scopes namespaces
+
diff --git a/gcloud/container/hub/scopes/namespaces/list b/gcloud/container/hub/scopes/namespaces/list
new file mode 100644
index 000000000..4988cf0f1
--- /dev/null
+++ b/gcloud/container/hub/scopes/namespaces/list
@@ -0,0 +1,94 @@
+NAME
+    gcloud container hub scopes namespaces list - list fleet namespaces in a
+        project
+
+SYNOPSIS
+    gcloud container hub scopes namespaces list --scope=SCOPE
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The user does not have access to the project specified.
+
+EXAMPLES
+    The following command lists namespaces in the active project:
+
+        $ gcloud container hub scopes namespaces list
+
+    The following command lists namespaces in project PROJECT_ID:
+
+        $ gcloud container hub scopes namespaces list --project=PROJECT_ID
+
+REQUIRED FLAGS
+     Scope resource - The group of arguments defining the Fleet Scope. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --scope on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --scope on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       --scope=SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument --scope on the command line.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub scopes namespaces list
+
+        $ gcloud beta container hub scopes namespaces list
+
diff --git a/gcloud/container/hub/scopes/namespaces/update b/gcloud/container/hub/scopes/namespaces/update
new file mode 100644
index 000000000..a780ec90b
--- /dev/null
+++ b/gcloud/container/hub/scopes/namespaces/update
@@ -0,0 +1,139 @@
+NAME
+    gcloud container hub scopes namespaces update - update a fleet namespace
+
+SYNOPSIS
+    gcloud container hub scopes namespaces update (NAMESPACE : --scope=SCOPE)
+        [--update-labels=[KEY=VALUE,...]]
+        [--update-namespace-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]]
+        [--clear-namespace-labels | --remove-namespace-labels=[KEY,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The fleet namespace does not exist in the project.
+      ▪ The caller does not have permission to access the project or
+        namespace.
+
+EXAMPLES
+    To update the namespace NAMESPACE in the active project:
+
+        $ gcloud container hub scopes namespaces update NAMESPACE
+
+    To update the namespace NAMESPACE in project PROJECT_ID:
+
+        $ gcloud container hub scopes namespaces update NAMESPACE \
+            --project=PROJECT_ID
+
+POSITIONAL ARGUMENTS
+     Namespace resource - The group of arguments defining the Fleet Namespace.
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument NAMESPACE on the command line with a fully
+        specified name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       NAMESPACE
+          ID of the namespace or fully qualified identifier for the namespace.
+
+          To set the namespace attribute:
+          ▸ provide the argument NAMESPACE on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --scope=SCOPE
+          the
+
+          To set the scope attribute:
+          ▸ provide the argument NAMESPACE on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+FLAGS
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     --update-namespace-labels=[KEY=VALUE,...]
+        List of namespace-level label KEY=VALUE pairs to update in the cluster
+        namespace. If a label exists, its value is modified. Otherwise, a new
+        label is' created.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud container hub scopes namespaces update --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud container hub scopes namespaces update --clear-labels \
+                --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+     At most one of these can be specified:
+
+       --clear-namespace-labels
+          Remove all namespace-level labels from the cluster namespace. If
+          --update-namespace-labels is also specified then
+          --clear-namespace-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud container hub scopes namespaces update namespace_name \
+                --clear-namespace-labels
+
+          To remove all existing namespace-level labels and create two new
+          labels, foo and baz:
+
+              $ gcloud container hub scopes namespaces update namespace_name \
+                --clear-namespace-labels \
+                --update-namespace-labels foo=bar,baz=qux
+
+       --remove-namespace-labels=[KEY,...]
+          List of namespace-level label keys to remove in the cluster
+          namespace. If a label does not exist it is silently ignored. If
+          --update-namespace-labels is also specified then
+          --update-namespace-labels is applied first.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub scopes namespaces update
+
+        $ gcloud beta container hub scopes namespaces update
+
diff --git a/gcloud/container/hub/scopes/rbacrolebindings/create b/gcloud/container/hub/scopes/rbacrolebindings/create
new file mode 100644
index 000000000..2dfb79c85
--- /dev/null
+++ b/gcloud/container/hub/scopes/rbacrolebindings/create
@@ -0,0 +1,105 @@
+NAME
+    gcloud container hub scopes rbacrolebindings create - create an RBAC
+        RoleBinding
+
+SYNOPSIS
+    gcloud container hub scopes rbacrolebindings create
+        (NAME : --location=LOCATION --scope=SCOPE) --role=ROLE
+        (--group=GROUP | --user=USER) [--labels=[KEY=VALUE,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The RBAC RoleBinding already exists.
+      ▪ The caller does not have permission to access the given scope.
+
+EXAMPLES
+    To create an admin RBAC RoleBinding RBRB in scope SCOPE for user
+    person@google.com, run:
+
+        $ gcloud container hub scopes rbacrolebindings create RBRB \
+            --scope=SCOPE --role=admin --user=person@google.com
+
+    To create a viewer RBAC RoleBinding RBRB in scope SCOPE for group
+    people@google.com, run:
+
+        $ gcloud container hub scopes rbacrolebindings create RBRB \
+            --scope=SCOPE --role=viewer --group=people@google.com
+
+POSITIONAL ARGUMENTS
+     Rbacrolebinding resource - The group of arguments defining an
+     RBACRoleBinding. The arguments in this group can be used to specify the
+     attributes of this resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAME on the command line with a fully specified
+        name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       NAME
+          ID of the rbacrolebinding or fully qualified identifier for the
+          rbacrolebinding.
+
+          To set the rbacrolebinding attribute:
+          ▸ provide the argument NAME on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the rbacrolebinding.
+
+          To set the location attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --scope=SCOPE
+          Name of the rbacrolebinding.
+
+          To set the scope attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+REQUIRED FLAGS
+     --role=ROLE
+        Role to assign. ROLE must be one of: admin, edit, view.
+
+     Exactly one of these must be specified:
+
+       --group=GROUP
+          Group for the RoleBinding.
+
+       --user=USER
+          User for the RoleBinding.
+
+OPTIONAL FLAGS
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub scopes rbacrolebindings create
+
+        $ gcloud beta container hub scopes rbacrolebindings create
+
diff --git a/gcloud/container/hub/scopes/rbacrolebindings/delete b/gcloud/container/hub/scopes/rbacrolebindings/delete
new file mode 100644
index 000000000..988195c48
--- /dev/null
+++ b/gcloud/container/hub/scopes/rbacrolebindings/delete
@@ -0,0 +1,75 @@
+NAME
+    gcloud container hub scopes rbacrolebindings delete - delete a fleet scope
+        RBAC RoleBinding
+
+SYNOPSIS
+    gcloud container hub scopes rbacrolebindings delete
+        (NAME : --location=LOCATION --scope=SCOPE) [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The RoleBinding specified does not exist.
+      ▪ The caller does not have permission to access the given RoleBinding.
+
+EXAMPLES
+    To delete RBAC RoleBinding RBRB in scope SCOPE in the active project:
+
+        $ gcloud container hub scopes rbacrolebindings delete RBRB \
+            --scope=SCOPE
+
+POSITIONAL ARGUMENTS
+     Rbacrolebinding resource - The group of arguments defining an
+     RBACRoleBinding. The arguments in this group can be used to specify the
+     attributes of this resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAME on the command line with a fully specified
+        name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       NAME
+          ID of the rbacrolebinding or fully qualified identifier for the
+          rbacrolebinding.
+
+          To set the rbacrolebinding attribute:
+          ▸ provide the argument NAME on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the rbacrolebinding.
+
+          To set the location attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --scope=SCOPE
+          Name of the rbacrolebinding.
+
+          To set the scope attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub scopes rbacrolebindings delete
+
+        $ gcloud beta container hub scopes rbacrolebindings delete
+
diff --git a/gcloud/container/hub/scopes/rbacrolebindings/describe b/gcloud/container/hub/scopes/rbacrolebindings/describe
new file mode 100644
index 000000000..7f682a8b6
--- /dev/null
+++ b/gcloud/container/hub/scopes/rbacrolebindings/describe
@@ -0,0 +1,75 @@
+NAME
+    gcloud container hub scopes rbacrolebindings describe - show fleet scope
+        RBAC RoleBinding information
+
+SYNOPSIS
+    gcloud container hub scopes rbacrolebindings describe
+        (NAME : --location=LOCATION --scope=SCOPE) [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The RoleBinding specified does not exist in the project.
+      ▪ The caller does not have permission to access the RoleBinding.
+
+EXAMPLES
+    To print metadata for RBAC RoleBinding RBRB in the scope SCOPE, run:
+
+        $ gcloud container hub scopes rbacrolebindings describe RBRB \
+            --scope=SCOPE
+
+POSITIONAL ARGUMENTS
+     Rbacrolebinding resource - The group of arguments defining an
+     RBACRoleBinding. The arguments in this group can be used to specify the
+     attributes of this resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAME on the command line with a fully specified
+        name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       NAME
+          ID of the rbacrolebinding or fully qualified identifier for the
+          rbacrolebinding.
+
+          To set the rbacrolebinding attribute:
+          ▸ provide the argument NAME on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the rbacrolebinding.
+
+          To set the location attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --scope=SCOPE
+          Name of the rbacrolebinding.
+
+          To set the scope attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub scopes rbacrolebindings describe
+
+        $ gcloud beta container hub scopes rbacrolebindings describe
+
diff --git a/gcloud/container/hub/scopes/rbacrolebindings/help b/gcloud/container/hub/scopes/rbacrolebindings/help
new file mode 100644
index 000000000..ff64e6b85
--- /dev/null
+++ b/gcloud/container/hub/scopes/rbacrolebindings/help
@@ -0,0 +1,46 @@
+NAME
+    gcloud container hub scopes rbacrolebindings - fleet scope RBAC
+        RoleBindings for permissions
+
+SYNOPSIS
+    gcloud container hub scopes rbacrolebindings COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command group allows for manipulation of fleet namespace RBAC
+    RoleBindings.
+
+EXAMPLES
+    Manage RBAC RoleBindings:
+
+        $ gcloud container hub scopes rbacrolebindings --help
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        Create an RBAC RoleBinding.
+
+     delete
+        Delete a fleet scope RBAC RoleBinding.
+
+     describe
+        Show fleet scope RBAC RoleBinding information.
+
+     list
+        List RBAC RoleBindings in a fleet scope.
+
+     update
+        Update a fleet scope RBAC RoleBinding.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub scopes rbacrolebindings
+
+        $ gcloud beta container hub scopes rbacrolebindings
+
diff --git a/gcloud/container/hub/scopes/rbacrolebindings/list b/gcloud/container/hub/scopes/rbacrolebindings/list
new file mode 100644
index 000000000..f898455fd
--- /dev/null
+++ b/gcloud/container/hub/scopes/rbacrolebindings/list
@@ -0,0 +1,72 @@
+NAME
+    gcloud container hub scopes rbacrolebindings list - list RBAC RoleBindings
+        in a fleet scope
+
+SYNOPSIS
+    gcloud container hub scopes rbacrolebindings list --scope=SCOPE
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The scope specified does not exist.
+      ▪ The user does not have access to the specified scope.
+
+EXAMPLES
+    The following command lists RBAC RoleBindings in scope SCOPE in project
+    PROJECT_ID:
+
+        $ gcloud container hub scopes rbacrolebindings list --scope=SCOPE \
+            --project=PROJECT_ID
+
+REQUIRED FLAGS
+     --scope=SCOPE
+        Name of the fleet scope to list RBAC RoleBindings from.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub scopes rbacrolebindings list
+
+        $ gcloud beta container hub scopes rbacrolebindings list
+
diff --git a/gcloud/container/hub/scopes/rbacrolebindings/update b/gcloud/container/hub/scopes/rbacrolebindings/update
new file mode 100644
index 000000000..d6f9a6608
--- /dev/null
+++ b/gcloud/container/hub/scopes/rbacrolebindings/update
@@ -0,0 +1,127 @@
+NAME
+    gcloud container hub scopes rbacrolebindings update - update a fleet scope
+        RBAC RoleBinding
+
+SYNOPSIS
+    gcloud container hub scopes rbacrolebindings update
+        (NAME : --location=LOCATION --scope=SCOPE) [--role=ROLE]
+        [--update-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]]
+        [--group=GROUP | --user=USER] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The RoleBinding does not exist in the project.
+      ▪ The caller does not have permission to access the RoleBinding.
+
+EXAMPLES
+    To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to
+    the viewer role:
+
+        $ gcloud container hub scopes rbacrolebindings update RBRB \
+            --scope=SCOPE --role=viewer
+
+    To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to
+    the user someone@google.com:
+
+        $ gcloud container hub scopes rbacrolebindings update RBRB \
+            --scope=SCOPE --user=someone@google.com
+
+POSITIONAL ARGUMENTS
+     Rbacrolebinding resource - The group of arguments defining an
+     RBACRoleBinding. The arguments in this group can be used to specify the
+     attributes of this resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument NAME on the command line with a fully specified
+        name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       NAME
+          ID of the rbacrolebinding or fully qualified identifier for the
+          rbacrolebinding.
+
+          To set the rbacrolebinding attribute:
+          ▸ provide the argument NAME on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location for the rbacrolebinding.
+
+          To set the location attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkehub/location.
+
+       --scope=SCOPE
+          Name of the rbacrolebinding.
+
+          To set the scope attribute:
+          ▸ provide the argument NAME on the command line with a fully
+            specified name;
+          ▸ provide the argument --scope on the command line.
+
+FLAGS
+     --role=ROLE
+        Role for the RBACRoleBinding to update to. ROLE must be one of: admin,
+        edit, view.
+
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud container hub scopes rbacrolebindings update --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud container hub scopes rbacrolebindings update \
+                --clear-labels --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+     At most one of these can be specified:
+
+       --group=GROUP
+          Group for the RBACRoleBinding to update to.
+
+       --user=USER
+          User for the RBACRoleBinding to update to.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub scopes rbacrolebindings update
+
+        $ gcloud beta container hub scopes rbacrolebindings update
+
diff --git a/gcloud/container/hub/scopes/remove-iam-policy-binding b/gcloud/container/hub/scopes/remove-iam-policy-binding
new file mode 100644
index 000000000..d5ae9a981
--- /dev/null
+++ b/gcloud/container/hub/scopes/remove-iam-policy-binding
@@ -0,0 +1,89 @@
+NAME
+    gcloud container hub scopes remove-iam-policy-binding - remove IAM policy
+        binding of a Fleet Scope
+
+SYNOPSIS
+    gcloud container hub scopes remove-iam-policy-binding SCOPE
+        --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Remove an IAM policy binding from the IAM policy of a scope. One binding
+    consists of a member, and a role.
+
+EXAMPLES
+    To remove an IAM policy binding for the role of 'roles/gkehub.scopeUser'
+    for the user 'test-user@gmail.com' with scope 'my-scope', run:
+
+        $ gcloud container hub scopes remove-iam-policy-binding my-scope \
+            --member='user:test-user@gmail.com' \
+            --role='roles/gkehub.scopeUser'
+
+    See https://cloud.google.com/iam/docs/managing-policies for details of
+    policy role and member types.
+
+POSITIONAL ARGUMENTS
+     Scope resource - The scope for which to remove IAM policy binding from.
+     This represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     To set the location attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ global is the only supported location.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+REQUIRED FLAGS
+     --member=PRINCIPAL
+        The principal to remove the binding for. Should be of the form
+        user|group|serviceAccount:email or domain:domain.
+
+        Examples: user:test-user@gmail.com, group:admins@example.com,
+        serviceAccount:test123@example.domain.com, or
+        domain:example.domain.com.
+
+        Deleted principals have an additional deleted: prefix and a ?uid=UID
+        suffix, where UID is a unique identifier for the principal. Example:
+        deleted:user:test-user@gmail.com?uid=123456789012345678901.
+
+        Some resources also accept the following special values:
+        ◆ allUsers - Special identifier that represents anyone who is on the
+          internet, with or without a Google account.
+        ◆ allAuthenticatedUsers - Special identifier that represents anyone
+          who is authenticated with a Google account or a service account.
+
+     --role=ROLE
+        The role to remove the principal from.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1 API. The full documentation for this API
+    can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub scopes remove-iam-policy-binding
+
+        $ gcloud beta container hub scopes remove-iam-policy-binding
+
diff --git a/gcloud/container/hub/scopes/update b/gcloud/container/hub/scopes/update
new file mode 100644
index 000000000..ed059dca0
--- /dev/null
+++ b/gcloud/container/hub/scopes/update
@@ -0,0 +1,227 @@
+NAME
+    gcloud container hub scopes update - update a scope
+
+SYNOPSIS
+    gcloud container hub scopes update (SCOPE : --location=LOCATION)
+        [--update-labels=[KEY=VALUE,...]]
+        [--update-namespace-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]]
+        [--clear-namespace-labels | --remove-namespace-labels=[KEY,...]]
+        [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING
+          --remove-upgrade-soaking-overrides
+          | --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE
+          --upgrade-selector=[name=NAME],[version=VERSION]
+          --reset-upstream-scope | --upstream-scope=UPSTREAM_SCOPE]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Update an existing Fleet Scope.
+
+EXAMPLES
+    First retrieve the ID of the scope using the command below.
+
+        $ gcloud container hub scopes list
+
+    Update a scope.
+
+        $ gcloud container hub scopes update SCOPE_NAME
+
+POSITIONAL ARGUMENTS
+     Scope resource - fleet scope resource. The arguments in this group can be
+     used to specify the attributes of this resource. (NOTE) Some attributes
+     are not given arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument scope on the command line with a fully specified
+        name;
+      ◆ set the property core/project;
+      ◆ provide the argument --project on the command line.
+
+     This must be specified.
+
+       SCOPE
+          ID of the scope or fully qualified identifier for the scope.
+
+          To set the scope attribute:
+          ▸ provide the argument scope on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location name.
+
+          To set the location attribute:
+          ▸ provide the argument scope on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ global is the only supported location.
+
+FLAGS
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     --update-namespace-labels=[KEY=VALUE,...]
+        List of scope-level label KEY=VALUE pairs to update in the cluster
+        namespace. If a label exists, its value is modified. Otherwise, a new
+        label is' created.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud container hub scopes update --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud container hub scopes update --clear-labels \
+                --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+     At most one of these can be specified:
+
+       --clear-namespace-labels
+          Remove all scope-level labels from the cluster namespace. If
+          --update-namespace-labels is also specified then
+          --clear-namespace-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud container hub scopes update scope_name \
+                --clear-namespace-labels
+
+          To remove all existing scope-level labels and create two new labels,
+          foo and baz:
+
+              $ gcloud container hub scopes update scope_name \
+                --clear-namespace-labels \
+                --update-namespace-labels foo=bar,baz=qux
+
+       --remove-namespace-labels=[KEY,...]
+          List of scope-level label keys to remove in the cluster namespace. If
+          a label does not exist it is silently ignored. If
+          --update-namespace-labels is also specified then
+          --update-namespace-labels is applied first.
+
+     Rollout Sequencing
+
+       --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING
+          Configures the default soaking duration for each upgrade propagating
+          through the current scope to become "COMPLETE". Soaking begins after
+          all clusters in the scope are on the target version, or after 30 days
+          if all cluster upgrades are not complete. Once an upgrade state
+          becomes "COMPLETE", it will automatically be propagated to the
+          downstream scope. Max is 30 days.
+
+          See $ gcloud topic datetimes for information on duration formats.
+
+          To configure Rollout Sequencing for a given scope, SCOPE_NAME, this
+          attribute must be set. To do this while specifying a default soaking
+          duration of 7 days, run:
+
+              $ gcloud container hub scopes update SCOPE_NAME \
+                  default-upgrade-soaking=7d
+
+       At most one of these can be specified:
+
+         --remove-upgrade-soaking-overrides
+            Removes soaking time overrides for all upgrades propagating through
+            the current scope. Consequently, all upgrades will follow the soak
+            time configured by --default-upgrade-soaking until new overrides
+            are configured with --add_upgrade_soaking_override and
+            --upgrade_selector.
+
+            To remove all soaking time overrides configured for SCOPE_NAME,
+            run:
+
+                $ gcloud container hub scopes update SCOPE_NAME \
+                    --remove-upgrade-soaking-overrides
+
+         Upgrade soaking override.
+
+         Defines a specific soaking time override for a particular upgrade
+         propagating through the current scope that supercedes the default
+         soaking duration configured by --default-upgrade-soaking.
+
+         To set an upgrade soaking override of 12 hours for the upgrade with
+         name, k8s_control_plane, and version, 1.23.1-gke.1000, run:
+
+             $ gcloud container hub scopes update SCOPE_NAME \
+               --add-upgrade-soaking-override=12h \
+               --upgrade-selector=name="k8s_control_plane",version="1.23.1-gke.1000"
+
+           --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE
+              Overrides the soaking time for a particular upgrade name and
+              version propagating through the current scope. Set soaking to 0
+              days to bypass soaking and fast-forward the upgrade to the
+              downstream scope.
+
+              See $ gcloud topic datetimes for information on duration formats.
+
+              This flag argument must be specified if any of the other
+              arguments in this group are specified.
+
+           --upgrade-selector=[name=NAME],[version=VERSION]
+              Name and version of the upgrade to be overridden where version is
+              a full GKE version. Currently, name can be either
+              k8s_control_plane or k8s_node.
+
+              This flag argument must be specified if any of the other
+              arguments in this group are specified.
+
+       At most one of these can be specified:
+
+         --reset-upstream-scope
+            Clears the relationship between the current scope and its upstream
+            scope in the rollout sequence.
+
+            To remove the link between SCOPE_NAME and its upstream scope, run:
+
+                $ gcloud container hub scopes update SCOPE_NAME \
+                    --reset-upstream-scope
+
+         --upstream-scope=UPSTREAM_SCOPE
+            Full resource name of the upstream scope in the format of
+            projects/{project}/locations/{location}/scopes/{scope}. GKE will
+            finish upgrades on the upstream scope before applying the same
+            upgrades to the current scope.
+
+            To configure the upstream scope for SCOPE_NAME, run:
+
+                $ gcloud container hub scopes update SCOPE_NAME \
+                  --upstream-scope=projects/{upstream_project}/locations/global/scopes/{upstream_scope}
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkehub/v1 API. The full documentation for this API
+    can be found at:
+    https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub scopes update
+
+        $ gcloud beta container hub scopes update
+
diff --git a/gcloud/container/hub/update b/gcloud/container/hub/update
new file mode 100644
index 000000000..e29831707
--- /dev/null
+++ b/gcloud/container/hub/update
@@ -0,0 +1,98 @@
+NAME
+    gcloud container hub update - update a fleet
+
+SYNOPSIS
+    gcloud container hub update [--async] [--display-name=DISPLAY_NAME]
+        [--update-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]]
+        [--security-posture=SECURITY_POSTURE
+          --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    This command can fail for the following reasons:
+      ▪ The project specified does not exist.
+      ▪ The project specified already has a fleet.
+      ▪ The active account does not have permission to access the given
+        project.
+
+EXAMPLES
+    To update the display name of the fleet in project example-foo-bar-1 to
+    updated-name, run:
+
+        $ gcloud container hub update --display-name=updated-name \
+            --project=example-foo-bar-1
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --display-name=DISPLAY_NAME
+        Display name of the fleet to be created (optional). 4-30 characters,
+        alphanumeric and [ '"!-] only.
+
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud container hub update --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud container hub update --clear-labels \
+                --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+     Default cluster configurations to apply across the fleet.
+
+       Security posture config.
+
+         --security-posture=SECURITY_POSTURE
+            To apply basic security posture to the clusters of the fleet,
+
+                $ gcloud container hub update --security-posture=basic
+
+            SECURITY_POSTURE must be one of: disabled, basic, enterprise.
+
+         --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING
+            To apply basic vulnerability scanning to the clusters of the fleet,
+
+                $ gcloud container hub update \
+                    --workload-vulnerability-scanning=disabled
+
+            WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, basic,
+            enterprise.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha container hub update
+
+        $ gcloud beta container hub update
+
diff --git a/gcloud/dataplex/assets/create b/gcloud/dataplex/assets/create
index cf46c9c3e..a9a567e07 100644
--- a/gcloud/dataplex/assets/create
+++ b/gcloud/dataplex/assets/create
@@ -4,8 +4,9 @@ NAME
 SYNOPSIS
     gcloud dataplex assets create
         (ASSET : --lake=LAKE --location=LOCATION --zone=ZONE)
-        (--resource-type=RESOURCE_TYPE : --resource-name=RESOURCE_NAME)
-        [--async] [--description=DESCRIPTION] [--display-name=DISPLAY_NAME]
+        (--resource-type=RESOURCE_TYPE : --resource-name=RESOURCE_NAME
+          --resource-read-access-mode=RESOURCE_READ_ACCESS_MODE) [--async]
+        [--description=DESCRIPTION] [--display-name=DISPLAY_NAME]
         [--labels=[KEY=VALUE,...]] [--validate-only]
         [--[no-]discovery-enabled
           --discovery-exclude-patterns=[EXCLUDE_PATTERNS,...]
@@ -119,6 +120,14 @@ REQUIRED FLAGS
           projects/{project_number}/buckets/{bucket_id} or
           projects/{project_number}/datasets/{dataset_id}
 
+       --resource-read-access-mode=RESOURCE_READ_ACCESS_MODE
+          Read access mode. RESOURCE_READ_ACCESS_MODE must be one of:
+
+           DIRECT
+              Data is accessed directly using storage APIs
+           MANAGED
+              Data is accessed through a managed interface using BigQuery APIs.
+
 OPTIONAL FLAGS
      --async
         Return immediately, without waiting for the operation in progress to
diff --git a/gcloud/dataplex/assets/update b/gcloud/dataplex/assets/update
index de46afa26..0d40fe1b1 100644
--- a/gcloud/dataplex/assets/update
+++ b/gcloud/dataplex/assets/update
@@ -5,7 +5,9 @@ SYNOPSIS
     gcloud dataplex assets update
         (ASSET : --lake=LAKE --location=LOCATION --zone=ZONE) [--async]
         [--description=DESCRIPTION] [--display-name=DISPLAY_NAME]
-        [--labels=[KEY=VALUE,...]] [--validate-only]
+        [--labels=[KEY=VALUE,...]]
+        [--resource-read-access-mode=RESOURCE_READ_ACCESS_MODE]
+        [--validate-only]
         [--[no-]discovery-enabled
           --discovery-exclude-patterns=[EXCLUDE_PATTERNS,...]
           --discovery-include-patterns=[INCLUDE_PATTERNS,...]
@@ -95,6 +97,16 @@ FLAGS
         contain only hyphens (-), underscores (_), lowercase characters, and
         numbers.
 
+     Specification of the resource that is referenced by this asset.
+
+       --resource-read-access-mode=RESOURCE_READ_ACCESS_MODE
+          Read access mode. RESOURCE_READ_ACCESS_MODE must be one of:
+
+           DIRECT
+              Data is accessed directly using storage APIs
+           MANAGED
+              Data is accessed through a managed interface using BigQuery APIs.
+
      --validate-only
         Validate the update action, but don't actually perform it.
 
diff --git a/gcloud/dataplex/datascans/create/data-profile b/gcloud/dataplex/datascans/create/data-profile
index 9500956f0..fb8ea0685 100644
--- a/gcloud/dataplex/datascans/create/data-profile
+++ b/gcloud/dataplex/datascans/create/data-profile
@@ -11,6 +11,7 @@ SYNOPSIS
         [--labels=[KEY=VALUE,...]] [--async | --validate-only]
         [--data-profile-spec-file=DATA_PROFILE_SPEC_FILE
           | --exclude-field-names=EXCLUDE_FIELD_NAMES
+          --export-results-table=EXPORT_RESULTS_TABLE
           --include-field-names=INCLUDE_FIELD_NAMES
           --row-filter=ROW_FILTER --sampling-percent=SAMPLING_PERCENT]
         [--incremental-field=INCREMENTAL_FIELD --on-demand=ON_DEMAND
@@ -25,7 +26,7 @@ EXAMPLES
     To create a data profile scan data-profile-datascan in project test-project
     located in us-central1, run:
 
-        $ gcloud dataplex datascans create data-profile data-profile \
+        $ gcloud dataplex datascans create data-profile \
             data-profile-datascan --project=test-project \
             --location=us-central1
 
@@ -119,6 +120,12 @@ OPTIONAL FLAGS
             respective fields will be excluded from data profile, regardless of
             the fields specified in the --include-field-names flag.
 
+         --export-results-table=EXPORT_RESULTS_TABLE
+            path to the resource table to export data profile scan results, of
+            the form:
+            //bigquery.googleapis.com/projects/{project_number}/datasets/{dataset_id}/tables/{table_id}.
+            The table will be created if not present.
+
          --include-field-names=INCLUDE_FIELD_NAMES
             Names of the fields to include in data profile. If not specified,
             all fields at the time of profile scan job execution are included.
diff --git a/gcloud/dataplex/datascans/create/data-quality b/gcloud/dataplex/datascans/create/data-quality
index ef237da9e..197aa0b24 100644
--- a/gcloud/dataplex/datascans/create/data-quality
+++ b/gcloud/dataplex/datascans/create/data-quality
@@ -22,7 +22,7 @@ EXAMPLES
     To create a data quality scan data-quality-datascan in project test-project
     located in us-central1 with data spec file data-quality-spec.json, run:
 
-        $ gcloud dataplex datascans create data-quality data-quality \
+        $ gcloud dataplex datascans create data-quality \
             data-quality-datascan --project=test-project \
             --location=us-central1 \
             --data-quality-spec-file="data-quality-spec.json"
diff --git a/gcloud/dataplex/datascans/update/data-profile b/gcloud/dataplex/datascans/update/data-profile
index 9e1419aec..38ccc07e5 100644
--- a/gcloud/dataplex/datascans/update/data-profile
+++ b/gcloud/dataplex/datascans/update/data-profile
@@ -22,7 +22,7 @@ EXAMPLES
     To update description of a data profile scan data-profile-datascan in
     project test-project located in us-central1, run:
 
-        $ gcloud dataplex datascans update data-profile data-profile \
+        $ gcloud dataplex datascans update data-profile \
             data-profile-datascan --project=test-project \
             --location=us-central1 --description="Description is updated."
 
diff --git a/gcloud/dataplex/datascans/update/data-quality b/gcloud/dataplex/datascans/update/data-quality
index cb5363e1f..d5397fe5f 100644
--- a/gcloud/dataplex/datascans/update/data-quality
+++ b/gcloud/dataplex/datascans/update/data-quality
@@ -19,7 +19,7 @@ EXAMPLES
     To update description of a data quality scan data-quality-datascan in
     project test-project located in us-central1, run:
 
-        $ gcloud dataplex datascans update data-quality data-quality \
+        $ gcloud dataplex datascans update data-quality \
             data-quality-datascan --project=test-project \
             --location=us-central1 --description="Description is updated."
 
diff --git a/gcloud/dataplex/tasks/create b/gcloud/dataplex/tasks/create
index 1b9dcfc57..60cec91f9 100644
--- a/gcloud/dataplex/tasks/create
+++ b/gcloud/dataplex/tasks/create
@@ -4,7 +4,7 @@ NAME
 SYNOPSIS
     gcloud dataplex tasks create (TASK : --lake=LAKE --location=LOCATION)
         (--execution-service-account=EXECUTION_SERVICE_ACCOUNT
-          : --execution-args=EXECUTION_ARGS
+          : --execution-args=[KEY=VALUE,...]
           --execution-project=EXECUTION_PROJECT --kms-key=KMS_KEY
           --max-job-execution-lifetime=MAX_JOB_EXECUTION_LIFETIME)
         ([--notebook=NOTEBOOK
@@ -12,9 +12,9 @@ SYNOPSIS
           --notebook-file-uris=[NOTEBOOK_FILE_URIS,...]
           --notebook-batch-executors-count=NOTEBOOK_BATCH_EXECUTORS_COUNT
           --notebook-batch-max-executors-count=NOTEBOOK_BATCH_MAX_EXECUTORS_COUNT --notebook-container-image=NOTEBOOK_CONTAINER_IMAGE --notebook-container-image-java-jars=[NOTEBOOK_CONTAINER_IMAGE_JAVA_JARS,
-          ...]
-          --notebook-container-image-properties=NOTEBOOK_CONTAINER_IMAGE_PROPERTIES --notebook-vpc-network-tags=[NOTEBOOK_VPC_NETWORK_TAGS,
-          ...] --notebook-vpc-network-name=NOTEBOOK_VPC_NETWORK_NAME
+          ...] --notebook-container-image-properties=[KEY=VALUE,...]
+          --notebook-vpc-network-tags=[NOTEBOOK_VPC_NETWORK_TAGS,...]
+          --notebook-vpc-network-name=NOTEBOOK_VPC_NETWORK_NAME
           | --notebook-vpc-sub-network-name=NOTEBOOK_VPC_SUB_NETWORK_NAME]
           | [(--spark-main-class=SPARK_MAIN_CLASS
           | --spark-main-jar-file-uri=SPARK_MAIN_JAR_FILE_URI
@@ -27,7 +27,7 @@ SYNOPSIS
           --batch-max-executors-count=BATCH_MAX_EXECUTORS_COUNT
           --container-image=CONTAINER_IMAGE
           --container-image-java-jars=[CONTAINER_IMAGE_JAVA_JARS,...]
-          --container-image-properties=CONTAINER_IMAGE_PROPERTIES
+          --container-image-properties=[KEY=VALUE,...]
           --container-image-python-packages=[CONTAINER_IMAGE_PYTHON_PACKAGES,
           ...] --vpc-network-tags=[VPC_NETWORK_TAGS,...]
           --vpc-network-name=VPC_NETWORK_NAME
@@ -127,7 +127,7 @@ REQUIRED FLAGS
           This flag argument must be specified if any of the other arguments in
           this group are specified.
 
-       --execution-args=EXECUTION_ARGS
+       --execution-args=[KEY=VALUE,...]
           The arguments to pass to the task. The args can use placeholders of
           the format ${placeholder} as part of key/value string. These will be
           interpolated before passing the args to the driver. Currently
@@ -198,7 +198,7 @@ REQUIRED FLAGS
               Cloud Storage URIs to Jar binaries. For example,
               gs://bucket-name/my/path/to/file.jar
 
-           --notebook-container-image-properties=NOTEBOOK_CONTAINER_IMAGE_PROPERTIES
+           --notebook-container-image-properties=[KEY=VALUE,...]
               The properties to set on daemon config files. Property keys are
               specified in prefix:property format, for example
               core:hadoop.tmp.dir. For more information, see Cluster properties
@@ -278,7 +278,7 @@ REQUIRED FLAGS
               Cloud Storage URIs to Jar binaries. For example,
               gs://bucket-name/my/path/to/file.jar
 
-           --container-image-properties=CONTAINER_IMAGE_PROPERTIES
+           --container-image-properties=[KEY=VALUE,...]
               The properties to set on daemon config files. Property keys are
               specified in prefix:property format, for example
               core:hadoop.tmp.dir. For more information, see Cluster properties
diff --git a/gcloud/dataplex/tasks/update b/gcloud/dataplex/tasks/update
index 14ef04cad..b123a2fec 100644
--- a/gcloud/dataplex/tasks/update
+++ b/gcloud/dataplex/tasks/update
@@ -6,7 +6,7 @@ SYNOPSIS
         [--async] [--description=DESCRIPTION] [--display-name=DISPLAY_NAME]
         [--update-labels=[KEY=VALUE,...]]
         [--clear-labels | --remove-labels=[KEY,...]]
-        [--execution-args=EXECUTION_ARGS --execution-project=EXECUTION_PROJECT
+        [--execution-args=[KEY=VALUE,...] --execution-project=EXECUTION_PROJECT
           --execution-service-account=EXECUTION_SERVICE_ACCOUNT
           --kms-key=KMS_KEY
           --max-job-execution-lifetime=MAX_JOB_EXECUTION_LIFETIME]
@@ -15,9 +15,9 @@ SYNOPSIS
           --notebook-file-uris=[NOTEBOOK_FILE_URIS,...]
           --notebook-batch-executors-count=NOTEBOOK_BATCH_EXECUTORS_COUNT
           --notebook-batch-max-executors-count=NOTEBOOK_BATCH_MAX_EXECUTORS_COUNT --notebook-container-image=NOTEBOOK_CONTAINER_IMAGE --notebook-container-image-java-jars=[NOTEBOOK_CONTAINER_IMAGE_JAVA_JARS,
-          ...]
-          --notebook-container-image-properties=NOTEBOOK_CONTAINER_IMAGE_PROPERTIES --notebook-vpc-network-tags=[NOTEBOOK_VPC_NETWORK_TAGS,
-          ...] --notebook-vpc-network-name=NOTEBOOK_VPC_NETWORK_NAME
+          ...] --notebook-container-image-properties=[KEY=VALUE,...]
+          --notebook-vpc-network-tags=[NOTEBOOK_VPC_NETWORK_TAGS,...]
+          --notebook-vpc-network-name=NOTEBOOK_VPC_NETWORK_NAME
           | --notebook-vpc-sub-network-name=NOTEBOOK_VPC_SUB_NETWORK_NAME
           | --spark-archive-uris=[SPARK_ARCHIVE_URIS,...]
           --spark-file-uris=[SPARK_FILE_URIS,...]
@@ -25,7 +25,7 @@ SYNOPSIS
           --batch-max-executors-count=BATCH_MAX_EXECUTORS_COUNT
           --container-image=CONTAINER_IMAGE
           --container-image-java-jars=[CONTAINER_IMAGE_JAVA_JARS,...]
-          --container-image-properties=CONTAINER_IMAGE_PROPERTIES
+          --container-image-properties=[KEY=VALUE,...]
           --container-image-python-packages=[CONTAINER_IMAGE_PYTHON_PACKAGES,
           ...] --vpc-network-tags=[VPC_NETWORK_TAGS,...]
           --vpc-network-name=VPC_NETWORK_NAME
@@ -132,7 +132,7 @@ FLAGS
 
      Spec related to how a task is executed.
 
-       --execution-args=EXECUTION_ARGS
+       --execution-args=[KEY=VALUE,...]
           The arguments to pass to the task. The args can use placeholders of
           the format ${placeholder} as part of key/value string. These will be
           interpolated before passing the args to the driver. Currently
@@ -202,7 +202,7 @@ FLAGS
               Cloud Storage URIs to Jar binaries. For example,
               gs://bucket-name/my/path/to/file.jar
 
-           --notebook-container-image-properties=NOTEBOOK_CONTAINER_IMAGE_PROPERTIES
+           --notebook-container-image-properties=[KEY=VALUE,...]
               Override to common configuration of open source components
               installed on the Dataproc cluster. The properties to set on
               daemon config files. Property keys are specified in
@@ -256,7 +256,7 @@ FLAGS
               Cloud Storage URIs to Jar binaries. For example,
               gs://bucket-name/my/path/to/file.jar
 
-           --container-image-properties=CONTAINER_IMAGE_PROPERTIES
+           --container-image-properties=[KEY=VALUE,...]
               Override to common configuration of open source components
               installed on the Dataproc cluster. The properties to set on
               daemon config files. Property keys are specified in
diff --git a/gcloud/dataproc/clusters/create b/gcloud/dataproc/clusters/create
index 65b8ff2b7..57d2dabb4 100644
--- a/gcloud/dataproc/clusters/create
+++ b/gcloud/dataproc/clusters/create
@@ -63,7 +63,8 @@ SYNOPSIS
         [[--metric-sources=[METRIC_SOURCE,...]
           : --metric-overrides=[METRIC_SOURCE:INSTANCE:GROUP:METRIC,...]
           | --metric-overrides-file=METRIC_OVERRIDES_FILE]]
-        [--single-node | --num-secondary-workers=NUM_SECONDARY_WORKERS
+        [--single-node | --min-num-workers=MIN_NUM_WORKERS
+          --num-secondary-workers=NUM_SECONDARY_WORKERS
           --num-workers=NUM_WORKERS
           --secondary-worker-type=TYPE; default="preemptible"]
         [GCLOUD_WIDE_FLAG ...]
@@ -840,6 +841,10 @@ FLAGS
 
        Multi-node cluster flags
 
+         --min-num-workers=MIN_NUM_WORKERS
+            The minimum number of workers nodes to provision for cluster create
+            operations to succeed.
+
          --num-secondary-workers=NUM_SECONDARY_WORKERS
             The number of secondary worker nodes in the cluster.
 
diff --git a/gcloud/dataproc/workflow-templates/set-managed-cluster b/gcloud/dataproc/workflow-templates/set-managed-cluster
index 263371140..64d191c2f 100644
--- a/gcloud/dataproc/workflow-templates/set-managed-cluster
+++ b/gcloud/dataproc/workflow-templates/set-managed-cluster
@@ -49,7 +49,8 @@ SYNOPSIS
         [[--metric-sources=[METRIC_SOURCE,...]
           : --metric-overrides=[METRIC_SOURCE:INSTANCE:GROUP:METRIC,...]
           | --metric-overrides-file=METRIC_OVERRIDES_FILE]]
-        [--single-node | --num-secondary-workers=NUM_SECONDARY_WORKERS
+        [--single-node | --min-num-workers=MIN_NUM_WORKERS
+          --num-secondary-workers=NUM_SECONDARY_WORKERS
           --num-workers=NUM_WORKERS
           --secondary-worker-type=TYPE; default="preemptible"]
         [GCLOUD_WIDE_FLAG ...]
@@ -706,6 +707,10 @@ FLAGS
 
        Multi-node cluster flags
 
+         --min-num-workers=MIN_NUM_WORKERS
+            The minimum number of workers nodes to provision for cluster create
+            operations to succeed.
+
          --num-secondary-workers=NUM_SECONDARY_WORKERS
             The number of secondary worker nodes in the cluster.
 
diff --git a/gcloud/edge-cache/keysets/create b/gcloud/edge-cache/keysets/create
index 011746d50..75b785cb9 100644
--- a/gcloud/edge-cache/keysets/create
+++ b/gcloud/edge-cache/keysets/create
@@ -3,9 +3,10 @@ NAME
 
 SYNOPSIS
     gcloud edge-cache keysets create (KEYSET : --location=LOCATION) [--async]
-        [--description=DESCRIPTION] [--labels=KEY=VALUE]
-        [--public-key=PUBLIC_KEY]
-        [--validation-shared-key=VALIDATION_SHARED_KEY] [GCLOUD_WIDE_FLAG ...]
+        [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]]
+        [--public-key=[id=ID],[managed=MANAGED],[value=VALUE]]
+        [--validation-shared-key=[secret_version=SECRET_VERSION]]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     Create a new EdgeCacheKeyset resource.
@@ -56,10 +57,10 @@ FLAGS
      --description=DESCRIPTION
         Human-readable description of the resource.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of KEY=VALUE labels to attach to this resource.
 
-     --public-key=PUBLIC_KEY
+     --public-key=[id=ID],[managed=MANAGED],[value=VALUE]
         Set of public keys to use for validating signed requests, when
         associated with a route. This flag can be repeated to create a Keyset
         with multiple public keys.
@@ -89,7 +90,7 @@ FLAGS
 
         At least one of public-key or validation-shared-key must be specified.
 
-     --validation-shared-key=VALIDATION_SHARED_KEY
+     --validation-shared-key=[secret_version=SECRET_VERSION]
         An ordered list of shared keys to use for validating signed requests.
 
         To create a validation shared key pointing to a Secret Manager secret
diff --git a/gcloud/edge-cache/keysets/update b/gcloud/edge-cache/keysets/update
index 79bd64787..567518dcd 100644
--- a/gcloud/edge-cache/keysets/update
+++ b/gcloud/edge-cache/keysets/update
@@ -3,9 +3,10 @@ NAME
 
 SYNOPSIS
     gcloud edge-cache keysets update (KEYSET : --location=LOCATION) [--async]
-        [--description=DESCRIPTION] [--labels=KEY=VALUE]
-        [--public-key=PUBLIC_KEY]
-        [--validation-shared-key=VALIDATION_SHARED_KEY] [GCLOUD_WIDE_FLAG ...]
+        [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]]
+        [--public-key=[id=ID],[managed=MANAGED],[value=VALUE]]
+        [--validation-shared-key=[secret_version=SECRET_VERSION]]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     Update an existing EdgeCacheKeyset resource.
@@ -69,10 +70,10 @@ FLAGS
      --description=DESCRIPTION
         Human-readable description of the resource.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of KEY=VALUE labels to attach to this resource.
 
-     --public-key=PUBLIC_KEY
+     --public-key=[id=ID],[managed=MANAGED],[value=VALUE]
         Set of public keys to use for validating signed requests, when
         associated with a route. This flag can be repeated to create a Keyset
         with multiple public keys.
@@ -102,7 +103,7 @@ FLAGS
 
         At least one of public-key or validation-shared-key must be specified.
 
-     --validation-shared-key=VALIDATION_SHARED_KEY
+     --validation-shared-key=[secret_version=SECRET_VERSION]
         An ordered list of shared keys to use for validating signed requests.
 
         To create a validation shared key pointing to a Secret Manager secret
diff --git a/gcloud/edge-cache/origins/create b/gcloud/edge-cache/origins/create
index 6934a67ea..efe8d730c 100644
--- a/gcloud/edge-cache/origins/create
+++ b/gcloud/edge-cache/origins/create
@@ -4,7 +4,7 @@ NAME
 SYNOPSIS
     gcloud edge-cache origins create (ORIGIN : --location=LOCATION)
         --origin-address=ORIGIN_ADDRESS [--async] [--description=DESCRIPTION]
-        [--failover-origin=FAILOVER_ORIGIN] [--labels=KEY=VALUE]
+        [--failover-origin=FAILOVER_ORIGIN] [--labels=[KEY=VALUE,...]]
         [--max-attempts=MAX_ATTEMPTS] [--port=PORT] [--protocol=PROTOCOL]
         [--response-timeout=RESPONSE_TIMEOUT]
         [--retry-conditions=[RETRY_CONDITIONS,...]] [GCLOUD_WIDE_FLAG ...]
@@ -89,7 +89,7 @@ OPTIONAL FLAGS
         The value of timeout.maxAttemptsTimeout dictates the timeout across all
         origins.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of KEY=VALUE labels to attach to this resource.
 
      --max-attempts=MAX_ATTEMPTS
diff --git a/gcloud/edge-cache/origins/update b/gcloud/edge-cache/origins/update
index cf205492e..9f8ef2633 100644
--- a/gcloud/edge-cache/origins/update
+++ b/gcloud/edge-cache/origins/update
@@ -4,7 +4,7 @@ NAME
 SYNOPSIS
     gcloud edge-cache origins update (ORIGIN : --location=LOCATION) [--async]
         [--description=DESCRIPTION] [--failover-origin=FAILOVER_ORIGIN]
-        [--labels=KEY=VALUE] [--max-attempts=MAX_ATTEMPTS]
+        [--labels=[KEY=VALUE,...]] [--max-attempts=MAX_ATTEMPTS]
         [--origin-address=ORIGIN_ADDRESS] [--port=PORT] [--protocol=PROTOCOL]
         [--response-timeout=RESPONSE_TIMEOUT]
         [--retry-conditions=[RETRY_CONDITIONS,...]] [GCLOUD_WIDE_FLAG ...]
@@ -72,7 +72,7 @@ FLAGS
         The value of timeout.maxAttemptsTimeout dictates the timeout across all
         origins.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of KEY=VALUE labels to attach to this resource.
 
      --max-attempts=MAX_ATTEMPTS
diff --git a/gcloud/edge-cache/services/update b/gcloud/edge-cache/services/update
index df44297c6..b67e1a168 100644
--- a/gcloud/edge-cache/services/update
+++ b/gcloud/edge-cache/services/update
@@ -6,7 +6,7 @@ SYNOPSIS
         [--description=DESCRIPTION]
         [--edge-security-policy=EDGE_SECURITY_POLICY]
         [--edge-ssl-certificate=[EDGE_SSL_CERTIFICATE,...]] [--enable-logging]
-        [--labels=KEY=VALUE] [--logging-sample-rate=LOGGING_SAMPLE_RATE]
+        [--labels=[KEY=VALUE,...]] [--logging-sample-rate=LOGGING_SAMPLE_RATE]
         [--require-tls] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -85,7 +85,7 @@ FLAGS
 
         Defaults to false.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of KEY=VALUE labels to attach to this resource.
 
      --logging-sample-rate=LOGGING_SAMPLE_RATE
diff --git a/gcloud/filestore/backups/create b/gcloud/filestore/backups/create
index a93511c43..3b6a89806 100644
--- a/gcloud/filestore/backups/create
+++ b/gcloud/filestore/backups/create
@@ -6,7 +6,7 @@ SYNOPSIS
         --instance=INSTANCE --region=REGION
         (--instance-location=INSTANCE_LOCATION | --instance-zone=INSTANCE_ZONE)
         [--async] [--description=DESCRIPTION] [--kms-key=KMS_KEY]
-        [--labels=KEY=VALUE] [GCLOUD_WIDE_FLAG ...]
+        [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     Create a Filestore backup of an instance file share.
@@ -60,7 +60,7 @@ OPTIONAL FLAGS
         CMEK for backup in the form of
         projects/{project}/locations/{location}/keyRings/{key-ring}/cryptoKeys/{crypto-key}
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
 GCLOUD WIDE FLAGS
diff --git a/gcloud/filestore/instances/snapshots/create b/gcloud/filestore/instances/snapshots/create
index ba5a32cf0..974bdabaa 100644
--- a/gcloud/filestore/instances/snapshots/create
+++ b/gcloud/filestore/instances/snapshots/create
@@ -5,7 +5,8 @@ SYNOPSIS
     gcloud filestore instances snapshots create SNAPSHOT --instance=INSTANCE
         (--instance-location=INSTANCE_LOCATION
           | --instance-region=INSTANCE_REGION) [--async]
-        [--description=DESCRIPTION] [--labels=KEY=VALUE] [GCLOUD_WIDE_FLAG ...]
+        [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     Create a Filestore snapshot of an instance.
@@ -47,7 +48,7 @@ OPTIONAL FLAGS
      --description=DESCRIPTION
         Description of the snapshot. Limit: 2048 characters.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
 GCLOUD WIDE FLAGS
diff --git a/gcloud/firestore/indexes/composite/create b/gcloud/firestore/indexes/composite/create
index 80a62cb73..eab9cf98a 100644
--- a/gcloud/firestore/indexes/composite/create
+++ b/gcloud/firestore/indexes/composite/create
@@ -2,7 +2,9 @@ NAME
     gcloud firestore indexes composite create - create a new composite index
 
 SYNOPSIS
-    gcloud firestore indexes composite create --field-config=FIELD_CONFIG
+    gcloud firestore indexes composite create
+        --field-config=[array-config=ARRAY-CONFIG],
+          [field-path=FIELD-PATH],[order=ORDER]
         (--collection-group=COLLECTION_GROUP : --database=DATABASE)
         [--api-scope=API_SCOPE; default="any-api"] [--async]
         [--query-scope=QUERY_SCOPE; default="collection"]
@@ -27,7 +29,7 @@ EXAMPLES
             --field-config=field-path=timestamp,order=descending
 
 REQUIRED FLAGS
-     --field-config=FIELD_CONFIG
+     --field-config=[array-config=ARRAY-CONFIG],[field-path=FIELD-PATH],[order=ORDER]
         Configuration for a field.
 
         This flag must be repeated to provide the ordered list of field
diff --git a/gcloud/firestore/indexes/fields/update b/gcloud/firestore/indexes/fields/update
index 1b13056eb..69d4feeb4 100644
--- a/gcloud/firestore/indexes/fields/update
+++ b/gcloud/firestore/indexes/fields/update
@@ -5,8 +5,8 @@ NAME
 SYNOPSIS
     gcloud firestore indexes fields update
         (FIELD : --collection-group=COLLECTION_GROUP --database=DATABASE)
-        (--clear-exemption | --disable-indexes | --index=KEY=VALUE) [--async]
-        [GCLOUD_WIDE_FLAG ...]
+        (--clear-exemption | --disable-indexes | --index=[KEY=VALUE,...])
+        [--async] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     Update the index configuration of the given field.
@@ -88,7 +88,7 @@ REQUIRED FLAGS
        --disable-indexes
           If provided, the field will no longer be indexed at all.
 
-       --index=KEY=VALUE
+       --index=[KEY=VALUE,...]
           An index for the field.
 
           This flag can be repeated to provide multiple indexes. Any existing
diff --git a/gcloud/healthcare/consent-stores/check-data-access b/gcloud/healthcare/consent-stores/check-data-access
index 008eb8e48..50ccbe3fe 100644
--- a/gcloud/healthcare/consent-stores/check-data-access
+++ b/gcloud/healthcare/consent-stores/check-data-access
@@ -5,7 +5,7 @@ NAME
 SYNOPSIS
     gcloud healthcare consent-stores check-data-access
         (CONSENT_STORE : --dataset=DATASET --location=LOCATION)
-        --data-id=DATA_ID [--request-attributes=[REQUEST_ATTRIBUTES,...]]
+        --data-id=DATA_ID [--request-attributes=[KEY=VALUE,...]]
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -68,7 +68,7 @@ REQUIRED FLAGS
         The unique identifier of the data to check access for.
 
 OPTIONAL FLAGS
-     --request-attributes=[REQUEST_ATTRIBUTES,...]
+     --request-attributes=[KEY=VALUE,...]
         Comma-separated list of request attributes associated with this access
         request. Each attribute has the form "KEY=VALUE".
 
diff --git a/gcloud/healthcare/consent-stores/evaluate-user-consents b/gcloud/healthcare/consent-stores/evaluate-user-consents
index f59d7945d..09ed1c011 100644
--- a/gcloud/healthcare/consent-stores/evaluate-user-consents
+++ b/gcloud/healthcare/consent-stores/evaluate-user-consents
@@ -7,9 +7,9 @@ SYNOPSIS
         (CONSENT_STORE : --dataset=DATASET --location=LOCATION)
         --user-id=USER_ID [--consent-list=[CONSENT_LIST,...]]
         [--page-size=PAGE_SIZE] [--page-token=PAGE_TOKEN]
-        [--request-attributes=[REQUEST_ATTRIBUTES,...]]
-        [--resource-attributes=[RESOURCE_ATTRIBUTES,...]]
-        [--response-view=RESPONSE_VIEW] [GCLOUD_WIDE_FLAG ...]
+        [--request-attributes=[KEY=VALUE,...]]
+        [--resource-attributes=[KEY=VALUE,...]] [--response-view=RESPONSE_VIEW]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     Check if each matching user data mapping in the given Cloud Healthcare API
@@ -84,11 +84,11 @@ OPTIONAL FLAGS
      --page-token=PAGE_TOKEN
         Token to retrieve the next page of results.
 
-     --request-attributes=[REQUEST_ATTRIBUTES,...]
+     --request-attributes=[KEY=VALUE,...]
         Comma-separated list of request attributes associated with this access
         request. Each attribute has the form "KEY=VALUE".
 
-     --resource-attributes=[RESOURCE_ATTRIBUTES,...]
+     --resource-attributes=[KEY=VALUE,...]
         Comma-separated list of resource attributes associated with this access
         request. Each attribute has the form "KEY=VALUE". If no values are
         specified, then all data types are queried.
diff --git a/gcloud/healthcare/consent-stores/query-accessible-data b/gcloud/healthcare/consent-stores/query-accessible-data
index 8ee0913d6..18ff510df 100644
--- a/gcloud/healthcare/consent-stores/query-accessible-data
+++ b/gcloud/healthcare/consent-stores/query-accessible-data
@@ -5,10 +5,8 @@ NAME
 SYNOPSIS
     gcloud healthcare consent-stores query-accessible-data
         (CONSENT_STORE : --dataset=DATASET --location=LOCATION)
-        --gcs-uri=GCS_URI [--async]
-        [--request-attributes=[REQUEST_ATTRIBUTES,...]]
-        [--resource-attributes=[RESOURCE_ATTRIBUTES,...]]
-        [GCLOUD_WIDE_FLAG ...]
+        --gcs-uri=GCS_URI [--async] [--request-attributes=[KEY=VALUE,...]]
+        [--resource-attributes=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     Queries all data IDs that are consented for a given use in the given Cloud
@@ -78,11 +76,11 @@ OPTIONAL FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
-     --request-attributes=[REQUEST_ATTRIBUTES,...]
+     --request-attributes=[KEY=VALUE,...]
         Comma-separated list of request attributes associated with this access
         request. Each attribute has the form "KEY=VALUE".
 
-     --resource-attributes=[RESOURCE_ATTRIBUTES,...]
+     --resource-attributes=[KEY=VALUE,...]
         Comma-separated list of resources attributes associated with the type
         of data being requested. Each attribute has the form "KEY=VALUE". If no
         values are specified, then all data types are included in the output.
diff --git a/gcloud/healthcare/hl7v2-stores/create b/gcloud/healthcare/hl7v2-stores/create
index 068d6b66e..b0feab65e 100644
--- a/gcloud/healthcare/hl7v2-stores/create
+++ b/gcloud/healthcare/hl7v2-stores/create
@@ -5,7 +5,8 @@ NAME
 SYNOPSIS
     gcloud healthcare hl7v2-stores create
         (HL7V2_STORE : --dataset=DATASET --location=LOCATION)
-        [--notification-config=NOTIFICATION_CONFIG] [GCLOUD_WIDE_FLAG ...]
+        [--notification-config=[filter=FILTER],[pubsub-topic=PUBSUB-TOPIC]]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     Create a Cloud Healthcare API HL7v2 store.
@@ -68,7 +69,7 @@ POSITIONAL ARGUMENTS
           ▸ set the property healthcare/location.
 
 FLAGS
-     --notification-config=NOTIFICATION_CONFIG
+     --notification-config=[filter=FILTER],[pubsub-topic=PUBSUB-TOPIC]
         A list of notification configs. Each configuration uses a filter to
         determine whether to publish a message (both Ingest & Create) on the
         corresponding notification destination. Only the message name is sent
diff --git a/gcloud/healthcare/hl7v2-stores/update b/gcloud/healthcare/hl7v2-stores/update
index d26adfbe1..08f6b96a8 100644
--- a/gcloud/healthcare/hl7v2-stores/update
+++ b/gcloud/healthcare/hl7v2-stores/update
@@ -5,7 +5,8 @@ NAME
 SYNOPSIS
     gcloud healthcare hl7v2-stores update
         (HL7V2_STORE : --dataset=DATASET --location=LOCATION)
-        [--notification-config=NOTIFICATION_CONFIG] [GCLOUD_WIDE_FLAG ...]
+        [--notification-config=[filter=FILTER],[pubsub-topic=PUBSUB-TOPIC]]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     Create a Cloud Healthcare API HL7v2 store.
@@ -61,7 +62,7 @@ POSITIONAL ARGUMENTS
           ▸ set the property healthcare/location.
 
 FLAGS
-     --notification-config=NOTIFICATION_CONFIG
+     --notification-config=[filter=FILTER],[pubsub-topic=PUBSUB-TOPIC]
         A list of notification configs. Each configuration uses a filter to
         determine whether to publish a message (both Ingest & Create) on the
         corresponding notification destination. Only the message name is sent
diff --git a/gcloud/iam/service-accounts/keys/create b/gcloud/iam/service-accounts/keys/create
index 1b8af4b9b..48cae73e7 100644
--- a/gcloud/iam/service-accounts/keys/create
+++ b/gcloud/iam/service-accounts/keys/create
@@ -1,6 +1,5 @@
 NAME
-    gcloud iam service-accounts keys create - create a private key for a
-        service account
+    gcloud iam service-accounts keys create - create a service account key
 
 SYNOPSIS
     gcloud iam service-accounts keys create OUTPUT-FILE
@@ -12,7 +11,7 @@ DESCRIPTION
     PERMISSION_DENIED error.
 
 EXAMPLES
-    To create a new private key for a service account, and save a copy of it
+    To create a new service account key and save the private portion of the key
     locally, run:
 
         $ gcloud iam service-accounts keys create key.json \
diff --git a/gcloud/iam/service-accounts/keys/delete b/gcloud/iam/service-accounts/keys/delete
index 740921ba5..d26a34c24 100644
--- a/gcloud/iam/service-accounts/keys/delete
+++ b/gcloud/iam/service-accounts/keys/delete
@@ -1,6 +1,5 @@
 NAME
-    gcloud iam service-accounts keys delete - delete a user-managed key from a
-        service account
+    gcloud iam service-accounts keys delete - delete a service account key
 
 SYNOPSIS
     gcloud iam service-accounts keys delete KEY-ID --iam-account=IAM_ACCOUNT
diff --git a/gcloud/iam/service-accounts/keys/disable b/gcloud/iam/service-accounts/keys/disable
index cdcc5872c..2b6db1e06 100644
--- a/gcloud/iam/service-accounts/keys/disable
+++ b/gcloud/iam/service-accounts/keys/disable
@@ -1,13 +1,12 @@
 NAME
-    gcloud iam service-accounts keys disable - disable a public key related to
-        an IAM service account
+    gcloud iam service-accounts keys disable - disable a service account key
 
 SYNOPSIS
     gcloud iam service-accounts keys disable
         (IAM_KEY : --iam-account=IAM_ACCOUNT) [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    Disable a public key related to an IAM service account.
+    Disable a service account key.
 
     If the service account does not exist, this command returns a
     PERMISSION_DENIED error.
diff --git a/gcloud/iam/service-accounts/keys/enable b/gcloud/iam/service-accounts/keys/enable
index ed6d7fc29..fc6a8955b 100644
--- a/gcloud/iam/service-accounts/keys/enable
+++ b/gcloud/iam/service-accounts/keys/enable
@@ -1,13 +1,12 @@
 NAME
-    gcloud iam service-accounts keys enable - enable a public key related to an
-        IAM service account
+    gcloud iam service-accounts keys enable - enable a service account key
 
 SYNOPSIS
     gcloud iam service-accounts keys enable
         (IAM_KEY : --iam-account=IAM_ACCOUNT) [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
-    Enable a public key related to an IAM service account.
+    Enable a service account key.
 
     If the service account does not exist, this command returns a
     PERMISSION_DENIED error.
diff --git a/gcloud/iam/service-accounts/keys/help b/gcloud/iam/service-accounts/keys/help
index 80c63c3f0..244d4683f 100644
--- a/gcloud/iam/service-accounts/keys/help
+++ b/gcloud/iam/service-accounts/keys/help
@@ -16,16 +16,16 @@ COMMANDS
     COMMAND is one of the following:
 
      create
-        Create a private key for a service account.
+        Create a service account key.
 
      delete
-        Delete a user-managed key from a service account.
+        Delete a service account key.
 
      disable
-        Disable a public key related to an IAM service account.
+        Disable a service account key.
 
      enable
-        Enable a public key related to an IAM service account.
+        Enable a service account key.
 
      list
         List the keys for a service account.
diff --git a/gcloud/iam/workforce-pools/providers/create-oidc b/gcloud/iam/workforce-pools/providers/create-oidc
index c8a360f53..133756ec7 100644
--- a/gcloud/iam/workforce-pools/providers/create-oidc
+++ b/gcloud/iam/workforce-pools/providers/create-oidc
@@ -5,7 +5,7 @@ NAME
 SYNOPSIS
     gcloud iam workforce-pools providers create-oidc
         (PROVIDER : --location=LOCATION --workforce-pool=WORKFORCE_POOL)
-        --attribute-mapping=[ATTRIBUTE_MAPPING,...] --client-id=CLIENT_ID
+        --attribute-mapping=[KEY=VALUE,...] --client-id=CLIENT_ID
         --issuer-uri=ISSUER_URI
         (--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR
           --web-sso-response-type=WEB_SSO_RESPONSE_TYPE
@@ -73,7 +73,7 @@ POSITIONAL ARGUMENTS
           ▸ provide the argument --workforce-pool on the command line.
 
 REQUIRED FLAGS
-     --attribute-mapping=[ATTRIBUTE_MAPPING,...]
+     --attribute-mapping=[KEY=VALUE,...]
         Maps claims from the authentication credentials issued by the Identity
         Provider into Google Cloud IAM attributes, e.g. subject, segment.
 
diff --git a/gcloud/iam/workforce-pools/providers/create-saml b/gcloud/iam/workforce-pools/providers/create-saml
index a9f4b1fe8..a62245a62 100644
--- a/gcloud/iam/workforce-pools/providers/create-saml
+++ b/gcloud/iam/workforce-pools/providers/create-saml
@@ -5,7 +5,7 @@ NAME
 SYNOPSIS
     gcloud iam workforce-pools providers create-saml
         (PROVIDER : --location=LOCATION --workforce-pool=WORKFORCE_POOL)
-        --attribute-mapping=[ATTRIBUTE_MAPPING,...]
+        --attribute-mapping=[KEY=VALUE,...]
         --idp-metadata-path=IDP_METADATA_PATH [--async]
         [--attribute-condition=ATTRIBUTE_CONDITION] [--description=DESCRIPTION]
         [--disabled] [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...]
@@ -65,7 +65,7 @@ POSITIONAL ARGUMENTS
           ▸ provide the argument --workforce-pool on the command line.
 
 REQUIRED FLAGS
-     --attribute-mapping=[ATTRIBUTE_MAPPING,...]
+     --attribute-mapping=[KEY=VALUE,...]
         Maps claims from the authentication credentials issued by the Identity
         Provider into Google Cloud IAM attributes, e.g. subject, segment.
 
diff --git a/gcloud/iam/workforce-pools/providers/update-oidc b/gcloud/iam/workforce-pools/providers/update-oidc
index f66e7b5e9..4927ef66d 100644
--- a/gcloud/iam/workforce-pools/providers/update-oidc
+++ b/gcloud/iam/workforce-pools/providers/update-oidc
@@ -6,7 +6,7 @@ SYNOPSIS
     gcloud iam workforce-pools providers update-oidc
         (PROVIDER : --location=LOCATION --workforce-pool=WORKFORCE_POOL)
         [--async] [--attribute-condition=ATTRIBUTE_CONDITION]
-        [--attribute-mapping=[ATTRIBUTE_MAPPING,...]] [--client-id=CLIENT_ID]
+        [--attribute-mapping=[KEY=VALUE,...]] [--client-id=CLIENT_ID]
         [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME]
         [--issuer-uri=ISSUER_URI]
         [--web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...]]
@@ -105,7 +105,7 @@ FLAGS
 
             "'admins' in google.groups"
 
-     --attribute-mapping=[ATTRIBUTE_MAPPING,...]
+     --attribute-mapping=[KEY=VALUE,...]
         Maps claims from the authentication credentials issued by the Identity
         Provider into Google Cloud IAM attributes, e.g. subject, segment.
 
diff --git a/gcloud/iam/workforce-pools/providers/update-saml b/gcloud/iam/workforce-pools/providers/update-saml
index 2d3f17458..309165276 100644
--- a/gcloud/iam/workforce-pools/providers/update-saml
+++ b/gcloud/iam/workforce-pools/providers/update-saml
@@ -6,8 +6,8 @@ SYNOPSIS
     gcloud iam workforce-pools providers update-saml
         (PROVIDER : --location=LOCATION --workforce-pool=WORKFORCE_POOL)
         [--async] [--attribute-condition=ATTRIBUTE_CONDITION]
-        [--attribute-mapping=[ATTRIBUTE_MAPPING,...]]
-        [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME]
+        [--attribute-mapping=[KEY=VALUE,...]] [--description=DESCRIPTION]
+        [--disabled] [--display-name=DISPLAY_NAME]
         [--idp-metadata-path=IDP_METADATA_PATH] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -96,7 +96,7 @@ FLAGS
 
             "'admins' in google.groups"
 
-     --attribute-mapping=[ATTRIBUTE_MAPPING,...]
+     --attribute-mapping=[KEY=VALUE,...]
         Maps claims from the authentication credentials issued by the Identity
         Provider into Google Cloud IAM attributes, e.g. subject, segment.
 
diff --git a/gcloud/iam/workload-identity-pools/providers/create-aws b/gcloud/iam/workload-identity-pools/providers/create-aws
index 47d8f7629..689637e4f 100644
--- a/gcloud/iam/workload-identity-pools/providers/create-aws
+++ b/gcloud/iam/workload-identity-pools/providers/create-aws
@@ -7,9 +7,8 @@ SYNOPSIS
         (PROVIDER : --location=LOCATION
           --workload-identity-pool=WORKLOAD_IDENTITY_POOL)
         --account-id=ACCOUNT_ID [--attribute-condition=ATTRIBUTE_CONDITION]
-        [--attribute-mapping=[ATTRIBUTE_MAPPING,...]]
-        [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME]
-        [GCLOUD_WIDE_FLAG ...]
+        [--attribute-mapping=[KEY=VALUE,...]] [--description=DESCRIPTION]
+        [--disabled] [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     Create a new AWS workload identity pool provider.
@@ -103,7 +102,7 @@ OPTIONAL FLAGS
 
             "'admins' in google.groups"
 
-     --attribute-mapping=[ATTRIBUTE_MAPPING,...]
+     --attribute-mapping=[KEY=VALUE,...]
         Maps attributes from authentication credentials issued by an external
         identity provider to Google Cloud attributes, such as subject and
         segment.
diff --git a/gcloud/iam/workload-identity-pools/providers/create-oidc b/gcloud/iam/workload-identity-pools/providers/create-oidc
index 50a5321f7..1ad918cb4 100644
--- a/gcloud/iam/workload-identity-pools/providers/create-oidc
+++ b/gcloud/iam/workload-identity-pools/providers/create-oidc
@@ -6,7 +6,7 @@ SYNOPSIS
     gcloud iam workload-identity-pools providers create-oidc
         (PROVIDER : --location=LOCATION
           --workload-identity-pool=WORKLOAD_IDENTITY_POOL)
-        --attribute-mapping=[ATTRIBUTE_MAPPING,...] --issuer-uri=ISSUER_URI
+        --attribute-mapping=[KEY=VALUE,...] --issuer-uri=ISSUER_URI
         [--allowed-audiences=[ALLOWED_AUDIENCES,...]]
         [--attribute-condition=ATTRIBUTE_CONDITION] [--description=DESCRIPTION]
         [--disabled] [--display-name=DISPLAY_NAME]
@@ -76,7 +76,7 @@ POSITIONAL ARGUMENTS
             line.
 
 REQUIRED FLAGS
-     --attribute-mapping=[ATTRIBUTE_MAPPING,...]
+     --attribute-mapping=[KEY=VALUE,...]
         Maps attributes from authentication credentials issued by an external
         identity provider to Google Cloud attributes, such as subject and
         segment.
diff --git a/gcloud/iam/workload-identity-pools/providers/create-saml b/gcloud/iam/workload-identity-pools/providers/create-saml
index c373f6d3d..4530a4560 100644
--- a/gcloud/iam/workload-identity-pools/providers/create-saml
+++ b/gcloud/iam/workload-identity-pools/providers/create-saml
@@ -6,7 +6,7 @@ SYNOPSIS
     gcloud iam workload-identity-pools providers create-saml
         (PROVIDER : --location=LOCATION
           --workload-identity-pool=WORKLOAD_IDENTITY_POOL)
-        --attribute-mapping=[ATTRIBUTE_MAPPING,...]
+        --attribute-mapping=[KEY=VALUE,...]
         --idp-metadata-path=IDP_METADATA_PATH
         [--attribute-condition=ATTRIBUTE_CONDITION] [--description=DESCRIPTION]
         [--disabled] [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...]
@@ -74,7 +74,7 @@ POSITIONAL ARGUMENTS
             line.
 
 REQUIRED FLAGS
-     --attribute-mapping=[ATTRIBUTE_MAPPING,...]
+     --attribute-mapping=[KEY=VALUE,...]
         Maps attributes from authentication credentials issued by an external
         identity provider to Google Cloud attributes, such as subject and
         segment.
diff --git a/gcloud/iam/workload-identity-pools/providers/update-aws b/gcloud/iam/workload-identity-pools/providers/update-aws
index 4b12af71a..9cb49ee90 100644
--- a/gcloud/iam/workload-identity-pools/providers/update-aws
+++ b/gcloud/iam/workload-identity-pools/providers/update-aws
@@ -7,9 +7,8 @@ SYNOPSIS
         (PROVIDER : --location=LOCATION
           --workload-identity-pool=WORKLOAD_IDENTITY_POOL)
         [--account-id=ACCOUNT_ID] [--attribute-condition=ATTRIBUTE_CONDITION]
-        [--attribute-mapping=[ATTRIBUTE_MAPPING,...]]
-        [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME]
-        [GCLOUD_WIDE_FLAG ...]
+        [--attribute-mapping=[KEY=VALUE,...]] [--description=DESCRIPTION]
+        [--disabled] [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     Update an AWS workload identity pool provider.
@@ -102,7 +101,7 @@ FLAGS
 
             "'admins' in google.groups"
 
-     --attribute-mapping=[ATTRIBUTE_MAPPING,...]
+     --attribute-mapping=[KEY=VALUE,...]
         Maps attributes from authentication credentials issued by an external
         identity provider to Google Cloud attributes, such as subject and
         segment.
diff --git a/gcloud/iam/workload-identity-pools/providers/update-oidc b/gcloud/iam/workload-identity-pools/providers/update-oidc
index ef703e1b3..c6d0113eb 100644
--- a/gcloud/iam/workload-identity-pools/providers/update-oidc
+++ b/gcloud/iam/workload-identity-pools/providers/update-oidc
@@ -8,10 +8,9 @@ SYNOPSIS
           --workload-identity-pool=WORKLOAD_IDENTITY_POOL)
         [--allowed-audiences=[ALLOWED_AUDIENCES,...]]
         [--attribute-condition=ATTRIBUTE_CONDITION]
-        [--attribute-mapping=[ATTRIBUTE_MAPPING,...]]
-        [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME]
-        [--issuer-uri=ISSUER_URI] [--jwk-json-path=JWK_JSON_PATH]
-        [GCLOUD_WIDE_FLAG ...]
+        [--attribute-mapping=[KEY=VALUE,...]] [--description=DESCRIPTION]
+        [--disabled] [--display-name=DISPLAY_NAME] [--issuer-uri=ISSUER_URI]
+        [--jwk-json-path=JWK_JSON_PATH] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     Update an OIDC workload identity pool provider.
@@ -117,7 +116,7 @@ FLAGS
 
             "'admins' in google.groups"
 
-     --attribute-mapping=[ATTRIBUTE_MAPPING,...]
+     --attribute-mapping=[KEY=VALUE,...]
         Maps attributes from authentication credentials issued by an external
         identity provider to Google Cloud attributes, such as subject and
         segment.
diff --git a/gcloud/iam/workload-identity-pools/providers/update-saml b/gcloud/iam/workload-identity-pools/providers/update-saml
index e560fe541..1b0e9cf39 100644
--- a/gcloud/iam/workload-identity-pools/providers/update-saml
+++ b/gcloud/iam/workload-identity-pools/providers/update-saml
@@ -7,8 +7,8 @@ SYNOPSIS
         (PROVIDER : --location=LOCATION
           --workload-identity-pool=WORKLOAD_IDENTITY_POOL)
         [--attribute-condition=ATTRIBUTE_CONDITION]
-        [--attribute-mapping=[ATTRIBUTE_MAPPING,...]]
-        [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME]
+        [--attribute-mapping=[KEY=VALUE,...]] [--description=DESCRIPTION]
+        [--disabled] [--display-name=DISPLAY_NAME]
         [--idp-metadata-path=IDP_METADATA_PATH] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -100,7 +100,7 @@ FLAGS
 
             "'admins' in google.groups"
 
-     --attribute-mapping=[ATTRIBUTE_MAPPING,...]
+     --attribute-mapping=[KEY=VALUE,...]
         Maps attributes from authentication credentials issued by an external
         identity provider to Google Cloud attributes, such as subject and
         segment.
diff --git a/gcloud/memcache/instances/create b/gcloud/memcache/instances/create
index c227cbe7e..50d0a3d52 100644
--- a/gcloud/memcache/instances/create
+++ b/gcloud/memcache/instances/create
@@ -5,7 +5,7 @@ SYNOPSIS
     gcloud memcache instances create (INSTANCE : --region=REGION)
         --node-count=NODE_COUNT --node-cpu=NODE_CPU --node-memory=NODE_MEMORY
         [--async] [--authorized-network=AUTHORIZED_NETWORK]
-        [--display-name=DISPLAY_NAME] [--labels=KEY=VALUE]
+        [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]]
         [--maintenance-window-day=MAINTENANCE_WINDOW_DAY]
         [--maintenance-window-duration=MAINTENANCE_WINDOW_DURATION]
         [--maintenance-window-start-time=MAINTENANCE_WINDOW_START_TIME]
@@ -89,7 +89,7 @@ OPTIONAL FLAGS
      --display-name=DISPLAY_NAME
         An arbitrary and optional user provided name for the instance.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
      --maintenance-window-day=MAINTENANCE_WINDOW_DAY
diff --git a/gcloud/memcache/instances/update b/gcloud/memcache/instances/update
index 75789f2eb..9a652f1d8 100644
--- a/gcloud/memcache/instances/update
+++ b/gcloud/memcache/instances/update
@@ -4,7 +4,8 @@ NAME
 SYNOPSIS
     gcloud memcache instances update (INSTANCE : --region=REGION)
         (--parameters=KEY=VALUE | --display-name=DISPLAY_NAME
-          --labels=KEY=VALUE --node-count=NODE_COUNT --maintenance-window-any
+          --labels=[KEY=VALUE,...]
+          --node-count=NODE_COUNT --maintenance-window-any
           | --maintenance-window-day=MAINTENANCE_WINDOW_DAY
           --maintenance-window-duration=MAINTENANCE_WINDOW_DURATION
           --maintenance-window-start-time=MAINTENANCE_WINDOW_START_TIME)
@@ -140,7 +141,7 @@ REQUIRED FLAGS
        --display-name=DISPLAY_NAME
           An arbitrary and optional user provided name for the instance.
 
-       --labels=KEY=VALUE
+       --labels=[KEY=VALUE,...]
           List of label KEY=VALUE pairs to add.
 
        --node-count=NODE_COUNT
diff --git a/gcloud/metastore/operations/cancel b/gcloud/metastore/operations/cancel
new file mode 100644
index 000000000..6ef8a293c
--- /dev/null
+++ b/gcloud/metastore/operations/cancel
@@ -0,0 +1,63 @@
+NAME
+    gcloud metastore operations cancel - cancel a Dataproc Metastore operation
+
+SYNOPSIS
+    gcloud metastore operations cancel (OPERATION : --location=LOCATION)
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Cancel a Dataproc Metastore operation.
+
+EXAMPLES
+    To cancel an active Dataproc Metastore operation with the name operation-1
+    in location us-central1, run:
+
+        $ gcloud metastore operations cancel operation-1 \
+            --location=us-central1
+
+POSITIONAL ARGUMENTS
+     Operation resource - The operation cancel. The arguments in this group can
+     be used to specify the attributes of this resource. (NOTE) Some attributes
+     are not given arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument operation on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       OPERATION
+          ID of the operation or fully qualified identifier for the operation.
+
+          To set the operation attribute:
+          ▸ provide the argument operation on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          Location to which the operation belongs.
+
+          To set the location attribute:
+          ▸ provide the argument operation on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property metastore/location.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha metastore operations cancel
+
+        $ gcloud beta metastore operations cancel
+
diff --git a/gcloud/metastore/operations/help b/gcloud/metastore/operations/help
index 0a15d2384..1db5a805b 100644
--- a/gcloud/metastore/operations/help
+++ b/gcloud/metastore/operations/help
@@ -15,6 +15,9 @@ GCLOUD WIDE FLAGS
 COMMANDS
     COMMAND is one of the following:
 
+     cancel
+        Cancel a Dataproc Metastore operation.
+
      delete
         Delete one or more completed Dataproc Metastore operations.
 
diff --git a/gcloud/metastore/services/alter-table-properties b/gcloud/metastore/services/alter-table-properties
index 18a921927..5c318d0fd 100644
--- a/gcloud/metastore/services/alter-table-properties
+++ b/gcloud/metastore/services/alter-table-properties
@@ -4,7 +4,7 @@ NAME
 
 SYNOPSIS
     gcloud metastore services alter-table-properties
-        (SERVICE : --location=LOCATION) --properties=PROPERTIES
+        (SERVICE : --location=LOCATION) --properties=[KEY=VALUE,...]
         --table-name=TABLE_NAME --update-mask=UPDATE_MASK [--async]
         [GCLOUD_WIDE_FLAG ...]
 
@@ -62,7 +62,7 @@ POSITIONAL ARGUMENTS
           ▸ set the property metastore/location.
 
 REQUIRED FLAGS
-     --properties=PROPERTIES
+     --properties=[KEY=VALUE,...]
         A string where field names are separated by a comma. Describes the
         desired values to mutate. If update-mask is empty, the properties will
         not update. Otherwise, the properties only alter the values whose
diff --git a/gcloud/metastore/services/create b/gcloud/metastore/services/create
index 8022949e6..5202b1ace 100644
--- a/gcloud/metastore/services/create
+++ b/gcloud/metastore/services/create
@@ -13,7 +13,7 @@ SYNOPSIS
           | --auxiliary-versions-from-file=AUXILIARY_VERSIONS_FROM_FILE]
         [--consumer-subnetworks=[CONSUMER_SUBNETWORKS,...] | --network=NETWORK
           | --network-config-from-file=NETWORK_CONFIG_FROM_FILE]
-        [--hive-metastore-configs=KEY=VALUE
+        [--hive-metastore-configs=[KEY=VALUE,...]
           | --hive-metastore-configs-from-file=HIVE_METASTORE_CONFIGS_FROM_FILE]
         [--instance-size=INSTANCE_SIZE | --scaling-factor=SCALING_FACTOR
           | --tier=TIER]
@@ -219,7 +219,7 @@ FLAGS
 
      At most one of these can be specified:
 
-       --hive-metastore-configs=KEY=VALUE
+       --hive-metastore-configs=[KEY=VALUE,...]
           A mapping of Hive metastore configuration key-value pairs to apply to
           the Hive metastore.
 
diff --git a/gcloud/metastore/services/update b/gcloud/metastore/services/update
index 9f2edf30c..41aa5d2e0 100644
--- a/gcloud/metastore/services/update
+++ b/gcloud/metastore/services/update
@@ -13,7 +13,7 @@ SYNOPSIS
           --maintenance-window-hour=MAINTENANCE_WINDOW_HOUR]
         [--update-auxiliary-versions-from-file=UPDATE_AUXILIARY_VERSIONS_FROM_FILE | --add-auxiliary-versions=[ADD_AUXILIARY_VERSIONS,
           ...] --clear-auxiliary-versions]
-        [--update-hive-metastore-configs-from-file=UPDATE_HIVE_METASTORE_CONFIGS_FROM_FILE | --update-hive-metastore-configs=[UPDATE_HIVE_METASTORE_CONFIGS,
+        [--update-hive-metastore-configs-from-file=UPDATE_HIVE_METASTORE_CONFIGS_FROM_FILE | --update-hive-metastore-configs=[KEY=VALUE,
           ...] --clear-hive-metastore-configs
           | --remove-hive-metastore-configs=[REMOVE_HIVE_METASTORE_CONFIGS,
           ...]] [GCLOUD_WIDE_FLAG ...]
@@ -249,7 +249,7 @@ FLAGS
        Modify the Hive metastore configuration properties by passing key-value
        pairs in through the flags.
 
-         --update-hive-metastore-configs=[UPDATE_HIVE_METASTORE_CONFIGS,...]
+         --update-hive-metastore-configs=[KEY=VALUE,...]
             Comma-separated list of Hive metastore configurations. Each
             configuration has the form "NAME=VALUE".
 
diff --git a/gcloud/netapp/active-directories/create b/gcloud/netapp/active-directories/create
new file mode 100644
index 000000000..2ed1a2cb7
--- /dev/null
+++ b/gcloud/netapp/active-directories/create
@@ -0,0 +1,151 @@
+NAME
+    gcloud netapp active-directories create - create a Cloud NetApp Active
+        Directory
+
+SYNOPSIS
+    gcloud netapp active-directories create
+        (ACTIVE_DIRECTORY : --location=LOCATION) --dns=DNS --domain=DOMAIN
+        --net-bios-prefix=NET_BIOS_PREFIX --password=PASSWORD
+        --username=USERNAME [--async]
+        [--backup-operators=[BACKUP_OPERATOR,...]] [--description=DESCRIPTION]
+        [--enable-aes=ENABLE_AES] [--enable-ldap-signing=ENABLE_LDAP_SIGNING]
+        [--encrypt-dc-connections=ENCRYPT_DC_CONNECTIONS]
+        [--kdc-hostname=KDC_HOSTNAME] [--kdc-ip=KDC_IP]
+        [--labels=[KEY=VALUE,...]] [--nfs-users-with-ldap=NFS_USERS_WITH_LDAP]
+        [--organizational-unit=ORGANIZATIONAL_UNIT]
+        [--security-operators=[SECURITY_OPERATOR,...]] [--site=SITE]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Creates an AD (Active Directory) config for Cloud NetApp Volumes.
+
+EXAMPLES
+    The following command creates an AD named AD_NAME with the required
+    arguments:
+
+        $ gcloud netapp active-directories create AD_NAME \
+          --location=us-central1 --domain=example-domain.com \
+          --dns=0.0.0.0 --net-bios-prefix=prefix-1 --enable-aes=true \
+          --username=user1 --password="secure1" \
+          --backup-operators=backup_op1,backup_op2 \
+          --security-operators=sec_op1,sec_op2 --enable-ldap-signing=false
+
+POSITIONAL ARGUMENTS
+     Active directory resource - The Active Directory to create. The arguments
+     in this group can be used to specify the attributes of this resource.
+     (NOTE) Some attributes are not given arguments in this group but can be
+     set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument active_directory on the command line with a
+        fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       ACTIVE_DIRECTORY
+          ID of the active_directory or fully qualified identifier for the
+          active_directory.
+
+          To set the active_directory attribute:
+          ▸ provide the argument active_directory on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the active_directory.
+
+          To set the location attribute:
+          ▸ provide the argument active_directory on the command line with a
+            fully specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+REQUIRED FLAGS
+     --dns=DNS
+        A comma separated list of DNS server IP addresses for the Active
+        Directory domain.
+
+     --domain=DOMAIN
+        The Active Directory domain.
+
+     --net-bios-prefix=NET_BIOS_PREFIX
+        NetBIOS prefix name of the server.
+
+     --password=PASSWORD
+        Password of the Active Directory domain administrator.
+
+     --username=USERNAME
+        Username of the Active Directory domain administrator.
+
+OPTIONAL FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --backup-operators=[BACKUP_OPERATOR,...]
+        Users to be added to the Built-in Backup Operator Active Directory
+        group.
+
+     --description=DESCRIPTION
+        A description of the Cloud NetApp Active Directory
+
+     --enable-aes=ENABLE_AES
+        The Boolean value indiciating whether AES encryption will be enabled
+        for SMB communication.
+
+     --enable-ldap-signing=ENABLE_LDAP_SIGNING
+        Boolean flag that specifies whether or not LDAP traffic needs to be
+        signed.
+
+     --encrypt-dc-connections=ENCRYPT_DC_CONNECTIONS
+        Boolean flag that specifies whether traffic between SMB server to
+        Domain Controller (DC) will be encrypted.
+
+     --kdc-hostname=KDC_HOSTNAME
+        Name of the Active Directory machine.
+
+     --kdc-ip=KDC_IP
+        KDC server IP address for the Active Directory machine.
+
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     --nfs-users-with-ldap=NFS_USERS_WITH_LDAP
+        Boolean flag that allows access to local users and LDAP users. If
+        access is needed only for LDAP users, it has to be disabled.
+
+     --organizational-unit=ORGANIZATIONAL_UNIT
+        The Organizational Unit (OU) within the Windows Active Directory the
+        user belongs to.
+
+     --security-operators=[SECURITY_OPERATOR,...]
+        Domain users to be given the Security privilege.
+
+     --site=SITE
+        The Active Directory site the service will limit Domain Controller
+        discovery to.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp active-directories create
+
+        $ gcloud beta netapp active-directories create
+
diff --git a/gcloud/netapp/active-directories/delete b/gcloud/netapp/active-directories/delete
new file mode 100644
index 000000000..c777713a1
--- /dev/null
+++ b/gcloud/netapp/active-directories/delete
@@ -0,0 +1,78 @@
+NAME
+    gcloud netapp active-directories delete - delete a Cloud NetApp Active
+        Directory
+
+SYNOPSIS
+    gcloud netapp active-directories delete
+        (ACTIVE_DIRECTORY : --location=LOCATION) [--async]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Deletes an AD (Active Directory) config for Cloud NetApp Volumes.
+
+EXAMPLES
+    The following command deletes an AD named AD_NAME with the required
+    arguments:
+
+        $ gcloud netapp active-directories delete AD_NAME \
+          --location=us-central1
+
+    To delete a AD Config asynchronously, run the following command:
+
+        $ gcloud netapp active-directories delete AD_NAME \
+          --location=us-central1 --async
+
+POSITIONAL ARGUMENTS
+     Active directory resource - The Active Directory to delete. The arguments
+     in this group can be used to specify the attributes of this resource.
+     (NOTE) Some attributes are not given arguments in this group but can be
+     set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument active_directory on the command line with a
+        fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       ACTIVE_DIRECTORY
+          ID of the active_directory or fully qualified identifier for the
+          active_directory.
+
+          To set the active_directory attribute:
+          ▸ provide the argument active_directory on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the active_directory.
+
+          To set the location attribute:
+          ▸ provide the argument active_directory on the command line with a
+            fully specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp active-directories delete
+
+        $ gcloud beta netapp active-directories delete
+
diff --git a/gcloud/netapp/active-directories/describe b/gcloud/netapp/active-directories/describe
new file mode 100644
index 000000000..24ad573e7
--- /dev/null
+++ b/gcloud/netapp/active-directories/describe
@@ -0,0 +1,67 @@
+NAME
+    gcloud netapp active-directories describe - show metadata for a Cloud
+        NetApp Active Directory
+
+SYNOPSIS
+    gcloud netapp active-directories describe
+        (ACTIVE_DIRECTORY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Describes an AD (Active Directory) config for Cloud NetApp Volumes.
+
+EXAMPLES
+    The following command describes an AD named AD_NAME with the required
+    arguments:
+
+        $ gcloud netapp active-directories describe AD_NAME \
+          --location=us-central1
+
+POSITIONAL ARGUMENTS
+     Active directory resource - The Active Directory to describe. The
+     arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument active_directory on the command line with a
+        fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       ACTIVE_DIRECTORY
+          ID of the active_directory or fully qualified identifier for the
+          active_directory.
+
+          To set the active_directory attribute:
+          ▸ provide the argument active_directory on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the active_directory.
+
+          To set the location attribute:
+          ▸ provide the argument active_directory on the command line with a
+            fully specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp active-directories describe
+
+        $ gcloud beta netapp active-directories describe
+
diff --git a/gcloud/netapp/active-directories/help b/gcloud/netapp/active-directories/help
new file mode 100644
index 000000000..89baadf11
--- /dev/null
+++ b/gcloud/netapp/active-directories/help
@@ -0,0 +1,40 @@
+NAME
+    gcloud netapp active-directories - create and manage Cloud NetApp Active
+        Directories
+
+SYNOPSIS
+    gcloud netapp active-directories COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Create and manage Cloud NetApp Active Directories.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        Create a Cloud NetApp Active Directory.
+
+     delete
+        Delete a Cloud NetApp Active Directory.
+
+     describe
+        Show metadata for a Cloud NetApp Active Directory.
+
+     list
+        List Cloud NetApp Active Directories.
+
+     update
+        Update a Cloud NetApp Active Directory.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp active-directories
+
+        $ gcloud beta netapp active-directories
+
diff --git a/gcloud/netapp/active-directories/list b/gcloud/netapp/active-directories/list
new file mode 100644
index 000000000..b270d4a4c
--- /dev/null
+++ b/gcloud/netapp/active-directories/list
@@ -0,0 +1,87 @@
+NAME
+    gcloud netapp active-directories list - list Cloud NetApp Active
+        Directories
+
+SYNOPSIS
+    gcloud netapp active-directories list [--location=LOCATION]
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Lists AD (Active Directory) configs for Cloud NetApp Volumes.
+
+EXAMPLES
+    The following command lists AD configs in the given project and location:
+
+        $ gcloud netapp active-directories list --location=us-central1
+
+FLAGS
+     Location resource - The location in which to list Active Directories. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --location on the command line with a fully
+        specified name;
+      ◆ uses all locations by default. with a fully specified name;
+      ◆ set the property netapp/location with a fully specified name;
+      ◆ set the property netapp/region with a fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+       --location=LOCATION
+          ID of the location or fully qualified identifier for the location.
+
+          To set the location attribute:
+          ▸ provide the argument --location on the command line;
+          ▸ uses all locations by default.;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp active-directories list
+
+        $ gcloud beta netapp active-directories list
+
diff --git a/gcloud/netapp/active-directories/update b/gcloud/netapp/active-directories/update
new file mode 100644
index 000000000..738d6c3f0
--- /dev/null
+++ b/gcloud/netapp/active-directories/update
@@ -0,0 +1,174 @@
+NAME
+    gcloud netapp active-directories update - update a Cloud NetApp Active
+        Directory
+
+SYNOPSIS
+    gcloud netapp active-directories update
+        (ACTIVE_DIRECTORY : --location=LOCATION) --dns=DNS --domain=DOMAIN
+        --net-bios-prefix=NET_BIOS_PREFIX --password=PASSWORD
+        --username=USERNAME [--async]
+        [--backup-operators=[BACKUP_OPERATOR,...]] [--description=DESCRIPTION]
+        [--enable-aes=ENABLE_AES] [--enable-ldap-signing=ENABLE_LDAP_SIGNING]
+        [--encrypt-dc-connections=ENCRYPT_DC_CONNECTIONS]
+        [--kdc-hostname=KDC_HOSTNAME] [--kdc-ip=KDC_IP]
+        [--nfs-users-with-ldap=NFS_USERS_WITH_LDAP]
+        [--organizational-unit=ORGANIZATIONAL_UNIT]
+        [--security-operators=[SECURITY_OPERATOR,...]] [--site=SITE]
+        [--update-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Updates AD (Active Directory) configs for Cloud NetApp Volumes.
+
+EXAMPLES
+    The following command updates an AD config in the given project and
+    location with specified arguments:
+
+        $ gcloud netapp active-directories update AD_NAME \
+          --location=us-central1 --domain=new-domain.com --dns=1.1.1.1 \
+          --site=new_site --net-bios-prefix=new_prefix \
+          --organizational-unit=ou2 --enable-aes=true --username=user2 \
+          --password="secure2" --backup-operators=backup_op3 \
+          --security-operators=secure_op3 --enable-ldap-signing=true \
+          --encrypt-dc-connections=yes --kdc-hostname=kdc-host1
+
+POSITIONAL ARGUMENTS
+     Active directory resource - The Active Directory to update. The arguments
+     in this group can be used to specify the attributes of this resource.
+     (NOTE) Some attributes are not given arguments in this group but can be
+     set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument active_directory on the command line with a
+        fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       ACTIVE_DIRECTORY
+          ID of the active_directory or fully qualified identifier for the
+          active_directory.
+
+          To set the active_directory attribute:
+          ▸ provide the argument active_directory on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the active_directory.
+
+          To set the location attribute:
+          ▸ provide the argument active_directory on the command line with a
+            fully specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+REQUIRED FLAGS
+     --dns=DNS
+        A comma separated list of DNS server IP addresses for the Active
+        Directory domain.
+
+     --domain=DOMAIN
+        The Active Directory domain.
+
+     --net-bios-prefix=NET_BIOS_PREFIX
+        NetBIOS prefix name of the server.
+
+     --password=PASSWORD
+        Password of the Active Directory domain administrator.
+
+     --username=USERNAME
+        Username of the Active Directory domain administrator.
+
+OPTIONAL FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --backup-operators=[BACKUP_OPERATOR,...]
+        Users to be added to the Built-in Backup Operator Active Directory
+        group.
+
+     --description=DESCRIPTION
+        A description of the Cloud NetApp Active Directory
+
+     --enable-aes=ENABLE_AES
+        The Boolean value indiciating whether AES encryption will be enabled
+        for SMB communication.
+
+     --enable-ldap-signing=ENABLE_LDAP_SIGNING
+        Boolean flag that specifies whether or not LDAP traffic needs to be
+        signed.
+
+     --encrypt-dc-connections=ENCRYPT_DC_CONNECTIONS
+        Boolean flag that specifies whether traffic between SMB server to
+        Domain Controller (DC) will be encrypted.
+
+     --kdc-hostname=KDC_HOSTNAME
+        Name of the Active Directory machine.
+
+     --kdc-ip=KDC_IP
+        KDC server IP address for the Active Directory machine.
+
+     --nfs-users-with-ldap=NFS_USERS_WITH_LDAP
+        Boolean flag that allows access to local users and LDAP users. If
+        access is needed only for LDAP users, it has to be disabled.
+
+     --organizational-unit=ORGANIZATIONAL_UNIT
+        The Organizational Unit (OU) within the Windows Active Directory the
+        user belongs to.
+
+     --security-operators=[SECURITY_OPERATOR,...]
+        Domain users to be given the Security privilege.
+
+     --site=SITE
+        The Active Directory site the service will limit Domain Controller
+        discovery to.
+
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud netapp active-directories update --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud netapp active-directories update --clear-labels \
+                --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp active-directories update
+
+        $ gcloud beta netapp active-directories update
+
diff --git a/gcloud/netapp/help b/gcloud/netapp/help
new file mode 100644
index 000000000..ce720762c
--- /dev/null
+++ b/gcloud/netapp/help
@@ -0,0 +1,52 @@
+NAME
+    gcloud netapp - create and manipulate Cloud NetApp Files resources
+
+SYNOPSIS
+    gcloud netapp GROUP [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    The gcloud netapp command group lets you create, configure and manipulate
+    Cloud NetApp Volumes resources such as Volumes, Storage Pools, Active
+    Directories, KMS Configs, Volume Snapshots, and Volume Replications etc.
+
+    With Cloud NetApp Volumes, you can take advantage of Google Cloud
+    Platform's scale, performance and value to manage and run on-prem NetApp
+    Files solutions on Google infrastructure, so you don't have to modernize
+    your file workloads, and allow for legacy feature support.
+
+    More information on Cloud NetApp Files can be found here:
+    https://cloud.google.com/netapp/docs/reference/rest
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+GROUPS
+    GROUP is one of the following:
+
+     active-directories
+        Create and manage Cloud NetApp Active Directories.
+
+     kms-configs
+        Create and manage Cloud NetApp Volumes KMS Configs.
+
+     locations
+        Get and list locations where Cloud NetApp Files is available.
+
+     operations
+        Read and manage Cloud NetApp Files Operations.
+
+     storage-pools
+        Create and manage Cloud NetApp Storage Pools.
+
+     volumes
+        Create and manage Cloud NetApp Volumes.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp
+
+        $ gcloud beta netapp
+
diff --git a/gcloud/netapp/kms-configs/create b/gcloud/netapp/kms-configs/create
new file mode 100644
index 000000000..72cfedff9
--- /dev/null
+++ b/gcloud/netapp/kms-configs/create
@@ -0,0 +1,130 @@
+NAME
+    gcloud netapp kms-configs create - create a Cloud NetApp Volumes KMS Config
+
+SYNOPSIS
+    gcloud netapp kms-configs create (KMS_CONFIG : --location=LOCATION)
+        (--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING
+          --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT) [--async]
+        [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Creates a KMS (Key Management System) Config to encrypt Cloud NetApp
+    Volumes, Storage Pools etc. using Customer Managed Encryption Keys (CMEK)
+
+EXAMPLES
+    The following command creates a KMS Config instance named KMS_CONFIG using
+    specified project, location, Key Ring and Crypto Key
+
+        $ gcloud netapp kms-configs create KMS_CONFIG \
+          --location=us-central1 --kms-location=northamerica-northeast1 \
+          --kms-project=kms-project1 --kms-keyring=kms-keyring21 \
+          --kms-key=crypto-key1
+
+POSITIONAL ARGUMENTS
+     Kms config resource - The KMS Config to create The arguments in this group
+     can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument kms_config on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       KMS_CONFIG
+          ID of the kms_config or fully qualified identifier for the
+          kms_config.
+
+          To set the kms_config attribute:
+          ▸ provide the argument kms_config on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the kms_config.
+
+          To set the location attribute:
+          ▸ provide the argument kms_config on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+REQUIRED FLAGS
+     Kms key resource - The Cloud KMS (Key Management Service) Crypto Key that
+     will be used The arguments in this group can be used to specify the
+     attributes of this resource.
+
+     This must be specified.
+
+       --kms-key=KMS_KEY
+          ID of the kms_key or fully qualified identifier for the kms_key.
+
+          To set the kms-key attribute:
+          ▸ provide the argument --kms-key on the command line.
+
+          This flag argument must be specified if any of the other arguments in
+          this group are specified.
+
+       --kms-keyring=KMS_KEYRING
+          The KMS keyring of the kms_key
+
+          To set the kms-keyring attribute:
+          ▸ provide the argument --kms-key on the command line with a fully
+            specified name;
+          ▸ provide the argument --kms-keyring on the command line.
+
+       --kms-location=KMS_LOCATION
+          The Cloud location for the kms_key.
+
+          To set the kms-location attribute:
+          ▸ provide the argument --kms-key on the command line with a fully
+            specified name;
+          ▸ provide the argument --kms-location on the command line;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+       --kms-project=KMS_PROJECT
+          The Cloud project for the kms_key.
+
+          To set the kms-project attribute:
+          ▸ provide the argument --kms-key on the command line with a fully
+            specified name;
+          ▸ provide the argument --kms-project on the command line;
+          ▸ set the property core/project.
+
+OPTIONAL FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --description=DESCRIPTION
+        A description of the Cloud NetApp KMS Config
+
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This variant is also available:
+
+        $ gcloud beta netapp kms-configs create
+
diff --git a/gcloud/netapp/kms-configs/delete b/gcloud/netapp/kms-configs/delete
new file mode 100644
index 000000000..ef701cb6b
--- /dev/null
+++ b/gcloud/netapp/kms-configs/delete
@@ -0,0 +1,73 @@
+NAME
+    gcloud netapp kms-configs delete - delete a Cloud NetApp Volumes KMS Config
+
+SYNOPSIS
+    gcloud netapp kms-configs delete (KMS_CONFIG : --location=LOCATION)
+        [--async] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Delete a KMS (Key Management System) Config
+
+EXAMPLES
+    The following command deletes a KMS Config instance named KMS_CONFIG in the
+    default netapp/location.
+
+        $ gcloud netapp kms-configs delete KMS_CONFIG
+
+    To delete a KMS Config named KMS_CONFIG asynchronously, run the following
+    command:
+
+        $ gcloud netapp kms-configs delete KMS_CONFIG --async
+
+POSITIONAL ARGUMENTS
+     Kms config resource - The KMS Config to delete The arguments in this group
+     can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument kms_config on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       KMS_CONFIG
+          ID of the kms_config or fully qualified identifier for the
+          kms_config.
+
+          To set the kms_config attribute:
+          ▸ provide the argument kms_config on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the kms_config.
+
+          To set the location attribute:
+          ▸ provide the argument kms_config on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This variant is also available:
+
+        $ gcloud beta netapp kms-configs delete
+
diff --git a/gcloud/netapp/kms-configs/describe b/gcloud/netapp/kms-configs/describe
new file mode 100644
index 000000000..d21ecbeff
--- /dev/null
+++ b/gcloud/netapp/kms-configs/describe
@@ -0,0 +1,70 @@
+NAME
+    gcloud netapp kms-configs describe - show metadata for a Cloud NetApp
+        Volumes KMS Config
+
+SYNOPSIS
+    gcloud netapp kms-configs describe (KMS_CONFIG : --location=LOCATION)
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Describe a KMS (Key Management System) Config.
+
+EXAMPLES
+    The following command gets metadata using describe for a KMS Config
+    instance named KMS_CONFIG in the default netapp/location.
+
+        $ gcloud netapp kms-configs describe KMS_CONFIG
+
+    To get metadata on a KMS Config named KMS_CONFIG in a specified location,
+    run:
+
+        $ gcloud netapp kms-configs describe KMS_CONFIG \
+          --location=us-central1s
+
+POSITIONAL ARGUMENTS
+     Kms config resource - The KMS Config to describe. The arguments in this
+     group can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument kms_config on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       KMS_CONFIG
+          ID of the kms_config or fully qualified identifier for the
+          kms_config.
+
+          To set the kms_config attribute:
+          ▸ provide the argument kms_config on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the kms_config.
+
+          To set the location attribute:
+          ▸ provide the argument kms_config on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This variant is also available:
+
+        $ gcloud beta netapp kms-configs describe
+
diff --git a/gcloud/netapp/kms-configs/encrypt b/gcloud/netapp/kms-configs/encrypt
new file mode 100644
index 000000000..3ffd446f8
--- /dev/null
+++ b/gcloud/netapp/kms-configs/encrypt
@@ -0,0 +1,71 @@
+NAME
+    gcloud netapp kms-configs encrypt - encrypt all existing volumes and
+        storage pools in the same region with the desired Cloud NetApp Volumes
+        KMS Config
+
+SYNOPSIS
+    gcloud netapp kms-configs encrypt (KMS_CONFIG : --location=LOCATION)
+        [--async] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Encrypt the existing volumes with the desired KMS (Key Management System)
+    Config using Customer Managed Encryption Keys (CMEK).
+
+EXAMPLES
+    The following command encrypts the existing volumes with the desired KMS
+    Config instance named KMS_CONFIG using specified project and location.
+
+        $ gcloud netapp kms-configs encrypt KMS_CONFIG --location=us-central1
+
+POSITIONAL ARGUMENTS
+     Kms config resource - The KMS Config used to encrypt The arguments in this
+     group can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument kms_config on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       KMS_CONFIG
+          ID of the kms_config or fully qualified identifier for the
+          kms_config.
+
+          To set the kms_config attribute:
+          ▸ provide the argument kms_config on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the kms_config.
+
+          To set the location attribute:
+          ▸ provide the argument kms_config on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This variant is also available:
+
+        $ gcloud beta netapp kms-configs encrypt
+
diff --git a/gcloud/netapp/kms-configs/help b/gcloud/netapp/kms-configs/help
new file mode 100644
index 000000000..e8ee726e6
--- /dev/null
+++ b/gcloud/netapp/kms-configs/help
@@ -0,0 +1,45 @@
+NAME
+    gcloud netapp kms-configs - create and manage Cloud NetApp Volumes KMS
+        Configs
+
+SYNOPSIS
+    gcloud netapp kms-configs COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Create and manage Cloud NetApp Volumes KMS Configs.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        Create a Cloud NetApp Volumes KMS Config.
+
+     delete
+        Delete a Cloud NetApp Volumes KMS Config.
+
+     describe
+        Show metadata for a Cloud NetApp Volumes KMS Config.
+
+     encrypt
+        Encrypt all existing volumes and storage pools in the same region with
+        the desired Cloud NetApp Volumes KMS Config.
+
+     list
+        List Cloud NetApp Volumes KMS Configs.
+
+     update
+        Update a Cloud NetApp Volumes KMS Config.
+
+     verify
+        Verify that the Cloud NetApp Volumes KMS Config is reachable.
+
+NOTES
+    This variant is also available:
+
+        $ gcloud beta netapp kms-configs
+
diff --git a/gcloud/netapp/kms-configs/list b/gcloud/netapp/kms-configs/list
new file mode 100644
index 000000000..ab00eee67
--- /dev/null
+++ b/gcloud/netapp/kms-configs/list
@@ -0,0 +1,90 @@
+NAME
+    gcloud netapp kms-configs list - list Cloud NetApp Volumes KMS Configs
+
+SYNOPSIS
+    gcloud netapp kms-configs list [--location=LOCATION] [--filter=EXPRESSION]
+        [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Lists KMS (Key Management System) Configs to encrypt Cloud NetApp Volumes,
+    Storage Pools etc. using Customer Managed Encryption Keys (CMEK).
+
+EXAMPLES
+    The following command lists all KMS Config instance in the default
+    netapp/location
+
+        $ gcloud netapp kms-configs list
+
+    To list all KMS Configs in a specified location, run:
+
+        $ gcloud netapp kms-configs list --location=us-central1
+
+FLAGS
+     Location resource - The location in which to list KMS Configs. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --location on the command line with a fully
+        specified name;
+      ◆ uses all locations by default. with a fully specified name;
+      ◆ set the property netapp/location with a fully specified name;
+      ◆ set the property netapp/region with a fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+       --location=LOCATION
+          ID of the location or fully qualified identifier for the location.
+
+          To set the location attribute:
+          ▸ provide the argument --location on the command line;
+          ▸ uses all locations by default.;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This variant is also available:
+
+        $ gcloud beta netapp kms-configs list
+
diff --git a/gcloud/netapp/kms-configs/update b/gcloud/netapp/kms-configs/update
new file mode 100644
index 000000000..5e850c046
--- /dev/null
+++ b/gcloud/netapp/kms-configs/update
@@ -0,0 +1,156 @@
+NAME
+    gcloud netapp kms-configs update - update a Cloud NetApp Volumes KMS Config
+
+SYNOPSIS
+    gcloud netapp kms-configs update (KMS_CONFIG : --location=LOCATION)
+        [--async] [--description=DESCRIPTION] [--update-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]]
+        [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING
+          --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Updates a KMS (Key Management System) Config.
+
+EXAMPLES
+    The following command updates a KMS Config instance named KMS_CONFIG with
+    all possible arguments:
+
+        $ gcloud netapp kms-configs update KMS_CONFIG \
+          --location=us-central1 --kms-location=europe-southwest1 \
+          --kms-project=new-kms-project --kms-keyring=kms-keyring2 \
+          --kms-key=crypto-key2
+
+    To update a KMS Config named KMS_CONFIG asynchronously, run the following
+    command:
+
+        $ gcloud netapp kms-configs update KMS_CONFIG --async \
+          --location=us-central1 --kms-location=europe-southwest1 \
+          --kms-project=new-kms-project --kms-keyring=kms-keyring2 \
+          --kms-key=crypto-key2
+
+POSITIONAL ARGUMENTS
+     Kms config resource - The KMS Config to update The arguments in this group
+     can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument kms_config on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       KMS_CONFIG
+          ID of the kms_config or fully qualified identifier for the
+          kms_config.
+
+          To set the kms_config attribute:
+          ▸ provide the argument kms_config on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the kms_config.
+
+          To set the location attribute:
+          ▸ provide the argument kms_config on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --description=DESCRIPTION
+        A description of the Cloud NetApp KMS Config
+
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud netapp kms-configs update --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud netapp kms-configs update --clear-labels \
+                --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+     Kms key resource - The Cloud KMS (Key Management Service) Crypto Key that
+     will be used The arguments in this group can be used to specify the
+     attributes of this resource.
+
+       --kms-key=KMS_KEY
+          ID of the kms_key or fully qualified identifier for the kms_key.
+
+          To set the kms-key attribute:
+          ▸ provide the argument --kms-key on the command line.
+
+          This flag argument must be specified if any of the other arguments in
+          this group are specified.
+
+       --kms-keyring=KMS_KEYRING
+          The KMS keyring of the kms_key
+
+          To set the kms-keyring attribute:
+          ▸ provide the argument --kms-key on the command line with a fully
+            specified name;
+          ▸ provide the argument --kms-keyring on the command line.
+
+       --kms-location=KMS_LOCATION
+          The Cloud location for the kms_key.
+
+          To set the kms-location attribute:
+          ▸ provide the argument --kms-key on the command line with a fully
+            specified name;
+          ▸ provide the argument --kms-location on the command line;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+       --kms-project=KMS_PROJECT
+          The Cloud project for the kms_key.
+
+          To set the kms-project attribute:
+          ▸ provide the argument --kms-key on the command line with a fully
+            specified name;
+          ▸ provide the argument --kms-project on the command line;
+          ▸ set the property core/project.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This variant is also available:
+
+        $ gcloud beta netapp kms-configs update
+
diff --git a/gcloud/netapp/kms-configs/verify b/gcloud/netapp/kms-configs/verify
new file mode 100644
index 000000000..274f63291
--- /dev/null
+++ b/gcloud/netapp/kms-configs/verify
@@ -0,0 +1,65 @@
+NAME
+    gcloud netapp kms-configs verify - verify that the Cloud NetApp Volumes KMS
+        Config is reachable
+
+SYNOPSIS
+    gcloud netapp kms-configs verify (KMS_CONFIG : --location=LOCATION)
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Verifies that the Cloud NetApp Volumes KMS (Key Management System) Config
+    is reachable.
+
+EXAMPLES
+    The following command verifies that the KMS Config instance named
+    KMS_CONFIG is reachable using specified location.
+
+        $ gcloud netapp kms-configs verify KMS_CONFIG --location=us-central1
+
+POSITIONAL ARGUMENTS
+     Kms config resource - The KMS Config used to verify The arguments in this
+     group can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument kms_config on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       KMS_CONFIG
+          ID of the kms_config or fully qualified identifier for the
+          kms_config.
+
+          To set the kms_config attribute:
+          ▸ provide the argument kms_config on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the kms_config.
+
+          To set the location attribute:
+          ▸ provide the argument kms_config on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This variant is also available:
+
+        $ gcloud beta netapp kms-configs verify
+
diff --git a/gcloud/netapp/locations/describe b/gcloud/netapp/locations/describe
new file mode 100644
index 000000000..a6dc6e505
--- /dev/null
+++ b/gcloud/netapp/locations/describe
@@ -0,0 +1,49 @@
+NAME
+    gcloud netapp locations describe - describe a Cloud NetApp Files location
+
+SYNOPSIS
+    gcloud netapp locations describe LOCATION [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Describe a Cloud NetApp Files location.
+
+EXAMPLES
+    The following command shows the details for the NetApp Files location named
+    NAME.
+
+        $ gcloud netapp locations describe NAME
+
+POSITIONAL ARGUMENTS
+     Location resource - The location to describe. This represents a Cloud
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument location on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       LOCATION
+          ID of the location or fully qualified identifier for the location.
+
+          To set the location attribute:
+          ▸ provide the argument location on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp locations describe
+
+        $ gcloud beta netapp locations describe
+
diff --git a/gcloud/netapp/locations/help b/gcloud/netapp/locations/help
new file mode 100644
index 000000000..625e8c834
--- /dev/null
+++ b/gcloud/netapp/locations/help
@@ -0,0 +1,31 @@
+NAME
+    gcloud netapp locations - get and list locations where Cloud NetApp Files
+        is available
+
+SYNOPSIS
+    gcloud netapp locations COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Get and list locations where Cloud NetApp Files is available.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     describe
+        Describe a Cloud NetApp Files location.
+
+     list
+        List all Cloud NetApp Files locations.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp locations
+
+        $ gcloud beta netapp locations
+
diff --git a/gcloud/netapp/locations/list b/gcloud/netapp/locations/list
new file mode 100644
index 000000000..673e7e9cc
--- /dev/null
+++ b/gcloud/netapp/locations/list
@@ -0,0 +1,63 @@
+NAME
+    gcloud netapp locations list - list all Cloud NetApp Files locations
+
+SYNOPSIS
+    gcloud netapp locations list [--filter=EXPRESSION] [--limit=LIMIT]
+        [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Lists all Cloud NetApp Files locations.
+
+EXAMPLES
+    The following command lists NetApp Files locations.
+
+        $ gcloud netapp locations list
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp locations list
+
+        $ gcloud beta netapp locations list
+
diff --git a/gcloud/netapp/operations/describe b/gcloud/netapp/operations/describe
new file mode 100644
index 000000000..5a084f78e
--- /dev/null
+++ b/gcloud/netapp/operations/describe
@@ -0,0 +1,64 @@
+NAME
+    gcloud netapp operations describe - describe a Cloud NetApp Files operation
+
+SYNOPSIS
+    gcloud netapp operations describe (OPERATION : --location=LOCATION)
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Describe a Cloud NetApp Files operation.
+
+EXAMPLES
+    The following command shows the details for the NetApp Files operation
+    named NAME.
+
+        $ gcloud netapp operations describe NAME
+
+POSITIONAL ARGUMENTS
+     Operation resource - The operation to describe. The arguments in this
+     group can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument operation on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       OPERATION
+          ID of the operation or fully qualified identifier for the operation.
+
+          To set the operation attribute:
+          ▸ provide the argument operation on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the operation.
+
+          To set the location attribute:
+          ▸ provide the argument operation on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp operations describe
+
+        $ gcloud beta netapp operations describe
+
diff --git a/gcloud/netapp/operations/help b/gcloud/netapp/operations/help
new file mode 100644
index 000000000..96eb95d76
--- /dev/null
+++ b/gcloud/netapp/operations/help
@@ -0,0 +1,30 @@
+NAME
+    gcloud netapp operations - read and manage Cloud NetApp Files Operations
+
+SYNOPSIS
+    gcloud netapp operations COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Read and manage Cloud NetApp Files Operations.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     describe
+        Describe a Cloud NetApp Files operation.
+
+     list
+        List Cloud NetApp Files operations.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp operations
+
+        $ gcloud beta netapp operations
+
diff --git a/gcloud/netapp/operations/list b/gcloud/netapp/operations/list
new file mode 100644
index 000000000..303b6220a
--- /dev/null
+++ b/gcloud/netapp/operations/list
@@ -0,0 +1,86 @@
+NAME
+    gcloud netapp operations list - list Cloud NetApp Files operations
+
+SYNOPSIS
+    gcloud netapp operations list [--location=LOCATION] [--filter=EXPRESSION]
+        [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Lists all Cloud NetApp Files operations.
+
+EXAMPLES
+    The following command lists NetApp Files operations under a given location
+
+        $ gcloud netapp operations list --location=us-central1
+
+FLAGS
+     Location resource - The location in which to list operations. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --location on the command line with a fully
+        specified name;
+      ◆ uses all locations by default. with a fully specified name;
+      ◆ set the property netapp/location with a fully specified name;
+      ◆ set the property netapp/region with a fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+       --location=LOCATION
+          ID of the location or fully qualified identifier for the location.
+
+          To set the location attribute:
+          ▸ provide the argument --location on the command line;
+          ▸ uses all locations by default.;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp operations list
+
+        $ gcloud beta netapp operations list
+
diff --git a/gcloud/netapp/storage-pools/create b/gcloud/netapp/storage-pools/create
new file mode 100644
index 000000000..486277932
--- /dev/null
+++ b/gcloud/netapp/storage-pools/create
@@ -0,0 +1,175 @@
+NAME
+    gcloud netapp storage-pools create - create a Cloud NetApp Storage Pool
+
+SYNOPSIS
+    gcloud netapp storage-pools create (STORAGE_POOL : --location=LOCATION)
+        --capacity=CAPACITY --network=[name=NAME],[psa-range=PSA-RANGE]
+        --service-level=SERVICE_LEVEL [--active-directory=ACTIVE_DIRECTORY]
+        [--async] [--description=DESCRIPTION] [--enable-ldap=ENABLE_LDAP]
+        [--kms-config=KMS_CONFIG] [--labels=[KEY=VALUE,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Creates a Storage Pool to contain Volumes with a specified Service Level
+    and capacity.
+
+EXAMPLES
+    The following command creates a Storage Pool named NAME using all possible
+    arguments
+
+        $ gcloud netapp storage-pools create NAME --location=us-central1 \
+          --service-level=standard --capacity=2048 \
+          --network=name=default --active-directory=ad1 \
+          --kms-config=kms-config1 --enable-ldap=true \
+          --description="example description"
+
+POSITIONAL ARGUMENTS
+     Storage pool resource - The Storage Pool to create. The arguments in this
+     group can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument storage_pool on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       STORAGE_POOL
+          ID of the storage_pool or fully qualified identifier for the
+          storage_pool.
+
+          To set the storage_pool attribute:
+          ▸ provide the argument storage_pool on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the storage_pool.
+
+          To set the location attribute:
+          ▸ provide the argument storage_pool on the command line with a
+            fully specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+REQUIRED FLAGS
+     --capacity=CAPACITY
+        The desired capacity of the Storage Pool in GiB or TiB units.If no
+        capacity unit is specified, GiB is assumed.
+
+     --network=[name=NAME],[psa-range=PSA-RANGE]
+        Network configuration for a Cloud NetApp Files Storage Pool. Specifying
+        psa-range is optional.
+         name
+            The name of the Google Compute Engine VPC network to which the
+            volume is connected.
+         psa-range
+            The psa-range is the name of the allocated range of the Private
+            Service Access connection. The range you specify can't overlap with
+            either existing subnets or assigned IP address ranges for other
+            Cloud NetApp Files Storage Pools in the selected VPC network.
+
+     --service-level=SERVICE_LEVEL
+        The service level for the Cloud NetApp Storage Pool. For more details,
+        see:
+        https://cloud.google.com/architecture/partners/netapp-cloud-volumes/service-levels
+
+        SERVICE_LEVEL must be one of:
+
+         extreme
+            Extreme Service Level for Cloud NetApp Storage Pool. The Extreme
+            Service Level has a throughput per TiB of allocated volume size of
+            128 MiB/s.
+         premium
+            Premium Service Level for Cloud NetApp Storage Pool. The Premium
+            Service Level has a throughput per TiB of allocated volume size of
+            64 MiB/s.
+
+OPTIONAL FLAGS
+     Active directory resource - The Active Directory to attach to the Storage
+     Pool. This represents a Cloud resource. (NOTE) Some attributes are not
+     given arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --active-directory on the command line with a
+        fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --active-directory on the command line with a
+        fully specified name;
+      ◆ provide the argument --location on the command line;
+      ◆ set the property netapp/location;
+      ◆ set the property netapp/region.
+
+       --active-directory=ACTIVE_DIRECTORY
+          ID of the active_directory or fully qualified identifier for the
+          active_directory.
+
+          To set the active_directory attribute:
+          ▸ provide the argument --active-directory on the command line.
+
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --description=DESCRIPTION
+        A description of the Cloud NetApp Storage Pool
+
+     --enable-ldap=ENABLE_LDAP
+        Boolean flag indicating whether Storage Pool is a NFS LDAP Storage Pool
+        or not
+
+     Kms config resource - The KMS config to attach to the Storage Pool. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --kms-config on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --kms-config on the command line with a fully
+        specified name;
+      ◆ provide the argument --location on the command line;
+      ◆ set the property netapp/location;
+      ◆ set the property netapp/region.
+
+       --kms-config=KMS_CONFIG
+          ID of the kms_config or fully qualified identifier for the
+          kms_config.
+
+          To set the kms_config attribute:
+          ▸ provide the argument --kms-config on the command line.
+
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp storage-pools create
+
+        $ gcloud beta netapp storage-pools create
+
diff --git a/gcloud/netapp/storage-pools/delete b/gcloud/netapp/storage-pools/delete
new file mode 100644
index 000000000..8c8534faa
--- /dev/null
+++ b/gcloud/netapp/storage-pools/delete
@@ -0,0 +1,75 @@
+NAME
+    gcloud netapp storage-pools delete - delete a Cloud NetApp Storage Pool
+
+SYNOPSIS
+    gcloud netapp storage-pools delete (STORAGE_POOL : --location=LOCATION)
+        [--async] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Delete a Storage Pool
+
+EXAMPLES
+    The following command deletes a Storage Pool named NAME in the given
+    location
+
+        $ gcloud netapp storage-pools delete NAME --location=us-central1
+
+    To delete a Storage Pool asynchronously, run the following command:
+
+        $ gcloud netapp storage-pools delete NAME --location=us-central1 \
+          --async
+
+POSITIONAL ARGUMENTS
+     Storage pool resource - The Storage Pool to delete. The arguments in this
+     group can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument storage_pool on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       STORAGE_POOL
+          ID of the storage_pool or fully qualified identifier for the
+          storage_pool.
+
+          To set the storage_pool attribute:
+          ▸ provide the argument storage_pool on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the storage_pool.
+
+          To set the location attribute:
+          ▸ provide the argument storage_pool on the command line with a
+            fully specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp storage-pools delete
+
+        $ gcloud beta netapp storage-pools delete
+
diff --git a/gcloud/netapp/storage-pools/describe b/gcloud/netapp/storage-pools/describe
new file mode 100644
index 000000000..90074377a
--- /dev/null
+++ b/gcloud/netapp/storage-pools/describe
@@ -0,0 +1,66 @@
+NAME
+    gcloud netapp storage-pools describe - show metadata for a Cloud NetApp
+        Storage Pool
+
+SYNOPSIS
+    gcloud netapp storage-pools describe (STORAGE_POOL : --location=LOCATION)
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Describe a Storage Pool
+
+EXAMPLES
+    The following command describes a Storage Pool named NAME in the given
+    location
+
+        $ gcloud netapp storage-pools describe NAME --location=us-central1
+
+POSITIONAL ARGUMENTS
+     Storage pool resource - The Storage Pool to describe. The arguments in
+     this group can be used to specify the attributes of this resource. (NOTE)
+     Some attributes are not given arguments in this group but can be set in
+     other ways.
+
+     To set the project attribute:
+      ◆ provide the argument storage_pool on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       STORAGE_POOL
+          ID of the storage_pool or fully qualified identifier for the
+          storage_pool.
+
+          To set the storage_pool attribute:
+          ▸ provide the argument storage_pool on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the storage_pool.
+
+          To set the location attribute:
+          ▸ provide the argument storage_pool on the command line with a
+            fully specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp storage-pools describe
+
+        $ gcloud beta netapp storage-pools describe
+
diff --git a/gcloud/netapp/storage-pools/help b/gcloud/netapp/storage-pools/help
new file mode 100644
index 000000000..9dc762a1c
--- /dev/null
+++ b/gcloud/netapp/storage-pools/help
@@ -0,0 +1,39 @@
+NAME
+    gcloud netapp storage-pools - create and manage Cloud NetApp Storage Pools
+
+SYNOPSIS
+    gcloud netapp storage-pools COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Create and manage Cloud NetApp Storage Pools.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        Create a Cloud NetApp Storage Pool.
+
+     delete
+        Delete a Cloud NetApp Storage Pool.
+
+     describe
+        Show metadata for a Cloud NetApp Storage Pool.
+
+     list
+        List Cloud NetApp Storage Pools.
+
+     update
+        Update a Cloud NetApp Storage Pool.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp storage-pools
+
+        $ gcloud beta netapp storage-pools
+
diff --git a/gcloud/netapp/storage-pools/list b/gcloud/netapp/storage-pools/list
new file mode 100644
index 000000000..494ff1bfb
--- /dev/null
+++ b/gcloud/netapp/storage-pools/list
@@ -0,0 +1,86 @@
+NAME
+    gcloud netapp storage-pools list - list Cloud NetApp Storage Pools
+
+SYNOPSIS
+    gcloud netapp storage-pools list [--location=LOCATION]
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Lists Storage Pools
+
+EXAMPLES
+    The following command lists Storage Pools in the given location
+
+        $ gcloud netapp storage-pools list --location=us-central1
+
+FLAGS
+     Location resource - The location in which to list Storage Pools. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --location on the command line with a fully
+        specified name;
+      ◆ uses all locations by default. with a fully specified name;
+      ◆ set the property netapp/location with a fully specified name;
+      ◆ set the property netapp/region with a fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+       --location=LOCATION
+          ID of the location or fully qualified identifier for the location.
+
+          To set the location attribute:
+          ▸ provide the argument --location on the command line;
+          ▸ uses all locations by default.;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp storage-pools list
+
+        $ gcloud beta netapp storage-pools list
+
diff --git a/gcloud/netapp/storage-pools/update b/gcloud/netapp/storage-pools/update
new file mode 100644
index 000000000..dfefc55a1
--- /dev/null
+++ b/gcloud/netapp/storage-pools/update
@@ -0,0 +1,134 @@
+NAME
+    gcloud netapp storage-pools update - update a Cloud NetApp Storage Pool
+
+SYNOPSIS
+    gcloud netapp storage-pools update (STORAGE_POOL : --location=LOCATION)
+        [--active-directory=ACTIVE_DIRECTORY] [--async] [--capacity=CAPACITY]
+        [--description=DESCRIPTION] [--update-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Updates a Storage Pool with given arguments
+
+EXAMPLES
+    The following command updates a Storage Pool named NAME in the given
+    location
+
+        $ gcloud netapp storage-pools update NAME --location=us-central1 \
+          --capacity=4096 --active-directory=ad-2 \
+          --description="new description" --update-labels=key1=val1
+
+POSITIONAL ARGUMENTS
+     Storage pool resource - The Storage Pool to update. The arguments in this
+     group can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument storage_pool on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       STORAGE_POOL
+          ID of the storage_pool or fully qualified identifier for the
+          storage_pool.
+
+          To set the storage_pool attribute:
+          ▸ provide the argument storage_pool on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the storage_pool.
+
+          To set the location attribute:
+          ▸ provide the argument storage_pool on the command line with a
+            fully specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+FLAGS
+     Active directory resource - The Active Directory to attach to the Storage
+     Pool. This represents a Cloud resource. (NOTE) Some attributes are not
+     given arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --active-directory on the command line with a
+        fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --active-directory on the command line with a
+        fully specified name;
+      ◆ provide the argument --location on the command line;
+      ◆ set the property netapp/location;
+      ◆ set the property netapp/region.
+
+       --active-directory=ACTIVE_DIRECTORY
+          ID of the active_directory or fully qualified identifier for the
+          active_directory.
+
+          To set the active_directory attribute:
+          ▸ provide the argument --active-directory on the command line.
+
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --capacity=CAPACITY
+        The desired capacity of the Storage Pool in GiB or TiB units.If no
+        capacity unit is specified, GiB is assumed.
+
+     --description=DESCRIPTION
+        A description of the Cloud NetApp Storage Pool
+
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud netapp storage-pools update --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud netapp storage-pools update --clear-labels \
+                --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp storage-pools update
+
+        $ gcloud beta netapp storage-pools update
+
diff --git a/gcloud/netapp/volumes/create b/gcloud/netapp/volumes/create
new file mode 100644
index 000000000..1ca2b73b5
--- /dev/null
+++ b/gcloud/netapp/volumes/create
@@ -0,0 +1,242 @@
+NAME
+    gcloud netapp volumes create - create a Cloud NetApp Volume
+
+SYNOPSIS
+    gcloud netapp volumes create (VOLUME : --location=LOCATION)
+        --capacity=CAPACITY --protocols=PROTOCOL,[PROTOCOL,...]
+        --share-name=SHARE_NAME --storage-pool=STORAGE_POOL [--async]
+        [--description=DESCRIPTION] [--enable-kerberos=ENABLE_KERBEROS]
+        [--export-policy=[access-type=ACCESS-TYPE],
+          [allowed-clients=ALLOWED-CLIENTS],[has-root-access=HAS-ROOT-ACCESS],
+          [kerberos-5-read-only=KERBEROS-5-READ-ONLY],
+          [kerberos-5-read-write=KERBEROS-5-READ-WRITE],
+          [kerberos-5i-read-only=KERBEROS-5I-READ-ONLY],
+          [kerberos-5i-read-write=KERBEROS-5I-READ-WRITE],
+          [kerberos-5p-read-only=KERBEROS-5P-READ-ONLY],
+          [kerberos-5p-read-write=KERBEROS-5P-READ-WRITE],
+          [nfsv3=NFSV3],[nfsv4=NFSV4]] [--labels=[KEY=VALUE,...]]
+        [--security-style=SECURITY_STYLE; default="SECURITY_STYLE_UNSPECIFIED"]
+        [--smb-settings=SMB_SETTING,[SMB_SETTING,...]]
+        [--snap-reserve=SNAP_RESERVE]
+        [--snapshot-daily=[hour=HOUR],
+          [minute=MINUTE],[snapshots-to-keep=SNAPSHOTS-TO-KEEP]]
+        [--snapshot-directory=SNAPSHOT_DIRECTORY; default="true"]
+        [--snapshot-hourly=[minute=MINUTE],
+          [snapshots-to-keep=SNAPSHOTS-TO-KEEP]]
+        [--snapshot-monthly=[day=DAY],
+          [hour=HOUR],[minute=MINUTE],[snapshots-to-keep=SNAPSHOTS-TO-KEEP]]
+        [--snapshot-weekly=[day=DAY],
+          [hour=HOUR],[minute=MINUTE],[snapshots-to-keep=SNAPSHOTS-TO-KEEP]]
+        [--source-snapshot=SOURCE_SNAPSHOT]
+        [--unix-permissions=UNIX_PERMISSIONS] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Create a Cloud NetApp Volume
+
+EXAMPLES
+    The following command creates a NFS Volume named NAME asynchronously using
+    the specified arguments
+
+        $ gcloud netapp volumes create NAME --capacity=1024 \
+          --protocols=nfsv3,nfsv4 --share-name=share1 --storage-pool=sp1 \
+          --description="test description" --enable-kerberos=true \
+          --unix-permissions=0755 --async
+
+    The following command creates a SMB Volume named NAME asynchronously using
+    the specified arguments
+
+        $ gcloud netapp volumes create NAME --capacity=1024 \
+          --protocols=smb --share-name=share2 --storage-pool=sp2 \
+          --description="test smb" --security-style=ntfs \
+          --smb-settings=SHOW_SNAPSHOT,SHOW_PREVIOUS_VERSIONS,\
+        ACCESS_BASED_ENUMERATION --snap-reserve=0.1 --async
+
+POSITIONAL ARGUMENTS
+     Volume resource - The Volume to create. The arguments in this group can be
+     used to specify the attributes of this resource. (NOTE) Some attributes
+     are not given arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       VOLUME
+          ID of the volume or fully qualified identifier for the volume.
+
+          To set the volume attribute:
+          ▸ provide the argument volume on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the volume.
+
+          To set the location attribute:
+          ▸ provide the argument volume on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+REQUIRED FLAGS
+     --capacity=CAPACITY
+        The desired capacity of the Volume in GiB or TiB units.If no capacity
+        unit is specified, GiB is assumed.
+
+     --protocols=PROTOCOL,[PROTOCOL,...]
+        Type of File System protocols for the Cloud NetApp Files VolumeValid
+        component values are: NFSV3, NFSV4, SMB
+
+            For more information, look athttps://cloud.google.com/netapp/docs/reference/rest/v1alpha1/projects.locations.volumes#protocols.
+
+     --share-name=SHARE_NAME
+        Share name of the Mount path clients will use.
+
+     Storage pool resource - The Storage Pool to associate with Volume. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --storage-pool on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --storage-pool on the command line with a fully
+        specified name;
+      ◆ provide the argument --location on the command line;
+      ◆ set the property netapp/location;
+      ◆ set the property netapp/region.
+
+     This must be specified.
+
+       --storage-pool=STORAGE_POOL
+          ID of the storage_pool or fully qualified identifier for the
+          storage_pool.
+
+          To set the storage_pool attribute:
+          ▸ provide the argument --storage-pool on the command line.
+
+OPTIONAL FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --description=DESCRIPTION
+        A description of the Cloud NetApp Volume
+
+     --enable-kerberos=ENABLE_KERBEROS
+        Boolean flag indicating whether Volume is a kerberos Volume or not
+
+     --export-policy=[access-type=ACCESS-TYPE],[allowed-clients=ALLOWED-CLIENTS],[has-root-access=HAS-ROOT-ACCESS],[kerberos-5-read-only=KERBEROS-5-READ-ONLY],[kerberos-5-read-write=KERBEROS-5-READ-WRITE],[kerberos-5i-read-only=KERBEROS-5I-READ-ONLY],[kerberos-5i-read-write=KERBEROS-5I-READ-WRITE],[kerberos-5p-read-only=KERBEROS-5P-READ-ONLY],[kerberos-5p-read-write=KERBEROS-5P-READ-WRITE],[nfsv3=NFSV3],[nfsv4=NFSV4]
+        Export Policy of a Cloud NetApp Files Volume. This will be a field
+        similar to network in which export policy fields can be specified as
+        such: --export-policy=allowed-clients=ALLOWED_CLIENTS_IP_ADDRESSES,
+        has-root-access=HAS_ROOT_ACCESS_BOOL,access=ACCESS_TYPE,nfsv3=NFSV3,
+        nfsv4=NFSV4,kerberos-5-read-only=KERBEROS_5_READ_ONLY,
+        kerberos-5-read-write=KERBEROS_5_READ_WRITE,
+        kerberos-5i-read-only=KERBEROS_5I_READ_ONLY,
+        kerberos-5i-read-write=KERBEROS_5I_READ_WRITE,
+        kerberos-5p-read-only=KERBEROS_5P_READ_ONLY,
+        kerberos-5p-read-write=KERBEROS_5P_READ_WRITE
+
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     --security-style=SECURITY_STYLE; default="SECURITY_STYLE_UNSPECIFIED"
+        The security style of the Volume. This can either be UNIX or NTFS.
+
+        SECURITY_STYLE must be one of:
+
+         ntfs
+            NTFS security style for Volume.
+         unix
+            UNIX security style for Volume
+
+     --smb-settings=SMB_SETTING,[SMB_SETTING,...]
+        List of settings specific to SMB protocolfor a Cloud NetApp Files
+        VolumeValid component values are: ENCRYPT_DATA, BROWSABLE,
+        CHANGE_NOTIFY, NON_BROWSABLE, OPLOCKS, SHOW_SNAPSHOT,
+        SHOW_PREVIOUS_VERSIONS, ACCESS_BASED_ENUMERATION,
+        CONTINUOUSLY_AVAILABLE
+
+            For more information, look at https://cloud.google.com/netapp/docs/reference/rest/v1alpha1/projects.locations.volumes#smbsettings.
+
+     --snap-reserve=SNAP_RESERVE
+        The percentage of volume storage reserved for snapshot storage. The
+        default value for this is 0 percent
+
+     --snapshot-daily=[hour=HOUR],[minute=MINUTE],[snapshots-to-keep=SNAPSHOTS-TO-KEEP]
+        Make a snapshot every day e.g. at 06:00, 05:20, 23:50
+
+     --snapshot-directory=SNAPSHOT_DIRECTORY; default="true"
+        Snapshot Directory if enabled (true) makes the Volume contain a
+        read-only .snapshot directory which provides access to each of the
+        volume's snapshots
+
+     --snapshot-hourly=[minute=MINUTE],[snapshots-to-keep=SNAPSHOTS-TO-KEEP]
+        Make a snapshot every hour e.g. at 04:00, 05:20, 06:00
+
+     --snapshot-monthly=[day=DAY],[hour=HOUR],[minute=MINUTE],[snapshots-to-keep=SNAPSHOTS-TO-KEEP]
+        Make a snapshot once a month e.g. at 2nd 04:00, 7th 05:20, 24th 23:50
+
+     --snapshot-weekly=[day=DAY],[hour=HOUR],[minute=MINUTE],[snapshots-to-keep=SNAPSHOTS-TO-KEEP]
+        Make a snapshot every week e.g. at Monday 04:00, Wednesday 05:20,
+        Sunday 23:50
+
+     Snapshot resource - The source Snapshot to create the Volume from. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --source-snapshot on the command line with a
+        fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --source-snapshot on the command line with a
+        fully specified name;
+      ◆ set the property netapp/location;
+      ◆ set the property netapp/region.
+
+     To set the volume attribute:
+      ◆ provide the argument --source-snapshot on the command line with a
+        fully specified name.
+
+       --source-snapshot=SOURCE_SNAPSHOT
+          ID of the snapshot or fully qualified identifier for the snapshot.
+
+          To set the snapshot attribute:
+          ▸ provide the argument --source-snapshot on the command line.
+
+     --unix-permissions=UNIX_PERMISSIONS
+        Unix permissions the mount point will be created with.Unix permissions
+        are only applicable with NFS protocol only
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp volumes create
+
+        $ gcloud beta netapp volumes create
+
diff --git a/gcloud/netapp/volumes/delete b/gcloud/netapp/volumes/delete
new file mode 100644
index 000000000..44011fbb4
--- /dev/null
+++ b/gcloud/netapp/volumes/delete
@@ -0,0 +1,75 @@
+NAME
+    gcloud netapp volumes delete - delete a Cloud NetApp Volume
+
+SYNOPSIS
+    gcloud netapp volumes delete (VOLUME : --location=LOCATION) [--async]
+        [--force] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Delete a Cloud NetApp Volume
+
+EXAMPLES
+    The following command deletes a Volume named NAME in the given location
+
+        $ gcloud netapp volumes delete NAME --location=us-central1
+
+    To delete a Volume named NAME asynchronously, run the following command:
+
+        $ gcloud netapp volumes delete NAME --location=us-central1 --async
+
+POSITIONAL ARGUMENTS
+     Volume resource - The Volume to delete. The arguments in this group can be
+     used to specify the attributes of this resource. (NOTE) Some attributes
+     are not given arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       VOLUME
+          ID of the volume or fully qualified identifier for the volume.
+
+          To set the volume attribute:
+          ▸ provide the argument volume on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the volume.
+
+          To set the location attribute:
+          ▸ provide the argument volume on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --force
+        Forces the deletion of a volume and its child resources, such as
+        snapshots.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp volumes delete
+
+        $ gcloud beta netapp volumes delete
+
diff --git a/gcloud/netapp/volumes/describe b/gcloud/netapp/volumes/describe
new file mode 100644
index 000000000..fa4dfdb31
--- /dev/null
+++ b/gcloud/netapp/volumes/describe
@@ -0,0 +1,62 @@
+NAME
+    gcloud netapp volumes describe - show metadata for a Cloud NetApp Volume
+
+SYNOPSIS
+    gcloud netapp volumes describe (VOLUME : --location=LOCATION)
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Describe a Cloud NetApp Volume
+
+EXAMPLES
+    The following command describe a Volume named NAME in the given location
+
+        $ gcloud netapp volumes describe NAME --location=us-central1
+
+POSITIONAL ARGUMENTS
+     Volume resource - The Volume to describe. The arguments in this group can
+     be used to specify the attributes of this resource. (NOTE) Some attributes
+     are not given arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       VOLUME
+          ID of the volume or fully qualified identifier for the volume.
+
+          To set the volume attribute:
+          ▸ provide the argument volume on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the volume.
+
+          To set the location attribute:
+          ▸ provide the argument volume on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp volumes describe
+
+        $ gcloud beta netapp volumes describe
+
diff --git a/gcloud/netapp/volumes/help b/gcloud/netapp/volumes/help
new file mode 100644
index 000000000..6584e340d
--- /dev/null
+++ b/gcloud/netapp/volumes/help
@@ -0,0 +1,51 @@
+NAME
+    gcloud netapp volumes - create and manage Cloud NetApp Volumes
+
+SYNOPSIS
+    gcloud netapp volumes GROUP | COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Create and manage Cloud NetApp Volumes.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+GROUPS
+    GROUP is one of the following:
+
+     replications
+        Create and manage Cloud NetApp Volume Replications.
+
+     snapshots
+        Create and manage Cloud NetApp Volume Snapshots.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        Create a Cloud NetApp Volume.
+
+     delete
+        Delete a Cloud NetApp Volume.
+
+     describe
+        Show metadata for a Cloud NetApp Volume.
+
+     list
+        List Cloud NetApp Volumes.
+
+     revert
+        Revert a Cloud NetApp Volume back to a specified Snapshot.
+
+     update
+        Update a Cloud NetApp Volume.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp volumes
+
+        $ gcloud beta netapp volumes
+
diff --git a/gcloud/netapp/volumes/list b/gcloud/netapp/volumes/list
new file mode 100644
index 000000000..19ad692f5
--- /dev/null
+++ b/gcloud/netapp/volumes/list
@@ -0,0 +1,86 @@
+NAME
+    gcloud netapp volumes list - list Cloud NetApp Volumes
+
+SYNOPSIS
+    gcloud netapp volumes list [--location=LOCATION] [--filter=EXPRESSION]
+        [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Lists Cloud NetApp Volumes
+
+EXAMPLES
+    The following command lists all Volumes in the given location
+
+        $ gcloud netapp volumes list --location=us-central1
+
+FLAGS
+     Location resource - The location in which to list Volumes. This represents
+     a Cloud resource. (NOTE) Some attributes are not given arguments in this
+     group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --location on the command line with a fully
+        specified name;
+      ◆ uses all locations by default. with a fully specified name;
+      ◆ set the property netapp/location with a fully specified name;
+      ◆ set the property netapp/region with a fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+       --location=LOCATION
+          ID of the location or fully qualified identifier for the location.
+
+          To set the location attribute:
+          ▸ provide the argument --location on the command line;
+          ▸ uses all locations by default.;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp volumes list
+
+        $ gcloud beta netapp volumes list
+
diff --git a/gcloud/netapp/volumes/replications/create b/gcloud/netapp/volumes/replications/create
new file mode 100644
index 000000000..b6b467283
--- /dev/null
+++ b/gcloud/netapp/volumes/replications/create
@@ -0,0 +1,123 @@
+NAME
+    gcloud netapp volumes replications create - create a Cloud NetApp Volume
+        Replication
+
+SYNOPSIS
+    gcloud netapp volumes replications create
+        (REPLICATION : --location=LOCATION)
+        --destination-volume-parameters=[description=DESCRIPTION],
+          [share_name=SHARE_NAME],
+          [storage_pool=STORAGE_POOL],[volume_id=VOLUME_ID]
+        --replication-schedule=REPLICATION_SCHEDULE [--async]
+        [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]]
+        [--volume=VOLUME] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Create a Cloud NetApp Volume Replication.
+
+EXAMPLES
+    The following command creates a Replication named NAME using the required
+    arguments:
+
+        $ gcloud netapp volumes replications create NAME \
+          --location=us-central1 --volume=vol1 \
+          --replication-schedule=EVERY_10_MINUTES \
+          --destination-volume-parameters=storage_pool=sp1,\
+        volume_id=vol2,share_name=share2
+
+POSITIONAL ARGUMENTS
+     Replication resource - The Replication to create. The arguments in this
+     group can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument replication on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the volume attribute:
+      ◆ provide the argument replication on the command line with a fully
+        specified name;
+      ◆ provide the argument --volume on the command line.
+
+     This must be specified.
+
+       REPLICATION
+          ID of the replication or fully qualified identifier for the
+          replication.
+
+          To set the replication attribute:
+          ▸ provide the argument replication on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the replication.
+
+          To set the location attribute:
+          ▸ provide the argument replication on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+REQUIRED FLAGS
+     --destination-volume-parameters=[description=DESCRIPTION],[share_name=SHARE_NAME],[storage_pool=STORAGE_POOL],[volume_id=VOLUME_ID]
+     --replication-schedule=REPLICATION_SCHEDULE
+        The schedule for the Replication.
+
+OPTIONAL FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --description=DESCRIPTION
+        A description of the Cloud NetApp Replication
+
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     Volume resource - The Volume that the Replication is based on This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --location on the command line;
+      ◆ set the property netapp/location;
+      ◆ set the property netapp/region.
+
+       --volume=VOLUME
+          ID of the volume or fully qualified identifier for the volume.
+
+          To set the volume attribute:
+          ▸ provide the argument --volume on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This variant is also available:
+
+        $ gcloud beta netapp volumes replications create
+
diff --git a/gcloud/netapp/volumes/replications/delete b/gcloud/netapp/volumes/replications/delete
new file mode 100644
index 000000000..a904b270b
--- /dev/null
+++ b/gcloud/netapp/volumes/replications/delete
@@ -0,0 +1,105 @@
+NAME
+    gcloud netapp volumes replications delete - delete a Cloud NetApp Volume
+        Replication
+
+SYNOPSIS
+    gcloud netapp volumes replications delete
+        (REPLICATION : --location=LOCATION) [--async] [--volume=VOLUME]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Delete a Cloud NetApp Volume Replication.
+
+EXAMPLES
+    The following command deletes a Replication named NAME using the required
+    arguments:
+
+        $ gcloud netapp volumes replications delete NAME \
+          --location=us-central1 --volume=vol1
+
+    To delete a Replication named NAME asynchronously, run the following
+    command:
+
+        $ gcloud netapp volumes replications delete NAME \
+          --location=us-central1 --volume=vol1 --async
+
+POSITIONAL ARGUMENTS
+     Replication resource - The Replication to delete. The arguments in this
+     group can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument replication on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the volume attribute:
+      ◆ provide the argument replication on the command line with a fully
+        specified name;
+      ◆ provide the argument --volume on the command line.
+
+     This must be specified.
+
+       REPLICATION
+          ID of the replication or fully qualified identifier for the
+          replication.
+
+          To set the replication attribute:
+          ▸ provide the argument replication on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the replication.
+
+          To set the location attribute:
+          ▸ provide the argument replication on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     Volume resource - The Volume that the Replication is based on This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --location on the command line;
+      ◆ set the property netapp/location;
+      ◆ set the property netapp/region.
+
+       --volume=VOLUME
+          ID of the volume or fully qualified identifier for the volume.
+
+          To set the volume attribute:
+          ▸ provide the argument --volume on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This variant is also available:
+
+        $ gcloud beta netapp volumes replications delete
+
diff --git a/gcloud/netapp/volumes/replications/describe b/gcloud/netapp/volumes/replications/describe
new file mode 100644
index 000000000..013b05dd9
--- /dev/null
+++ b/gcloud/netapp/volumes/replications/describe
@@ -0,0 +1,95 @@
+NAME
+    gcloud netapp volumes replications describe - describe a Cloud NetApp
+        Volume Replication
+
+SYNOPSIS
+    gcloud netapp volumes replications describe
+        (REPLICATION : --location=LOCATION) [--volume=VOLUME]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Describe a Cloud NetApp Volume Replication.
+
+EXAMPLES
+    The following command describes a Replication named NAME in the given
+    location and volume:
+
+        $ gcloud netapp volumes replications describe NAME \
+          --location=us-central1 --volume=vol1
+
+POSITIONAL ARGUMENTS
+     Replication resource - The Replication to describe. The arguments in this
+     group can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument replication on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the volume attribute:
+      ◆ provide the argument replication on the command line with a fully
+        specified name;
+      ◆ provide the argument --volume on the command line.
+
+     This must be specified.
+
+       REPLICATION
+          ID of the replication or fully qualified identifier for the
+          replication.
+
+          To set the replication attribute:
+          ▸ provide the argument replication on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the replication.
+
+          To set the location attribute:
+          ▸ provide the argument replication on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+FLAGS
+     Volume resource - The Volume that the Replication is based on This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --location on the command line;
+      ◆ set the property netapp/location;
+      ◆ set the property netapp/region.
+
+       --volume=VOLUME
+          ID of the volume or fully qualified identifier for the volume.
+
+          To set the volume attribute:
+          ▸ provide the argument --volume on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This variant is also available:
+
+        $ gcloud beta netapp volumes replications describe
+
diff --git a/gcloud/netapp/volumes/replications/help b/gcloud/netapp/volumes/replications/help
new file mode 100644
index 000000000..db728ffdf
--- /dev/null
+++ b/gcloud/netapp/volumes/replications/help
@@ -0,0 +1,47 @@
+NAME
+    gcloud netapp volumes replications - create and manage Cloud NetApp Volume
+        Replications
+
+SYNOPSIS
+    gcloud netapp volumes replications COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Create and manage Cloud NetApp Volume Replications.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        Create a Cloud NetApp Volume Replication.
+
+     delete
+        Delete a Cloud NetApp Volume Replication.
+
+     describe
+        Describe a Cloud NetApp Volume Replication.
+
+     list
+        List Cloud NetApp Volume Replications.
+
+     resume
+        Resume a Cloud NetApp Volume Replication.
+
+     reverse
+        Reverse a Cloud NetApp Volume Replication's direction.
+
+     stop
+        Stop a Cloud NetApp Volume Replication.
+
+     update
+        Update a Cloud NetApp Volume Replication.
+
+NOTES
+    This variant is also available:
+
+        $ gcloud beta netapp volumes replications
+
diff --git a/gcloud/netapp/volumes/replications/list b/gcloud/netapp/volumes/replications/list
new file mode 100644
index 000000000..ea8dddfe5
--- /dev/null
+++ b/gcloud/netapp/volumes/replications/list
@@ -0,0 +1,111 @@
+NAME
+    gcloud netapp volumes replications list - list Cloud NetApp Volume
+        Replications
+
+SYNOPSIS
+    gcloud netapp volumes replications list [--location=LOCATION]
+        [--volume=VOLUME] [--filter=EXPRESSION] [--limit=LIMIT]
+        [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Lists Cloud NetApp Volume Replications.
+
+EXAMPLES
+    The following command lists all Replications in the given location and
+    volume:
+
+        $ gcloud netapp volumes replications list --location=us-central1 \
+          --volume=vol1
+
+FLAGS
+     Location resource - The location in which to list Volume Replications.
+     This represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --location on the command line with a fully
+        specified name;
+      ◆ uses all locations by default. with a fully specified name;
+      ◆ set the property netapp/location with a fully specified name;
+      ◆ set the property netapp/region with a fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+       --location=LOCATION
+          ID of the location or fully qualified identifier for the location.
+
+          To set the location attribute:
+          ▸ provide the argument --location on the command line;
+          ▸ uses all locations by default.;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+     Volume resource - The Volume that the Replication is based on This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --location on the command line;
+      ◆ set the property netapp/location;
+      ◆ set the property netapp/region.
+
+       --volume=VOLUME
+          ID of the volume or fully qualified identifier for the volume.
+
+          To set the volume attribute:
+          ▸ provide the argument --volume on the command line.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This variant is also available:
+
+        $ gcloud beta netapp volumes replications list
+
diff --git a/gcloud/netapp/volumes/replications/resume b/gcloud/netapp/volumes/replications/resume
new file mode 100644
index 000000000..de0aa3935
--- /dev/null
+++ b/gcloud/netapp/volumes/replications/resume
@@ -0,0 +1,105 @@
+NAME
+    gcloud netapp volumes replications resume - resume a Cloud NetApp Volume
+        Replication
+
+SYNOPSIS
+    gcloud netapp volumes replications resume
+        (REPLICATION : --location=LOCATION) [--async] [--volume=VOLUME]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Resume a Cloud NetApp Volume Replication.
+
+EXAMPLES
+    The following command resumes a Replication named NAME using the required
+    arguments:
+
+        $ gcloud netapp volumes replications resume NAME \
+          --location=us-central1 --volume=vol1
+
+    To resume a Replication named NAME asynchronously, run the following
+    command:
+
+        $ gcloud netapp volumes replications resume NAME \
+          --location=us-central1 --volume=vol1 --async
+
+POSITIONAL ARGUMENTS
+     Replication resource - The Replication to create. The arguments in this
+     group can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument replication on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the volume attribute:
+      ◆ provide the argument replication on the command line with a fully
+        specified name;
+      ◆ provide the argument --volume on the command line.
+
+     This must be specified.
+
+       REPLICATION
+          ID of the replication or fully qualified identifier for the
+          replication.
+
+          To set the replication attribute:
+          ▸ provide the argument replication on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the replication.
+
+          To set the location attribute:
+          ▸ provide the argument replication on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     Volume resource - The Volume that the Replication is based on This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --location on the command line;
+      ◆ set the property netapp/location;
+      ◆ set the property netapp/region.
+
+       --volume=VOLUME
+          ID of the volume or fully qualified identifier for the volume.
+
+          To set the volume attribute:
+          ▸ provide the argument --volume on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This variant is also available:
+
+        $ gcloud beta netapp volumes replications resume
+
diff --git a/gcloud/netapp/volumes/replications/reverse b/gcloud/netapp/volumes/replications/reverse
new file mode 100644
index 000000000..d31cbe70f
--- /dev/null
+++ b/gcloud/netapp/volumes/replications/reverse
@@ -0,0 +1,105 @@
+NAME
+    gcloud netapp volumes replications reverse - reverse a Cloud NetApp Volume
+        Replication's direction
+
+SYNOPSIS
+    gcloud netapp volumes replications reverse
+        (REPLICATION : --location=LOCATION) [--async] [--volume=VOLUME]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Reverse a Cloud NetApp Volume Replication.
+
+EXAMPLES
+    The following command reverses a Replication named NAME using the required
+    arguments:
+
+        $ gcloud netapp volumes replications reverse NAME \
+          --location=us-central1 --volume=vol1
+
+    To reverse a Replication named NAME asynchronously, run the following
+    command:
+
+        $ gcloud netapp volumes replications reverse NAME \
+          --location=us-central1 --volume=vol1 --async
+
+POSITIONAL ARGUMENTS
+     Replication resource - The Replication to reverse direction. The arguments
+     in this group can be used to specify the attributes of this resource.
+     (NOTE) Some attributes are not given arguments in this group but can be
+     set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument replication on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the volume attribute:
+      ◆ provide the argument replication on the command line with a fully
+        specified name;
+      ◆ provide the argument --volume on the command line.
+
+     This must be specified.
+
+       REPLICATION
+          ID of the replication or fully qualified identifier for the
+          replication.
+
+          To set the replication attribute:
+          ▸ provide the argument replication on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the replication.
+
+          To set the location attribute:
+          ▸ provide the argument replication on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     Volume resource - The source Volume to reverse the Replication direction
+     of This represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --location on the command line;
+      ◆ set the property netapp/location;
+      ◆ set the property netapp/region.
+
+       --volume=VOLUME
+          ID of the volume or fully qualified identifier for the volume.
+
+          To set the volume attribute:
+          ▸ provide the argument --volume on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This variant is also available:
+
+        $ gcloud beta netapp volumes replications reverse
+
diff --git a/gcloud/netapp/volumes/replications/stop b/gcloud/netapp/volumes/replications/stop
new file mode 100644
index 000000000..79159a064
--- /dev/null
+++ b/gcloud/netapp/volumes/replications/stop
@@ -0,0 +1,110 @@
+NAME
+    gcloud netapp volumes replications stop - stop a Cloud NetApp Volume
+        Replication
+
+SYNOPSIS
+    gcloud netapp volumes replications stop (REPLICATION : --location=LOCATION)
+        [--async] [--force] [--volume=VOLUME] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Stop a Cloud NetApp Volume Replication.
+
+EXAMPLES
+    The following command stops a Replication named NAME using the required
+    arguments:
+
+        $ gcloud netapp volumes replications stop NAME \
+          --location=us-central1 --volume=vol1
+
+    To stop a Replication named NAME asynchronously, run the following command:
+
+        $ gcloud netapp volumes replications stop NAME \
+          --location=us-central1 --volume=vol1 --async
+
+POSITIONAL ARGUMENTS
+     Replication resource - The Replication to create. The arguments in this
+     group can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument replication on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the volume attribute:
+      ◆ provide the argument replication on the command line with a fully
+        specified name;
+      ◆ provide the argument --volume on the command line.
+
+     This must be specified.
+
+       REPLICATION
+          ID of the replication or fully qualified identifier for the
+          replication.
+
+          To set the replication attribute:
+          ▸ provide the argument replication on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the replication.
+
+          To set the location attribute:
+          ▸ provide the argument replication on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --force
+        Indicates whether to stop replication forcefully while data transfer is
+        in progress. Warning! if force is true, this will abort any current
+        transfers and can lead to data loss due to partial transfer. If force
+        is false, stop replication will fail while data transfer is in progress
+        and you will need to retry later.
+
+     Volume resource - The Volume that the Replication is based on This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --location on the command line;
+      ◆ set the property netapp/location;
+      ◆ set the property netapp/region.
+
+       --volume=VOLUME
+          ID of the volume or fully qualified identifier for the volume.
+
+          To set the volume attribute:
+          ▸ provide the argument --volume on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This variant is also available:
+
+        $ gcloud beta netapp volumes replications stop
+
diff --git a/gcloud/netapp/volumes/replications/update b/gcloud/netapp/volumes/replications/update
new file mode 100644
index 000000000..bd02e62c9
--- /dev/null
+++ b/gcloud/netapp/volumes/replications/update
@@ -0,0 +1,139 @@
+NAME
+    gcloud netapp volumes replications update - update a Cloud NetApp Volume
+        Replication
+
+SYNOPSIS
+    gcloud netapp volumes replications update
+        (REPLICATION : --location=LOCATION) [--async]
+        [--description=DESCRIPTION]
+        [--replication-schedule=REPLICATION_SCHEDULE]
+        [--update-labels=[KEY=VALUE,...]] [--volume=VOLUME]
+        [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Update a Cloud NetApp Volume Replication and its specified parameters.
+
+EXAMPLES
+    The following command updates a Replication named NAME and its specified
+    parameters:
+
+        $ gcloud netapp volumes replications update NAME \
+          --location=us-central1 --volume=vol1 \
+          --replication-schedule=EVERY_5_MINUTES \
+          --description="new description"
+
+POSITIONAL ARGUMENTS
+     Replication resource - The Replication to update. The arguments in this
+     group can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument replication on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the volume attribute:
+      ◆ provide the argument replication on the command line with a fully
+        specified name;
+      ◆ provide the argument --volume on the command line.
+
+     This must be specified.
+
+       REPLICATION
+          ID of the replication or fully qualified identifier for the
+          replication.
+
+          To set the replication attribute:
+          ▸ provide the argument replication on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the replication.
+
+          To set the location attribute:
+          ▸ provide the argument replication on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --description=DESCRIPTION
+        A description of the Cloud NetApp Replication
+
+     --replication-schedule=REPLICATION_SCHEDULE
+        The schedule for the Replication.
+
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     Volume resource - The Volume that the Replication is based on This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --location on the command line;
+      ◆ set the property netapp/location;
+      ◆ set the property netapp/region.
+
+       --volume=VOLUME
+          ID of the volume or fully qualified identifier for the volume.
+
+          To set the volume attribute:
+          ▸ provide the argument --volume on the command line.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud netapp volumes replications update --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud netapp volumes replications update --clear-labels \
+                --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This variant is also available:
+
+        $ gcloud beta netapp volumes replications update
+
diff --git a/gcloud/netapp/volumes/revert b/gcloud/netapp/volumes/revert
new file mode 100644
index 000000000..bc18e5132
--- /dev/null
+++ b/gcloud/netapp/volumes/revert
@@ -0,0 +1,99 @@
+NAME
+    gcloud netapp volumes revert - revert a Cloud NetApp Volume back to a
+        specified Snapshot
+
+SYNOPSIS
+    gcloud netapp volumes revert (VOLUME : --location=LOCATION)
+        --snapshot=SNAPSHOT [--async] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Revert a Cloud NetApp Volume back to a specified source Snapshot
+
+EXAMPLES
+    The following command reverts a Volume named NAME in the given location and
+    snapshot
+
+        $ gcloud netapp volumes revert NAME --location=us-central1 \
+          --snapshot="snapshot1"
+
+POSITIONAL ARGUMENTS
+     Volume resource - The Volume to revert. The arguments in this group can be
+     used to specify the attributes of this resource. (NOTE) Some attributes
+     are not given arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       VOLUME
+          ID of the volume or fully qualified identifier for the volume.
+
+          To set the volume attribute:
+          ▸ provide the argument volume on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the volume.
+
+          To set the location attribute:
+          ▸ provide the argument volume on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+REQUIRED FLAGS
+     Snapshot resource - The Snapshot to revert the Volume back to. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --snapshot on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --snapshot on the command line with a fully
+        specified name;
+      ◆ set the property netapp/location;
+      ◆ set the property netapp/region.
+
+     To set the volume attribute:
+      ◆ provide the argument --snapshot on the command line with a fully
+        specified name.
+
+     This must be specified.
+
+       --snapshot=SNAPSHOT
+          ID of the snapshot or fully qualified identifier for the snapshot.
+
+          To set the snapshot attribute:
+          ▸ provide the argument --snapshot on the command line.
+
+OPTIONAL FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp volumes revert
+
+        $ gcloud beta netapp volumes revert
+
diff --git a/gcloud/netapp/volumes/snapshots/create b/gcloud/netapp/volumes/snapshots/create
new file mode 100644
index 000000000..bb2a35332
--- /dev/null
+++ b/gcloud/netapp/volumes/snapshots/create
@@ -0,0 +1,111 @@
+NAME
+    gcloud netapp volumes snapshots create - create a Cloud NetApp Volume
+        Snapshot
+
+SYNOPSIS
+    gcloud netapp volumes snapshots create (SNAPSHOT : --location=LOCATION)
+        [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]]
+        [--volume=VOLUME] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Create a Cloud NetApp Volume Snapshot.
+
+EXAMPLES
+    The following command creates a Snapshot named NAME using the required
+    arguments:
+
+        $ gcloud netapp volumes snapshots create NAME \
+          --location=us-central1 --volume=vol1
+
+POSITIONAL ARGUMENTS
+     Snapshot resource - The Snapshot to create. The arguments in this group
+     can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument snapshot on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the volume attribute:
+      ◆ provide the argument snapshot on the command line with a fully
+        specified name;
+      ◆ provide the argument --volume on the command line.
+
+     This must be specified.
+
+       SNAPSHOT
+          ID of the snapshot or fully qualified identifier for the snapshot.
+
+          To set the snapshot attribute:
+          ▸ provide the argument snapshot on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the snapshot.
+
+          To set the location attribute:
+          ▸ provide the argument snapshot on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --description=DESCRIPTION
+        A description of the Cloud NetApp Snapshot
+
+     --labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to add.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     Volume resource - The Volume to take a Snapshot of. This represents a
+     Cloud resource. (NOTE) Some attributes are not given arguments in this
+     group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --location on the command line;
+      ◆ set the property netapp/location;
+      ◆ set the property netapp/region.
+
+       --volume=VOLUME
+          ID of the volume or fully qualified identifier for the volume.
+
+          To set the volume attribute:
+          ▸ provide the argument --volume on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp volumes snapshots create
+
+        $ gcloud beta netapp volumes snapshots create
+
diff --git a/gcloud/netapp/volumes/snapshots/delete b/gcloud/netapp/volumes/snapshots/delete
new file mode 100644
index 000000000..cdfbd63e8
--- /dev/null
+++ b/gcloud/netapp/volumes/snapshots/delete
@@ -0,0 +1,104 @@
+NAME
+    gcloud netapp volumes snapshots delete - delete a Cloud NetApp Volume
+        Snapshot
+
+SYNOPSIS
+    gcloud netapp volumes snapshots delete (SNAPSHOT : --location=LOCATION)
+        [--async] [--volume=VOLUME] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Delete a Cloud NetApp Volume Snapshot.
+
+EXAMPLES
+    The following command deletes a Snapshot named NAME in the given location
+    and volume:
+
+        $ gcloud netapp volumes snapshots delete NAME \
+          --location=us-central1 --volume=vol1
+
+    To delete a Snapshot named NAME asynchronously, run the following command:
+
+        $ gcloud netapp volumes snapshots delete NAME \
+          --location=us-central1 --volume=vol1 --async
+
+POSITIONAL ARGUMENTS
+     Snapshot resource - The Snapshot to delete. The arguments in this group
+     can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument snapshot on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the volume attribute:
+      ◆ provide the argument snapshot on the command line with a fully
+        specified name;
+      ◆ provide the argument --volume on the command line.
+
+     This must be specified.
+
+       SNAPSHOT
+          ID of the snapshot or fully qualified identifier for the snapshot.
+
+          To set the snapshot attribute:
+          ▸ provide the argument snapshot on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the snapshot.
+
+          To set the location attribute:
+          ▸ provide the argument snapshot on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     Volume resource - The Volume to take a Snapshot of. This represents a
+     Cloud resource. (NOTE) Some attributes are not given arguments in this
+     group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --location on the command line;
+      ◆ set the property netapp/location;
+      ◆ set the property netapp/region.
+
+       --volume=VOLUME
+          ID of the volume or fully qualified identifier for the volume.
+
+          To set the volume attribute:
+          ▸ provide the argument --volume on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp volumes snapshots delete
+
+        $ gcloud beta netapp volumes snapshots delete
+
diff --git a/gcloud/netapp/volumes/snapshots/describe b/gcloud/netapp/volumes/snapshots/describe
new file mode 100644
index 000000000..12659eb6c
--- /dev/null
+++ b/gcloud/netapp/volumes/snapshots/describe
@@ -0,0 +1,95 @@
+NAME
+    gcloud netapp volumes snapshots describe - describe a Cloud NetApp Volume
+        Snapshot
+
+SYNOPSIS
+    gcloud netapp volumes snapshots describe (SNAPSHOT : --location=LOCATION)
+        [--volume=VOLUME] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Describe a Cloud NetApp Volume Snapshot.
+
+EXAMPLES
+    The following command describes a Snapshot named NAME in the given location
+    and volume:
+
+        $ gcloud netapp volumes snapshots describe NAME \
+          --location=us-central1 --volume=vol1
+
+POSITIONAL ARGUMENTS
+     Snapshot resource - The Snapshot to describe. The arguments in this group
+     can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument snapshot on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the volume attribute:
+      ◆ provide the argument snapshot on the command line with a fully
+        specified name;
+      ◆ provide the argument --volume on the command line.
+
+     This must be specified.
+
+       SNAPSHOT
+          ID of the snapshot or fully qualified identifier for the snapshot.
+
+          To set the snapshot attribute:
+          ▸ provide the argument snapshot on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the snapshot.
+
+          To set the location attribute:
+          ▸ provide the argument snapshot on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+FLAGS
+     Volume resource - The Volume to take a Snapshot of. This represents a
+     Cloud resource. (NOTE) Some attributes are not given arguments in this
+     group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --location on the command line;
+      ◆ set the property netapp/location;
+      ◆ set the property netapp/region.
+
+       --volume=VOLUME
+          ID of the volume or fully qualified identifier for the volume.
+
+          To set the volume attribute:
+          ▸ provide the argument --volume on the command line.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp volumes snapshots describe
+
+        $ gcloud beta netapp volumes snapshots describe
+
diff --git a/gcloud/netapp/volumes/snapshots/help b/gcloud/netapp/volumes/snapshots/help
new file mode 100644
index 000000000..e51319a62
--- /dev/null
+++ b/gcloud/netapp/volumes/snapshots/help
@@ -0,0 +1,40 @@
+NAME
+    gcloud netapp volumes snapshots - create and manage Cloud NetApp Volume
+        Snapshots
+
+SYNOPSIS
+    gcloud netapp volumes snapshots COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Create and manage Cloud NetApp Volume Snapshots.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        Create a Cloud NetApp Volume Snapshot.
+
+     delete
+        Delete a Cloud NetApp Volume Snapshot.
+
+     describe
+        Describe a Cloud NetApp Volume Snapshot.
+
+     list
+        List Cloud NetApp Volume Snapshots.
+
+     update
+        Update a Cloud NetApp Volume Snapshot.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp volumes snapshots
+
+        $ gcloud beta netapp volumes snapshots
+
diff --git a/gcloud/netapp/volumes/snapshots/list b/gcloud/netapp/volumes/snapshots/list
new file mode 100644
index 000000000..b22884255
--- /dev/null
+++ b/gcloud/netapp/volumes/snapshots/list
@@ -0,0 +1,111 @@
+NAME
+    gcloud netapp volumes snapshots list - list Cloud NetApp Volume Snapshots
+
+SYNOPSIS
+    gcloud netapp volumes snapshots list [--location=LOCATION]
+        [--volume=VOLUME] [--filter=EXPRESSION] [--limit=LIMIT]
+        [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Lists Cloud NetApp Volume Snapshots.
+
+EXAMPLES
+    The following command lists all Snapshots in the given location and volume:
+
+        $ gcloud netapp volumes snapshots list --location=us-central1 \
+          --volume=vol1
+
+FLAGS
+     Location resource - The location in which to list Volume Snapshots. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --location on the command line with a fully
+        specified name;
+      ◆ uses all locations by default. with a fully specified name;
+      ◆ set the property netapp/location with a fully specified name;
+      ◆ set the property netapp/region with a fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+       --location=LOCATION
+          ID of the location or fully qualified identifier for the location.
+
+          To set the location attribute:
+          ▸ provide the argument --location on the command line;
+          ▸ uses all locations by default.;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+     Volume resource - The Volume to take a Snapshot of. This represents a
+     Cloud resource. (NOTE) Some attributes are not given arguments in this
+     group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --location on the command line;
+      ◆ set the property netapp/location;
+      ◆ set the property netapp/region.
+
+       --volume=VOLUME
+          ID of the volume or fully qualified identifier for the volume.
+
+          To set the volume attribute:
+          ▸ provide the argument --volume on the command line.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp volumes snapshots list
+
+        $ gcloud beta netapp volumes snapshots list
+
diff --git a/gcloud/netapp/volumes/snapshots/update b/gcloud/netapp/volumes/snapshots/update
new file mode 100644
index 000000000..4eda9de46
--- /dev/null
+++ b/gcloud/netapp/volumes/snapshots/update
@@ -0,0 +1,134 @@
+NAME
+    gcloud netapp volumes snapshots update - update a Cloud NetApp Volume
+        Snapshot
+
+SYNOPSIS
+    gcloud netapp volumes snapshots update (SNAPSHOT : --location=LOCATION)
+        [--async] [--description=DESCRIPTION] [--update-labels=[KEY=VALUE,...]]
+        [--volume=VOLUME] [--clear-labels | --remove-labels=[KEY,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Update a Cloud NetApp Volume Snapshot and its specified parameters.
+
+EXAMPLES
+    The following command updates a Snapshot named NAME and its specified
+    parameters:
+
+        $ gcloud netapp volumes snapshots update NAME \
+          --location=us-central1 --description="new" \
+          --update-labels=key2=val2 --volume=vol1
+
+POSITIONAL ARGUMENTS
+     Snapshot resource - The Snapshot to update. The arguments in this group
+     can be used to specify the attributes of this resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument snapshot on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the volume attribute:
+      ◆ provide the argument snapshot on the command line with a fully
+        specified name;
+      ◆ provide the argument --volume on the command line.
+
+     This must be specified.
+
+       SNAPSHOT
+          ID of the snapshot or fully qualified identifier for the snapshot.
+
+          To set the snapshot attribute:
+          ▸ provide the argument snapshot on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the snapshot.
+
+          To set the location attribute:
+          ▸ provide the argument snapshot on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --description=DESCRIPTION
+        A description of the Cloud NetApp Snapshot
+
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     Volume resource - The Volume to take a Snapshot of. This represents a
+     Cloud resource. (NOTE) Some attributes are not given arguments in this
+     group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --location on the command line;
+      ◆ set the property netapp/location;
+      ◆ set the property netapp/region.
+
+       --volume=VOLUME
+          ID of the volume or fully qualified identifier for the volume.
+
+          To set the volume attribute:
+          ▸ provide the argument --volume on the command line.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud netapp volumes snapshots update --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud netapp volumes snapshots update --clear-labels \
+                --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp volumes snapshots update
+
+        $ gcloud beta netapp volumes snapshots update
+
diff --git a/gcloud/netapp/volumes/update b/gcloud/netapp/volumes/update
new file mode 100644
index 000000000..594948640
--- /dev/null
+++ b/gcloud/netapp/volumes/update
@@ -0,0 +1,252 @@
+NAME
+    gcloud netapp volumes update - update a Cloud NetApp Volume
+
+SYNOPSIS
+    gcloud netapp volumes update (VOLUME : --location=LOCATION) [--async]
+        [--capacity=CAPACITY] [--description=DESCRIPTION]
+        [--enable-kerberos=ENABLE_KERBEROS]
+        [--export-policy=[access-type=ACCESS-TYPE],
+          [allowed-clients=ALLOWED-CLIENTS],[has-root-access=HAS-ROOT-ACCESS],
+          [kerberos-5-read-only=KERBEROS-5-READ-ONLY],
+          [kerberos-5-read-write=KERBEROS-5-READ-WRITE],
+          [kerberos-5i-read-only=KERBEROS-5I-READ-ONLY],
+          [kerberos-5i-read-write=KERBEROS-5I-READ-WRITE],
+          [kerberos-5p-read-only=KERBEROS-5P-READ-ONLY],
+          [kerberos-5p-read-write=KERBEROS-5P-READ-WRITE],
+          [nfsv3=NFSV3],[nfsv4=NFSV4]] [--protocols=PROTOCOL,[PROTOCOL,...]]
+        [--security-style=SECURITY_STYLE; default="SECURITY_STYLE_UNSPECIFIED"]
+        [--share-name=SHARE_NAME]
+        [--smb-settings=SMB_SETTING,[SMB_SETTING,...]]
+        [--snap-reserve=SNAP_RESERVE]
+        [--snapshot-daily=[hour=HOUR],
+          [minute=MINUTE],[snapshots-to-keep=SNAPSHOTS-TO-KEEP]]
+        [--snapshot-directory=SNAPSHOT_DIRECTORY; default="true"]
+        [--snapshot-hourly=[minute=MINUTE],
+          [snapshots-to-keep=SNAPSHOTS-TO-KEEP]]
+        [--snapshot-monthly=[day=DAY],
+          [hour=HOUR],[minute=MINUTE],[snapshots-to-keep=SNAPSHOTS-TO-KEEP]]
+        [--snapshot-weekly=[day=DAY],
+          [hour=HOUR],[minute=MINUTE],[snapshots-to-keep=SNAPSHOTS-TO-KEEP]]
+        [--source-snapshot=SOURCE_SNAPSHOT] [--storage-pool=STORAGE_POOL]
+        [--unix-permissions=UNIX_PERMISSIONS] [--update-labels=[KEY=VALUE,...]]
+        [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Update a Cloud NetApp Volume and its specified parameters
+
+EXAMPLES
+    The following command updates a Volume named NAME and its specified
+    parameters
+
+        $ gcloud netapp volumes update NAME --location=us-central1 \
+          --capacity=4096 --description="new description" \
+          --enable-kerberos=false --storage-pool=sp3 \
+          --unix-permissions=0777
+
+POSITIONAL ARGUMENTS
+     Volume resource - The Volume to update. The arguments in this group can be
+     used to specify the attributes of this resource. (NOTE) Some attributes
+     are not given arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument volume on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       VOLUME
+          ID of the volume or fully qualified identifier for the volume.
+
+          To set the volume attribute:
+          ▸ provide the argument volume on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location of the volume.
+
+          To set the location attribute:
+          ▸ provide the argument volume on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line;
+          ▸ set the property netapp/location;
+          ▸ set the property netapp/region.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --capacity=CAPACITY
+        The desired capacity of the Volume in GiB or TiB units.If no capacity
+        unit is specified, GiB is assumed.
+
+     --description=DESCRIPTION
+        A description of the Cloud NetApp Volume
+
+     --enable-kerberos=ENABLE_KERBEROS
+        Boolean flag indicating whether Volume is a kerberos Volume or not
+
+     --export-policy=[access-type=ACCESS-TYPE],[allowed-clients=ALLOWED-CLIENTS],[has-root-access=HAS-ROOT-ACCESS],[kerberos-5-read-only=KERBEROS-5-READ-ONLY],[kerberos-5-read-write=KERBEROS-5-READ-WRITE],[kerberos-5i-read-only=KERBEROS-5I-READ-ONLY],[kerberos-5i-read-write=KERBEROS-5I-READ-WRITE],[kerberos-5p-read-only=KERBEROS-5P-READ-ONLY],[kerberos-5p-read-write=KERBEROS-5P-READ-WRITE],[nfsv3=NFSV3],[nfsv4=NFSV4]
+        Export Policy of a Cloud NetApp Files Volume. This will be a field
+        similar to network in which export policy fields can be specified as
+        such: --export-policy=allowed-clients=ALLOWED_CLIENTS_IP_ADDRESSES,
+        has-root-access=HAS_ROOT_ACCESS_BOOL,access=ACCESS_TYPE,nfsv3=NFSV3,
+        nfsv4=NFSV4,kerberos-5-read-only=KERBEROS_5_READ_ONLY,
+        kerberos-5-read-write=KERBEROS_5_READ_WRITE,
+        kerberos-5i-read-only=KERBEROS_5I_READ_ONLY,
+        kerberos-5i-read-write=KERBEROS_5I_READ_WRITE,
+        kerberos-5p-read-only=KERBEROS_5P_READ_ONLY,
+        kerberos-5p-read-write=KERBEROS_5P_READ_WRITE
+
+     --protocols=PROTOCOL,[PROTOCOL,...]
+        Type of File System protocols for the Cloud NetApp Files VolumeValid
+        component values are: NFSV3, NFSV4, SMB
+
+            For more information, look athttps://cloud.google.com/netapp/docs/reference/rest/v1alpha1/projects.locations.volumes#protocols.
+
+     --security-style=SECURITY_STYLE; default="SECURITY_STYLE_UNSPECIFIED"
+        The security style of the Volume. This can either be UNIX or NTFS.
+
+        SECURITY_STYLE must be one of:
+
+         ntfs
+            NTFS security style for Volume.
+         unix
+            UNIX security style for Volume
+
+     --share-name=SHARE_NAME
+        Share name of the Mount path clients will use.
+
+     --smb-settings=SMB_SETTING,[SMB_SETTING,...]
+        List of settings specific to SMB protocolfor a Cloud NetApp Files
+        VolumeValid component values are: ENCRYPT_DATA, BROWSABLE,
+        CHANGE_NOTIFY, NON_BROWSABLE, OPLOCKS, SHOW_SNAPSHOT,
+        SHOW_PREVIOUS_VERSIONS, ACCESS_BASED_ENUMERATION,
+        CONTINUOUSLY_AVAILABLE
+
+            For more information, look at https://cloud.google.com/netapp/docs/reference/rest/v1alpha1/projects.locations.volumes#smbsettings.
+
+     --snap-reserve=SNAP_RESERVE
+        The percentage of volume storage reserved for snapshot storage. The
+        default value for this is 0 percent
+
+     --snapshot-daily=[hour=HOUR],[minute=MINUTE],[snapshots-to-keep=SNAPSHOTS-TO-KEEP]
+        Make a snapshot every day e.g. at 06:00, 05:20, 23:50
+
+     --snapshot-directory=SNAPSHOT_DIRECTORY; default="true"
+        Snapshot Directory if enabled (true) makes the Volume contain a
+        read-only .snapshot directory which provides access to each of the
+        volume's snapshots
+
+     --snapshot-hourly=[minute=MINUTE],[snapshots-to-keep=SNAPSHOTS-TO-KEEP]
+        Make a snapshot every hour e.g. at 04:00, 05:20, 06:00
+
+     --snapshot-monthly=[day=DAY],[hour=HOUR],[minute=MINUTE],[snapshots-to-keep=SNAPSHOTS-TO-KEEP]
+        Make a snapshot once a month e.g. at 2nd 04:00, 7th 05:20, 24th 23:50
+
+     --snapshot-weekly=[day=DAY],[hour=HOUR],[minute=MINUTE],[snapshots-to-keep=SNAPSHOTS-TO-KEEP]
+        Make a snapshot every week e.g. at Monday 04:00, Wednesday 05:20,
+        Sunday 23:50
+
+     Snapshot resource - The source Snapshot to create the Volume from. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --source-snapshot on the command line with a
+        fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --source-snapshot on the command line with a
+        fully specified name;
+      ◆ set the property netapp/location;
+      ◆ set the property netapp/region.
+
+     To set the volume attribute:
+      ◆ provide the argument --source-snapshot on the command line with a
+        fully specified name.
+
+       --source-snapshot=SOURCE_SNAPSHOT
+          ID of the snapshot or fully qualified identifier for the snapshot.
+
+          To set the snapshot attribute:
+          ▸ provide the argument --source-snapshot on the command line.
+
+     Storage pool resource - The Storage Pool to associate with Volume. This
+     represents a Cloud resource. (NOTE) Some attributes are not given
+     arguments in this group but can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument --storage-pool on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     To set the location attribute:
+      ◆ provide the argument --storage-pool on the command line with a fully
+        specified name;
+      ◆ provide the argument --location on the command line;
+      ◆ set the property netapp/location;
+      ◆ set the property netapp/region.
+
+       --storage-pool=STORAGE_POOL
+          ID of the storage_pool or fully qualified identifier for the
+          storage_pool.
+
+          To set the storage_pool attribute:
+          ▸ provide the argument --storage-pool on the command line.
+
+     --unix-permissions=UNIX_PERMISSIONS
+        Unix permissions the mount point will be created with.Unix permissions
+        are only applicable with NFS protocol only
+
+     --update-labels=[KEY=VALUE,...]
+        List of label KEY=VALUE pairs to update. If a label exists, its value
+        is modified. Otherwise, a new label is created.
+
+        Keys must start with a lowercase character and contain only hyphens
+        (-), underscores (_), lowercase characters, and numbers. Values must
+        contain only hyphens (-), underscores (_), lowercase characters, and
+        numbers.
+
+     At most one of these can be specified:
+
+       --clear-labels
+          Remove all labels. If --update-labels is also specified then
+          --clear-labels is applied first.
+
+          For example, to remove all labels:
+
+              $ gcloud netapp volumes update --clear-labels
+
+          To remove all existing labels and create two new labels, foo and baz:
+
+              $ gcloud netapp volumes update --clear-labels \
+                --update-labels foo=bar,baz=qux
+
+       --remove-labels=[KEY,...]
+          List of label keys to remove. If a label does not exist it is
+          silently ignored. If --update-labels is also specified then
+          --update-labels is applied first.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha netapp volumes update
+
+        $ gcloud beta netapp volumes update
+
diff --git a/gcloud/network-connectivity/internal-ranges/create b/gcloud/network-connectivity/internal-ranges/create
index 080fcebe5..644729db7 100644
--- a/gcloud/network-connectivity/internal-ranges/create
+++ b/gcloud/network-connectivity/internal-ranges/create
@@ -7,7 +7,7 @@ SYNOPSIS
         (INTERNAL_RANGE : --region=REGION) --network=NETWORK
         (--ip-cidr-range=IP_CIDR_RANGE | [--prefix-length=PREFIX_LENGTH
           : --target-cidr-range=[TARGET_CIDR_RANGE,...]]) [--async]
-        [--description=DESCRIPTION] [--labels=KEY=VALUE]
+        [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]]
         [--overlaps=[OVERLAPS,...]] [--peering=PEERING; default="for-self"]
         [--usage=USAGE; default="for-vpc"] [GCLOUD_WIDE_FLAG ...]
 
@@ -101,12 +101,16 @@ OPTIONAL FLAGS
      --description=DESCRIPTION
         Description of the internal range to be created.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
      --overlaps=[OVERLAPS,...]
         Overlap specifications for the range being created. OVERLAPS must be
-        (only one value is supported):
+        one of:
+
+         overlap-existing-subnet-range
+            Allows for creation of internal ranges that overlap with existing
+            subnets.
 
          overlap-route-range
             Allows for creation or existence of routes that have a more
diff --git a/gcloud/network-connectivity/internal-ranges/update b/gcloud/network-connectivity/internal-ranges/update
index 63989ec28..761ed5887 100644
--- a/gcloud/network-connectivity/internal-ranges/update
+++ b/gcloud/network-connectivity/internal-ranges/update
@@ -68,7 +68,11 @@ FLAGS
 
        --overlaps=[OVERLAPS,...]
           Overlap specifications for the range being updated. OVERLAPS must be
-          (only one value is supported):
+          one of:
+
+           overlap-existing-subnet-range
+              Allows for creation of internal ranges that overlap with existing
+              subnets.
 
            overlap-route-range
               Allows for creation or existence of routes that have a more
diff --git a/gcloud/network-connectivity/service-connection-policies/create b/gcloud/network-connectivity/service-connection-policies/create
index 22ec439eb..f4c46beae 100644
--- a/gcloud/network-connectivity/service-connection-policies/create
+++ b/gcloud/network-connectivity/service-connection-policies/create
@@ -7,7 +7,7 @@ SYNOPSIS
         SERVICE_CONNECTION_POLICY --network=NETWORK
         --service-class=SERVICE_CLASS
         (--subnets=[SUBNETS,...] : --psc-connection-limit=PSC_CONNECTION_LIMIT)
-        [--async] [--description=DESCRIPTION] [--labels=KEY=VALUE]
+        [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]]
         [--region=REGION] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -110,7 +110,7 @@ OPTIONAL FLAGS
      --description=DESCRIPTION
         Description of the Service Connection Policy to be created.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
      --region=REGION
diff --git a/gcloud/network-connectivity/spokes/linked-router-appliances/create b/gcloud/network-connectivity/spokes/linked-router-appliances/create
index 54696a0da..0d7c48ee3 100644
--- a/gcloud/network-connectivity/spokes/linked-router-appliances/create
+++ b/gcloud/network-connectivity/spokes/linked-router-appliances/create
@@ -4,8 +4,9 @@ NAME
 
 SYNOPSIS
     gcloud network-connectivity spokes linked-router-appliances create
-        (SPOKE : --region=REGION) --hub=HUB --router-appliance=ROUTER_APPLIANCE
-        [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]]
+        (SPOKE : --region=REGION) --hub=HUB
+        --router-appliance=[instance=INSTANCE],[ip=IP] [--async]
+        [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]]
         [--site-to-site-data-transfer] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -62,7 +63,7 @@ REQUIRED FLAGS
      --hub=HUB
         Hub that the spoke will attach to. The hub must already exist.
 
-     --router-appliance=ROUTER_APPLIANCE
+     --router-appliance=[instance=INSTANCE],[ip=IP]
         Router appliance instance(s) that the spoke provides connectivity to.
         The resources must already exist.
 
diff --git a/gcloud/network-connectivity/spokes/linked-router-appliances/update b/gcloud/network-connectivity/spokes/linked-router-appliances/update
index d4489377c..c6733a1c9 100644
--- a/gcloud/network-connectivity/spokes/linked-router-appliances/update
+++ b/gcloud/network-connectivity/spokes/linked-router-appliances/update
@@ -5,7 +5,8 @@ NAME
 SYNOPSIS
     gcloud network-connectivity spokes linked-router-appliances update
         (SPOKE : --region=REGION) [--async] [--description=DESCRIPTION]
-        [--router-appliance=ROUTER_APPLIANCE] [--update-labels=[KEY=VALUE,...]]
+        [--router-appliance=[instance=INSTANCE],[ip=IP]]
+        [--update-labels=[KEY=VALUE,...]]
         [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -69,7 +70,7 @@ FLAGS
      --description=DESCRIPTION
         New description of the spoke.
 
-     --router-appliance=ROUTER_APPLIANCE
+     --router-appliance=[instance=INSTANCE],[ip=IP]
         Router appliance instance(s) with which to replace the set of instances
         already linked to this spoke. Pass this flag multiple times to replace
         with multiple instances. For example, use
diff --git a/gcloud/network-management/connectivity-tests/create b/gcloud/network-management/connectivity-tests/create
index 7688b50d8..4585a2a53 100644
--- a/gcloud/network-management/connectivity-tests/create
+++ b/gcloud/network-management/connectivity-tests/create
@@ -18,7 +18,7 @@ SYNOPSIS
           --source-ip-address=SOURCE_IP_ADDRESS) [--async]
         [--description=DESCRIPTION] [--destination-network=DESTINATION_NETWORK]
         [--destination-port=DESTINATION_PORT]
-        [--destination-project=DESTINATION_PROJECT] [--labels=KEY=VALUE]
+        [--destination-project=DESTINATION_PROJECT] [--labels=[KEY=VALUE,...]]
         [--other-projects=[OTHER_PROJECTS,...]] [--protocol=PROTOCOL]
         [--source-network=SOURCE_NETWORK]
         [--source-network-type=SOURCE_NETWORK_TYPE; default="gcp-network"]
@@ -120,7 +120,7 @@ OPTIONAL FLAGS
      --destination-project=DESTINATION_PROJECT
         Project ID of the destination endpoint.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
      --other-projects=[OTHER_PROJECTS,...]
diff --git a/gcloud/network-management/connectivity-tests/update b/gcloud/network-management/connectivity-tests/update
index e6d8d7b05..96bf9ca19 100644
--- a/gcloud/network-management/connectivity-tests/update
+++ b/gcloud/network-management/connectivity-tests/update
@@ -7,7 +7,7 @@ SYNOPSIS
         [--async] [--description=DESCRIPTION]
         [--destination-network=DESTINATION_NETWORK]
         [--destination-port=DESTINATION_PORT]
-        [--destination-project=DESTINATION_PROJECT] [--labels=KEY=VALUE]
+        [--destination-project=DESTINATION_PROJECT] [--labels=[KEY=VALUE,...]]
         [--other-projects=[OTHER_PROJECTS,...]] [--protocol=PROTOCOL]
         [--source-network=SOURCE_NETWORK]
         [--source-network-type=SOURCE_NETWORK_TYPE; default="gcp-network"]
@@ -85,7 +85,7 @@ FLAGS
      --destination-project=DESTINATION_PROJECT
         Project ID of the destination endpoint.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
      --other-projects=[OTHER_PROJECTS,...]
diff --git a/gcloud/network-security/address-groups/create b/gcloud/network-security/address-groups/create
index 2d213a6e2..d06ee6580 100644
--- a/gcloud/network-security/address-groups/create
+++ b/gcloud/network-security/address-groups/create
@@ -5,7 +5,7 @@ SYNOPSIS
     gcloud network-security address-groups create
         (ADDRESS_GROUP : --location=LOCATION) --capacity=CAPACITY --type=TYPE
         [--async] [--description=DESCRIPTION] [--items=[ITEMS,...]]
-        [--labels=KEY=VALUE] [GCLOUD_WIDE_FLAG ...]
+        [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     Create a new address group with the given name.
@@ -67,7 +67,7 @@ OPTIONAL FLAGS
      --items=[ITEMS,...]
         Items of the address group.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
 GCLOUD WIDE FLAGS
diff --git a/gcloud/network-security/org-address-groups/create b/gcloud/network-security/org-address-groups/create
index c54dbdf55..0ec604c75 100644
--- a/gcloud/network-security/org-address-groups/create
+++ b/gcloud/network-security/org-address-groups/create
@@ -5,7 +5,7 @@ SYNOPSIS
     gcloud network-security org-address-groups create
         (ADDRESS_GROUP : --location=LOCATION --organization=ORGANIZATION)
         --capacity=CAPACITY --type=TYPE [--async] [--description=DESCRIPTION]
-        [--items=[ITEMS,...]] [--labels=KEY=VALUE] [GCLOUD_WIDE_FLAG ...]
+        [--items=[ITEMS,...]] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     Create a new address group with the given name.
@@ -69,7 +69,7 @@ OPTIONAL FLAGS
      --items=[ITEMS,...]
         Items of the address group.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
 GCLOUD WIDE FLAGS
diff --git a/gcloud/recaptcha/keys/update b/gcloud/recaptcha/keys/update
index 2449725b3..716d96fc8 100644
--- a/gcloud/recaptcha/keys/update
+++ b/gcloud/recaptcha/keys/update
@@ -3,7 +3,7 @@ NAME
 
 SYNOPSIS
     gcloud recaptcha keys update KEY [--display-name=DISPLAY_NAME]
-        [--labels=KEY=VALUE]
+        [--labels=[KEY=VALUE,...]]
         [--android (--allow-all-package-names
           | --package-names=[PACKAGE_NAMES,...])
           | [--ios : --allow-all-bundle-ids | --bundle-ids=[BUNDLE_IDS,...]
@@ -45,7 +45,7 @@ FLAGS
      --display-name=DISPLAY_NAME
         A human-readable name for the key. Typically a site or app name.
 
-     --labels=KEY=VALUE
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
      At most one of these can be specified:
diff --git a/gcloud/recommender/recommendations/list b/gcloud/recommender/recommendations/list
index e7f6fa56b..5b780e56e 100644
--- a/gcloud/recommender/recommendations/list
+++ b/gcloud/recommender/recommendations/list
@@ -27,10 +27,8 @@ REQUIRED FLAGS
         Location
 
      --recommender=RECOMMENDER
-        Recommender to list recommendations for. If no recommender is
-        specified, recommendations for all supported recommenders is listed.
-        Supported recommenders can be found here:
-        https://cloud.google.com/recommender/docs/recommenders
+        Recommender to list recommendations for. Supported recommenders can be
+        found here: https://cloud.google.com/recommender/docs/recommenders.
 
      Resource that is associated with cloud entity type. Currently four
      mutually exclusive flags are supported, --project, --billing-account,
diff --git a/gcloud/redis/instances/create b/gcloud/redis/instances/create
index 222bad269..f98e5851c 100644
--- a/gcloud/redis/instances/create
+++ b/gcloud/redis/instances/create
@@ -14,10 +14,10 @@ SYNOPSIS
         [--persistence-mode=PERSISTENCE_MODE]
         [--rdb-snapshot-period=RDB_SNAPSHOT_PERIOD]
         [--rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME]
-        [--read-replicas-mode=READ_REPLICAS_MODE] [--redis-config=KEY=VALUE]
-        [--redis-version=VERSION] [--replica-count=REPLICA_COUNT]
-        [--reserved-ip-range=RESERVED_IP_RANGE] [--size=SIZE; default=1]
-        [--tier=TIER; default="basic"]
+        [--read-replicas-mode=READ_REPLICAS_MODE]
+        [--redis-config=[KEY=VALUE,...]] [--redis-version=VERSION]
+        [--replica-count=REPLICA_COUNT] [--reserved-ip-range=RESERVED_IP_RANGE]
+        [--size=SIZE; default=1] [--tier=TIER; default="basic"]
         [--transit-encryption-mode=TRANSIT_ENCRYPTION_MODE] [--zone=ZONE]
         [GCLOUD_WIDE_FLAG ...]
 
@@ -157,7 +157,7 @@ FLAGS
             provided and the instance can scale up and down the number of
             replicas.
 
-     --redis-config=KEY=VALUE
+     --redis-config=[KEY=VALUE,...]
         A list of Redis config KEY=VALUE pairs to set on the instance according
         to http://redis.io/topics/config. Currently, the only supported
         parameters are:
diff --git a/gcloud/scc/assets/update-marks b/gcloud/scc/assets/update-marks
index d956b8f6b..16f2461aa 100644
--- a/gcloud/scc/assets/update-marks
+++ b/gcloud/scc/assets/update-marks
@@ -4,7 +4,7 @@ NAME
 
 SYNOPSIS
     gcloud scc assets update-marks (ASSET : --organization=ORGANIZATION)
-        [--security-marks=[SECURITY_MARKS,...]] [--start-time=START_TIME]
+        [--security-marks=[KEY=VALUE,...]] [--start-time=START_TIME]
         [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -73,7 +73,7 @@ POSITIONAL ARGUMENTS
             line..
 
 FLAGS
-     --security-marks=[SECURITY_MARKS,...]
+     --security-marks=[KEY=VALUE,...]
         SecurityMarks resource to be passed as the request body. It's a
         key=value pair separated by comma (,). For example:
         --security-marks="key1=val1,key2=val2".
diff --git a/gcloud/scc/findings/create b/gcloud/scc/findings/create
index f76fe3524..cbd32070f 100644
--- a/gcloud/scc/findings/create
+++ b/gcloud/scc/findings/create
@@ -6,7 +6,7 @@ SYNOPSIS
         (FINDING : --organization=ORGANIZATION --source=SOURCE)
         --category=CATEGORY --event-time=EVENT_TIME
         --resource-name=RESOURCE_NAME [--external-uri=EXTERNAL_URI]
-        [--source-properties=[SOURCE_PROPERTIES,...]] [--state=STATE]
+        [--source-properties=[KEY=VALUE,...]] [--state=STATE]
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -106,7 +106,7 @@ OPTIONAL FLAGS
         finding can be found. This field is guaranteed to be either empty or a
         well formed URL.
 
-     --source-properties=[SOURCE_PROPERTIES,...]
+     --source-properties=[KEY=VALUE,...]
         Source specific properties. These properties are managed by the source
         that writes the finding. The key names in the source_properties map
         must be between 1 and 255 characters, and must start with a letter and
diff --git a/gcloud/scc/findings/update b/gcloud/scc/findings/update
index 442e09fe7..f30ab5706 100644
--- a/gcloud/scc/findings/update
+++ b/gcloud/scc/findings/update
@@ -5,7 +5,7 @@ SYNOPSIS
     gcloud scc findings update
         (FINDING : --organization=ORGANIZATION --source=SOURCE)
         [--event-time=EVENT_TIME] [--external-uri=EXTERNAL_URI]
-        [--source-properties=[SOURCE_PROPERTIES,...]] [--state=STATE]
+        [--source-properties=[KEY=VALUE,...]] [--state=STATE]
         [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -97,7 +97,7 @@ FLAGS
         finding can be found. This field is guaranteed to be either empty or a
         well formed URL.
 
-     --source-properties=[SOURCE_PROPERTIES,...]
+     --source-properties=[KEY=VALUE,...]
         Source specific properties. These properties are managed by the source
         that writes the finding. The key names in the source_properties map
         must be between 1 and 255 characters, and must start with a letter and
diff --git a/gcloud/scc/findings/update-marks b/gcloud/scc/findings/update-marks
index 64f8b6cdd..a4626d90a 100644
--- a/gcloud/scc/findings/update-marks
+++ b/gcloud/scc/findings/update-marks
@@ -5,7 +5,7 @@ NAME
 SYNOPSIS
     gcloud scc findings update-marks
         (FINDING : --organization=ORGANIZATION --source=SOURCE)
-        [--security-marks=[SECURITY_MARKS,...]] [--start-time=START_TIME]
+        [--security-marks=[KEY=VALUE,...]] [--start-time=START_TIME]
         [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -86,7 +86,7 @@ POSITIONAL ARGUMENTS
           ▸ provide the argument --source on the command line.
 
 FLAGS
-     --security-marks=[SECURITY_MARKS,...]
+     --security-marks=[KEY=VALUE,...]
         SecurityMarks resource to be passed as the request body. It's a
         key=value pair separated by comma (,). For example:
         --security-marks="key1=val1,key2=val2".
diff --git a/gcloud/scheduler/jobs/create/app-engine b/gcloud/scheduler/jobs/create/app-engine
index 7f91cdd07..970a53847 100644
--- a/gcloud/scheduler/jobs/create/app-engine
+++ b/gcloud/scheduler/jobs/create/app-engine
@@ -5,7 +5,7 @@ NAME
 SYNOPSIS
     gcloud scheduler jobs create app-engine (JOB : --location=LOCATION)
         --schedule=SCHEDULE [--attempt-deadline=ATTEMPT_DEADLINE]
-        [--description=DESCRIPTION] [--headers=HEADERS]
+        [--description=DESCRIPTION] [--headers=[KEY=VALUE,...]]
         [--http-method=HTTP_METHOD; default="post"]
         [--max-backoff=MAX_BACKOFF; default="1h"]
         [--max-doublings=MAX_DOUBLINGS; default=16]
@@ -91,7 +91,7 @@ OPTIONAL FLAGS
      --description=DESCRIPTION
         Human-readable description of the job.
 
-     --headers=HEADERS
+     --headers=[KEY=VALUE,...]
         KEY=VALUE pairs of HTTP headers to include in the request. Cannot be
         repeated. For example: --headers
         Accept-Language=en-us,Accept=text/plain
diff --git a/gcloud/scheduler/jobs/create/http b/gcloud/scheduler/jobs/create/http
index e7b79da36..8e984f835 100644
--- a/gcloud/scheduler/jobs/create/http
+++ b/gcloud/scheduler/jobs/create/http
@@ -5,7 +5,7 @@ NAME
 SYNOPSIS
     gcloud scheduler jobs create http (JOB : --location=LOCATION)
         --schedule=SCHEDULE --uri=URI [--attempt-deadline=ATTEMPT_DEADLINE]
-        [--description=DESCRIPTION] [--headers=HEADERS]
+        [--description=DESCRIPTION] [--headers=[KEY=VALUE,...]]
         [--http-method=HTTP_METHOD; default="post"]
         [--max-backoff=MAX_BACKOFF; default="1h"]
         [--max-doublings=MAX_DOUBLINGS; default=16]
@@ -101,7 +101,7 @@ OPTIONAL FLAGS
      --description=DESCRIPTION
         Human-readable description of the job.
 
-     --headers=HEADERS
+     --headers=[KEY=VALUE,...]
         KEY=VALUE pairs of HTTP headers to include in the request. Cannot be
         repeated. For example: --headers
         Accept-Language=en-us,Accept=text/plain
diff --git a/gcloud/scheduler/jobs/update/app-engine b/gcloud/scheduler/jobs/update/app-engine
index 978e166a1..cf80c2279 100644
--- a/gcloud/scheduler/jobs/update/app-engine
+++ b/gcloud/scheduler/jobs/update/app-engine
@@ -8,7 +8,7 @@ SYNOPSIS
         [--http-method=HTTP_METHOD; default="post"] [--schedule=SCHEDULE]
         [--version=VERSION]
         [--clear-headers | --remove-headers=[REMOVE_HEADERS,...]
-          --update-headers=[UPDATE_HEADERS,...]]
+          --update-headers=[KEY=VALUE,...]]
         [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="1h"]
         [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=16]
         [--clear-max-retry-attempts | --max-retry-attempts=MAX_RETRY_ATTEMPTS]
@@ -108,7 +108,7 @@ FLAGS
           KEY1,KEY2 list of HTTP headers to remove from the request.
           --remove-headers Accept-Language,Accept
 
-       --update-headers=[UPDATE_HEADERS,...]
+       --update-headers=[KEY=VALUE,...]
           KEY=VALUE pairs of HTTP headers to include in the request. Cannot be
           repeated. For example: --update-headers
           Accept-Language=en-us,Accept=text/plain
diff --git a/gcloud/scheduler/jobs/update/http b/gcloud/scheduler/jobs/update/http
index 3458fa8a6..ac5831b8a 100644
--- a/gcloud/scheduler/jobs/update/http
+++ b/gcloud/scheduler/jobs/update/http
@@ -13,7 +13,7 @@ SYNOPSIS
           | [--oidc-service-account-email=OIDC_SERVICE_ACCOUNT_EMAIL
           : --oidc-token-audience=OIDC_TOKEN_AUDIENCE]]
         [--clear-headers | --remove-headers=[REMOVE_HEADERS,...]
-          --update-headers=[UPDATE_HEADERS,...]]
+          --update-headers=[KEY=VALUE,...]]
         [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="1h"]
         [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=16]
         [--clear-max-retry-attempts | --max-retry-attempts=MAX_RETRY_ATTEMPTS]
@@ -162,7 +162,7 @@ FLAGS
           KEY1,KEY2 list of HTTP headers to remove from the request.
           --remove-headers Accept-Language,Accept
 
-       --update-headers=[UPDATE_HEADERS,...]
+       --update-headers=[KEY=VALUE,...]
           KEY=VALUE pairs of HTTP headers to include in the request. Cannot be
           repeated. For example: --update-headers
           Accept-Language=en-us,Accept=text/plain
diff --git a/gcloud/scheduler/jobs/update/pubsub b/gcloud/scheduler/jobs/update/pubsub
index f10a8e1f8..489018d8d 100644
--- a/gcloud/scheduler/jobs/update/pubsub
+++ b/gcloud/scheduler/jobs/update/pubsub
@@ -6,7 +6,7 @@ SYNOPSIS
     gcloud scheduler jobs update pubsub (JOB : --location=LOCATION)
         [--description=DESCRIPTION] [--schedule=SCHEDULE] [--topic=TOPIC]
         [--clear-attributes | --remove-attributes=[REMOVE_ATTRIBUTES,...]
-          --update-attributes=[UPDATE_ATTRIBUTES,...]]
+          --update-attributes=[KEY=VALUE,...]]
         [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="1h"]
         [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=16]
         [--clear-max-retry-attempts | --max-retry-attempts=MAX_RETRY_ATTEMPTS]
@@ -94,7 +94,7 @@ FLAGS
           Comma-separated list of attribute keys to remove with the form
           "KEY1,KEY2".
 
-       --update-attributes=[UPDATE_ATTRIBUTES,...]
+       --update-attributes=[KEY=VALUE,...]
           Comma-separated list of attributes. Each attribute has the form
           "NAME=VALUE". You can specify up to 100 attributes.
 
diff --git a/gcloud/workflows/execute b/gcloud/workflows/execute
index 79b3e08c3..9f9f400ff 100644
--- a/gcloud/workflows/execute
+++ b/gcloud/workflows/execute
@@ -4,7 +4,7 @@ NAME
 SYNOPSIS
     gcloud workflows execute (WORKFLOW : --location=LOCATION)
         [--call-log-level=CALL_LOG_LEVEL; default="none"] [--data=DATA]
-        [--labels=[LABELS,...]] [GCLOUD_WIDE_FLAG ...]
+        [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     Execute a workflow.
@@ -70,7 +70,7 @@ FLAGS
         JSON string with data that will be passed to the workflow as an
         argument.
 
-     --labels=[LABELS,...]
+     --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
         Keys must start with a lowercase character and contain only hyphens,
diff --git a/gcloud/workstations/clusters/create b/gcloud/workstations/clusters/create
index 374964017..91936a042 100644
--- a/gcloud/workstations/clusters/create
+++ b/gcloud/workstations/clusters/create
@@ -3,8 +3,8 @@ NAME
 
 SYNOPSIS
     gcloud workstations clusters create (CLUSTER : --region=REGION) [--async]
-        [--enable-private-endpoint] [--labels=[LABELS,...]] [--network=NETWORK]
-        [--subnetwork=SUBNETWORK] [GCLOUD_WIDE_FLAG ...]
+        [--enable-private-endpoint] [--labels=[KEY=VALUE,...]]
+        [--network=NETWORK] [--subnetwork=SUBNETWORK] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     Create a workstation cluster.
@@ -63,7 +63,7 @@ FLAGS
         workstations from public networks, but requires additional
         configuration. Learn more: https://cloud.google.com/workstations/docs.
 
-     --labels=[LABELS,...]
+     --labels=[KEY=VALUE,...]
         Labels that are applied to the cluster and propagated to the underlying
         Compute Engine resources.
 
diff --git a/gcloud/workstations/create b/gcloud/workstations/create
index 5e4182480..f2e1596af 100644
--- a/gcloud/workstations/create
+++ b/gcloud/workstations/create
@@ -4,7 +4,7 @@ NAME
 SYNOPSIS
     gcloud workstations create
         (WORKSTATION : --cluster=CLUSTER --config=CONFIG --region=REGION)
-        [--async] [--labels=[LABELS,...]] [GCLOUD_WIDE_FLAG ...]
+        [--async] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     Create a workstation.
@@ -67,7 +67,7 @@ FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
-     --labels=[LABELS,...]
+     --labels=[KEY=VALUE,...]
         Labels that are applied to the workstation and propagated to the
         underlying Compute Engine resources.