NAME
    gcloud beta container vmware clusters update - update an Anthos cluster on
        VMware

SYNOPSIS
    gcloud beta container vmware clusters update
        (CLUSTER : --location=LOCATION) [--admin-users=ADMIN_USERS] [--async]
        [--description=DESCRIPTION]
        [--metal-lb-config-address-pools=[addresses=ADDRESSES],
          [avoid-buggy-ips=AVOID-BUGGY-IPS],
          [manual-assign=MANUAL-ASSIGN],[pool=POOL]]
        [--static-ip-config-ip-blocks=[gateway=GATEWAY],
          [ips=IPS],[netmask=NETMASK]]
        [--upgrade-policy=[control-plane-only=CONTROL-PLANE-ONLY]]
        [--validate-only] [--version=VERSION]
        [--add-annotations=[KEY1=VALUE1,KEY2=VALUE2,...]
          | --remove-annotations=[KEY1,KEY2,...]]
        [--cpus=CPUS --memory=MEMORY --disable-auto-resize
          | --enable-auto-resize] [--disable-aag-config | --enable-aag-config]
        [--disable-auto-repair | --enable-auto-repair]
        [--disable-vsphere-csi | --enable-vsphere-csi] [GCLOUD_WIDE_FLAG ...]

DESCRIPTION
    (BETA) Update an Anthos cluster on VMware.

EXAMPLES
    To update a cluster named my-cluster managed in location us-west1, run:

        $ gcloud beta container vmware clusters update my-cluster \
            --location=us-west1

POSITIONAL ARGUMENTS
     Cluster resource - cluster 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 cluster 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.

       CLUSTER
          ID of the cluster or fully qualified identifier for the cluster.

          To set the cluster attribute:
          ▸ provide the argument cluster on the command line.

          This positional argument must be specified if any of the other
          arguments in this group are specified.

       --location=LOCATION
          Google Cloud location for the cluster.

          To set the location attribute:
          ▸ provide the argument cluster on the command line with a fully
            specified name;
          ▸ provide the argument --location on the command line;
          ▸ set the property container_vmware/location.

FLAGS
     User cluster authorization configurations to bootstrap onto the admin
     cluster

     --admin-users=ADMIN_USERS
        Users that will be granted the cluster-admin role on the cluster,
        providing full access to the cluster.

        To add multiple users, specify one in each flag. When updating, the
        update command overwrites the whole grant list. Specify all existing
        and new users that you want to be cluster administrators.

        Examples:

            $ gcloud beta container vmware clusters update
                --admin-users alice@example.com
                --admin-users bob@example.com

     --async
        Return immediately, without waiting for the operation in progress to
        complete.

     --description=DESCRIPTION
        Description for the resource.

     Anthos on VMware cluster load balancer configurations

     Populate one of the load balancers.

     MetalLB Configuration

     At most one of these can be specified:

       --metal-lb-config-address-pools=[addresses=ADDRESSES],[avoid-buggy-ips=AVOID-BUGGY-IPS],[manual-assign=MANUAL-ASSIGN],[pool=POOL]
          MetalLB load balancer configurations.

          Examples:

          To specify MetalLB load balancer configurations for two address pools
          pool1 and pool2,

              $ gcloud gcloud beta container vmware clusters update
                  --metal-lb-config-address-pools 'pool=pool1,avoid-buggy-ips=True,manual-assign=True,addresses=192.168.1.1/32;192.168.1.2-192.168.1.3'
                  --metal-lb-config-address-pools 'pool=pool2,avoid-buggy-ips=False,manual-assign=False,addresses=192.168.2.1/32;192.168.2.2-192.168.2.3'

          Use quote around the flag value to escape semicolon in the terminal.

     VMware User Cluster network configurations

     IP configuration used by the VMware User Cluster

     Static IP configuration group

     At most one of these can be specified:

       --static-ip-config-ip-blocks=[gateway=GATEWAY],[ips=IPS],[netmask=NETMASK]
          Static IP configurations.

          Expect an individual IP address, an individual IP address with an
          optional hostname, or a CIDR block.

          Example:

          To specify two Static IP blocks,

              $ gcloud gcloud beta container vmware clusters update
                  --static-ip-config-ip-blocks 'gateway=192.168.0.1,netmask=255.255.255.0,ips=192.168.1.1;0.0.0.0 localhost;192.168.1.2/16'
                  --static-ip-config-ip-blocks 'gateway=192.168.1.1,netmask=255.255.0.0,ips=8.8.8.8;4.4.4.4'

          Use quote around the flag value to escape semicolon in the terminal.

     Upgrade policy for the cluster.

     --upgrade-policy=[control-plane-only=CONTROL-PLANE-ONLY]
        If not specified, control-plane-only is set to False. In the next
        upgrade operation, all worker node pools will be upgraded together with
        the control plane.

        Example:

            To upgrade the control plane only and keep worker node pools version unchanged, first specify the policy:

            $ gcloud beta container vmware clusters update CLUSTER \
              --upgrade-policy control-plane-only=True

            Then to start the upgrade operation using the specified policy, run:

            $ gcloud beta container vmware clusters upgrade CLUSTER \
              --version=VERSION

            After upgrading only the cluster control plane, to upgrade an individual node pool, run:

            $ gcloud beta container vmware node-pools update NODE_POOL \
              --version=VERSION

        Example:

            Alternatively, to upgrade both the control plane and all worker node pools, first specify the policy:

            $ gcloud beta container vmware clusters update CLUSTER \
              --upgrade-policy control-plane-only=False

            Then to start the upgrade operation using the specified policy, run:

            $ gcloud beta container vmware clusters upgrade CLUSTER \
              --version=VERSION

     --validate-only
        If set, only validate the request, but do not actually perform the
        operation.

     --version=VERSION
        Anthos Cluster on VMware version for the cluster resource

     At most one of these can be specified:

       --add-annotations=[KEY1=VALUE1,KEY2=VALUE2,...]
          Add the given key-value pairs to the current annotations, or update
          its value if the key already exists.

       --remove-annotations=[KEY1,KEY2,...]
          Remove annotations of the given keys.

     Control plane node configurations

     --cpus=CPUS
        Number of CPUs for each admin cluster node that serve as control planes
        for this VMware user cluster. (default: 4 CPUs)

     --memory=MEMORY
        Megabytes of memory for each admin cluster node that serves as a
        control plane for this VMware User Cluster (default: 8192 MB memory).

     Auto resize configurations

     At most one of these can be specified:

       --disable-auto-resize
          Disable controle plane node auto resize.

       --enable-auto-resize
          Enable controle plane node auto resize.

     Anti-affinity group configurations

     At most one of these can be specified:

       --disable-aag-config
          If set, spread nodes across at least three physical hosts (requires
          at least three hosts). Enabled by default.

       --enable-aag-config
          If set, enable anti-affinity group config.

     Auto-repair configurations

     At most one of these can be specified:

       --disable-auto-repair
          If set, disables auto repair.

       --enable-auto-repair
          If set, deploy the cluster-health-controller.

     Storage configurations

     At most one of these can be specified:

       --disable-vsphere-csi
          If set, vSphere CSI components are not deployed in the VMware User
          Cluster. Enabled by default.

       --enable-vsphere-csi
          If set, vSphere CSI components are deployed in the VMware User
          Cluster.

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 vmware clusters update

        $ gcloud alpha container vmware clusters update

