gcloud: Wed Feb 8 10:13:59 UTC 2023

gcloud/compute/commitments/create

@@ -96,9 +96,10 @@ OPTIONAL FLAGS
      --type=TYPE; default="general-purpose"
         Type of commitment. memory-optimized indicates that the commitment is
         for memory-optimized VMs. TYPE must be one of: accelerator-optimized,
-        compute-optimized, compute-optimized-c2d, general-purpose,
-        general-purpose-e2, general-purpose-n2, general-purpose-n2d,
-        general-purpose-t2d, memory-optimized, memory-optimized-m3.
+        compute-optimized, compute-optimized-c2d, compute-optimized-c3,
+        general-purpose, general-purpose-e2, general-purpose-n2,
+        general-purpose-n2d, general-purpose-t2d, memory-optimized,
+        memory-optimized-m3.
 
      Manage the reservations to be created with the commitment.
 

gcloud/compute/help

@@ -90,6 +90,9 @@ GROUPS
      machine-types
         Read Compute Engine virtual machine types.
 
+     network-attachments
+        Manage Compute Engine network attachment resources.
+
      network-edge-security-services
         Read and manipulate network edge security services.
 

gcloud/compute/instance-groups/managed/set-autoscaling

@@ -235,8 +235,14 @@ OPTIONAL FLAGS
         autoscaler scales the group to have at least as many VMs as defined by
         the minimum required instances. After the configured duration, if there
         is no need to maintain capacity, the autoscaler starts removing
-        instances after a 10-minute stabilization period and (if configured)
-        following scale-in controls.
+        instances after the usual stabilization period and after scale-in
+        controls (if configured). For more information, see Delays in scaling
+        in
+        (https://cloud.google.com/compute/docs/autoscaler/understanding-autoscaler-decisions#delays_in_scaling_in)
+        and Scale-in controls
+        (https://cloud.google.com/compute/docs/autoscaler/understanding-autoscaler-decisions#scale-in_controls).
+        This ensures you don't accidentally lose capacity immediately after the
+        scaling schedule ends.
 
      --schedule-min-required-replicas=MIN_REQUIRED_REPLICAS
         How many VMs the autoscaler should provision for the duration of this

gcloud/compute/instance-groups/managed/set-instance-template

@@ -22,6 +22,15 @@ DESCRIPTION
       ▪ Use the rolling-action start-update command.
       ▪ Use the API to set the group's updatePolicy.type to PROACTIVE.
 
+EXAMPLES
+    Running:
+
+        gcloud compute instance-groups managed set-instance-template \
+        example-managed-instance-group --template=example-global-instance-template
+
+    Sets the group's instance template to a global instance template resource:
+    'example-global-instance-template'.
+
 POSITIONAL ARGUMENTS
      NAME
         Name of the managed instance group to operate on.

gcloud/compute/instance-groups/managed/update-autoscaling

@@ -130,10 +130,14 @@ FLAGS
           scaling schedule that is currently active the disabled scaling
           schedule stops being effective immediately after it moves into
           DISABLED state. If there is no need to maintain capacity, the
-          autoscaler starts removing instances after a 10-minute stabilization
-          period and (if configured) following scale-in controls. This ensures
-          you don't accidentally lose capacity immediately after the scaling
-          schedule ends.
+          autoscaler starts removing instances after the usual stabilization
+          period and after scale-in controls (if configured). For more
+          information, see Delays in scaling in
+          (https://cloud.google.com/compute/docs/autoscaler/understanding-autoscaler-decisions#delays_in_scaling_in)
+          and Scale-in controls
+          (https://cloud.google.com/compute/docs/autoscaler/understanding-autoscaler-decisions#scale-in_controls).
+          This ensures you don't accidentally lose capacity immediately after
+          the scaling schedule ends.
 
        --enable-schedule=SCHEDULE_NAME
           Name of the scaling schedule to be enabled.
@@ -150,9 +154,14 @@ FLAGS
           scaling schedule that is currently active, the deleted scaling
           schedule stops being effective immediately after it is deleted. If
           there is no need to maintain capacity, the autoscaler starts removing
-          instances after a 10-minute stabilization period and (if configured)
-          following scale-in controls. This ensures you don't accidentally lose
-          capacity immediately after the scaling schedule ends.
+          instances after the usual stabilization period and after scale-in
+          controls (if configured). For more information, see Delays in scaling
+          in
+          (https://cloud.google.com/compute/docs/autoscaler/understanding-autoscaler-decisions#delays_in_scaling_in)
+          and Scale-in controls
+          (https://cloud.google.com/compute/docs/autoscaler/understanding-autoscaler-decisions#scale-in_controls).
+          This ensures you don't accidentally lose capacity immediately after
+          the scaling schedule ends.
 
        --set-schedule=SCHEDULE_NAME
           A unique name for the scaling schedule to be configured.
@@ -205,8 +214,14 @@ FLAGS
         autoscaler scales the group to have at least as many VMs as defined by
         the minimum required instances. After the configured duration, if there
         is no need to maintain capacity, the autoscaler starts removing
-        instances after a 10-minute stabilization period and (if configured)
-        following scale-in controls.
+        instances after the usual stabilization period and after scale-in
+        controls (if configured). For more information, see Delays in scaling
+        in
+        (https://cloud.google.com/compute/docs/autoscaler/understanding-autoscaler-decisions#delays_in_scaling_in)
+        and Scale-in controls
+        (https://cloud.google.com/compute/docs/autoscaler/understanding-autoscaler-decisions#scale-in_controls).
+        This ensures you don't accidentally lose capacity immediately after the
+        scaling schedule ends.
 
      --schedule-min-required-replicas=MIN_REQUIRED_REPLICAS
         How many VMs the autoscaler should provision for the duration of this

gcloud/compute/instance-templates/create

@@ -556,10 +556,6 @@ FLAGS
                 The IP allocator will pick an available range with the specified
                 netmask and allocate it to this network interface.
 
-         network-attachment
-            Specifies the network attachment that this interface should connect
-            to. Mutually exclusive with --network and --subnet flags.
-
      --network-performance-configs=[PROPERTY=VALUE,...]
         Configures network performance settings for the instance. If this flag
         is not specified, the instance will be created with its default network

gcloud/compute/instance-templates/create-with-container

@@ -515,10 +515,6 @@ FLAGS
                 The IP allocator will pick an available range with the specified
                 netmask and allocate it to this network interface.
 
-         network-attachment
-            Specifies the network attachment that this interface should connect
-            to. Mutually exclusive with --network and --subnet flags.
-
      --network-tier=NETWORK_TIER
         Specifies the network tier that will be used to configure the instance.
         NETWORK_TIER must be one of: PREMIUM, STANDARD, FIXED_STANDARD. The

gcloud/compute/instances/create

@@ -634,10 +634,6 @@ FLAGS
                 IP allocator will pick an available range with the specified netmask
                 and allocate it to this network interface.
 
-         network-attachment
-            Specifies the network attachment that this interface should connect
-            to. Mutually exclusive with --network and --subnet flags.
-
      --network-performance-configs=[PROPERTY=VALUE,...]
         Configures network performance settings for the instance. If this flag
         is not specified, the instance will be created with its default network

gcloud/compute/instances/create-with-container

@@ -565,10 +565,6 @@ FLAGS
                 IP allocator will pick an available range with the specified netmask
                 and allocate it to this network interface.
 
-         network-attachment
-            Specifies the network attachment that this interface should connect
-            to. Mutually exclusive with --network and --subnet flags.
-
      --network-performance-configs=[PROPERTY=VALUE,...]
         Configures network performance settings for the instance. If this flag
         is not specified, the instance will be created with its default network

gcloud/compute/network-attachments/create

@@ -0,0 +1,101 @@
+NAME
+    gcloud compute network-attachments create - create a Google Compute Engine
+        network attachment
+
+SYNOPSIS
+    gcloud compute network-attachments create NAME
+        --subnets=SUBNETS,[SUBNETS,...]
+        [--connection-preference=CONNECTION_PREFERENCE;
+          default="ACCEPT_AUTOMATIC"] [--description=DESCRIPTION]
+        [--producer-accept-list=[ACCEPT_LIST,...]]
+        [--producer-reject-list=[REJECT_LIST,...]] [--region=REGION]
+        [--subnets-region=SUBNETS_REGION] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    gcloud compute network-attachments create is used to create network
+    attachments. A service consumer creates network attachments and makes it
+    available to producers. Service producers then use a multi-NIC VM to form a
+    bi-directional, non-NAT'd communication channel.
+
+EXAMPLES
+        $ gcloud compute network-attachments create \
+            NETWORK_ATTACHMENT_NAME --region=us-central1 \
+            --subnets=MY_SUBNET --connection-preference=ACCEPT_MANUAL \
+            --producer-accept-list=PROJECT1,PROJECT2 \
+            --producer-reject-list=PROJECT3,PROJECT4
+
+    To create a network attachment with a textual description, run:
+
+        $ gcloud compute network-attachments create \
+            NETWORK_ATTACHMENT_NAME --region=us-central1 \
+            --subnets=MY_SUBNET --connection-preference=ACCEPT_MANUAL \
+            --producer-accept-list=PROJECT1,PROJECT2 \
+            --producer-reject-list=PROJECT3,PROJECT4 \
+            --description='default network attachment'
+
+POSITIONAL ARGUMENTS
+     NAME
+        Name of the network attachment to create.
+
+REQUIRED FLAGS
+     --subnets=SUBNETS,[SUBNETS,...]
+        The subnetworks provided by the consumer for the producers
+
+OPTIONAL FLAGS
+     --connection-preference=CONNECTION_PREFERENCE; default="ACCEPT_AUTOMATIC"
+        The connection preference of network attachment. The value can be set
+        to ACCEPT_AUTOMATIC or ACCEPT_MANUAL. An ACCEPT_AUTOMATIC network
+        attachment is one that always accepts the connection from producer NIC.
+        An ACCEPT_MANUAL network attachment is one that requires an explicit
+        addition of the producer project id or project number to the producer
+        accept list. CONNECTION_PREFERENCE must be one of: ACCEPT_AUTOMATIC,
+        ACCEPT_MANUAL.
+
+     --description=DESCRIPTION
+        An optional, textual description for the network attachment.
+
+     --producer-accept-list=[ACCEPT_LIST,...]
+        Projects that are allowed to connect to this network attachment.
+
+     --producer-reject-list=[REJECT_LIST,...]
+        Projects that are not allowed to connect to this network attachment.
+
+     --region=REGION
+        Region of the network attachment to create. 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.
+
+     --subnets-region=SUBNETS_REGION
+        Region of the subnetworks to operate on. Overrides the default
+        compute/region property value for this command invocation.
+
+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 network-attachments create
+
+        $ gcloud beta compute network-attachments create
+

gcloud/compute/network-attachments/delete

@@ -0,0 +1,57 @@
+NAME
+    gcloud compute network-attachments delete - delete one or more Google
+        Compute Engine network attachments
+
+SYNOPSIS
+    gcloud compute network-attachments delete NAME [NAME ...] [--region=REGION]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Delete one or more Google Compute Engine network attachments.
+
+EXAMPLES
+    To delete a network attachment, run:
+
+        $ gcloud compute network-attachments delete \
+          NETWORK_ATTACHMENT_NAME --region=us-central1
+
+POSITIONAL ARGUMENTS
+     NAME [NAME ...]
+        Names of the network attachments to delete.
+
+FLAGS
+     --region=REGION
+        Region of the network attachments to delete. 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 network-attachments delete
+
+        $ gcloud beta compute network-attachments delete
+

gcloud/compute/network-attachments/describe

@@ -0,0 +1,57 @@
+NAME
+    gcloud compute network-attachments describe - describes a Google Compute
+        Engine network attachment
+
+SYNOPSIS
+    gcloud compute network-attachments describe NAME [--region=REGION]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Describes a Google Compute Engine network attachment.
+
+EXAMPLES
+    To describe a network attachment, run:
+
+        $ gcloud compute network-attachments describe \
+          NETWORK_ATTACHMENT_NAME --region=us-central1
+
+POSITIONAL ARGUMENTS
+     NAME
+        Name of the network attachment to describe.
+
+FLAGS
+     --region=REGION
+        Region of the network attachment to describe. 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 network-attachments describe
+
+        $ gcloud beta compute network-attachments describe
+

gcloud/compute/network-attachments/help

@@ -0,0 +1,37 @@
+NAME
+    gcloud compute network-attachments - manage Compute Engine network
+        attachment resources
+
+SYNOPSIS
+    gcloud compute network-attachments COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    List, create, describe, update and delete network attachments.
+
+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 Google Compute Engine network attachment.
+
+     delete
+        Delete one or more Google Compute Engine network attachments.
+
+     describe
+        Describes a Google Compute Engine network attachment.
+
+     list
+        List Google Compute Engine network attachments.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha compute network-attachments
+
+        $ gcloud beta compute network-attachments
+

gcloud/compute/network-attachments/list

@@ -0,0 +1,88 @@
+NAME
+    gcloud compute network-attachments list - list Google Compute Engine
+        network attachments
+
+SYNOPSIS
+    gcloud compute network-attachments list [NAME ...]
+        [--regexp=REGEXP, -r REGEXP] [--regions=REGION,[REGION,...]]
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    List Google Compute Engine network attachments.
+
+EXAMPLES
+    To list all the network attachments, run:
+
+        $ gcloud compute network-attachments list
+
+    To list the network attachments in given region(s), run:
+
+        $ gcloud compute network-attachments list --regions=region-1,region-2
+
+POSITIONAL ARGUMENTS
+     [NAME ...]
+        (DEPRECATED) If provided, show details for the specified names and/or
+        URIs of resources.
+
+        Argument NAME is deprecated. Use --filter="name=( 'NAME' ... )"
+        instead.
+
+FLAGS
+     --regexp=REGEXP, -r REGEXP
+        (DEPRECATED) Regular expression to filter the names of the results on.
+        Any names that do not match the entire regular expression will be
+        filtered out.
+
+        Flag --regexp is deprecated. Use --filter="name~'REGEXP'" instead.
+
+     --regions=REGION,[REGION,...]
+        If provided, only resources from the given regions are queried.
+
+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 compute network-attachments list
+
+        $ gcloud beta compute network-attachments list
+