gcloud: Wed Mar 8 10:34:05 UTC 2023

2026-07-18 14:56:05 +00:00 · 2023-03-08 10:34:05 +00:00 · 2023-03-08 10:34:05 +00:00 · 29661f002c
commit 29661f002c
parent bdaa0b3cfc
111 changed files with 1800 additions and 704 deletions
--- a/gcloud/beta/compute/instances/ops-agents/policies/create
+++ b/gcloud/beta/compute/instances/ops-agents/policies/create
@ -229,8 +229,10 @@ REQUIRED FLAGS
            debian             11
            debian             10
            debian             9
+            rhel               9.*
            rhel               8.*
            rhel               7.*
+            rocky              9.*
            rocky              8.*
            sles               12.*
            sles               15.*
@ -249,8 +251,8 @@ REQUIRED FLAGS
         short-name
            Short name of the OS.

-            Required. Allowed values: centos, debian, rhel, sles, sles_sap,
-            ubuntu.
+            Required. Allowed values: centos, debian, rhel, rocky, sles,
+            sles_sap, ubuntu.

            To inspect the exact OS short name of an instance, run:

--- a/gcloud/beta/compute/instances/ops-agents/policies/update
+++ b/gcloud/beta/compute/instances/ops-agents/policies/update
@ -266,8 +266,10 @@ FLAGS
            debian             11
            debian             10
            debian             9
+            rhel               9.*
            rhel               8.*
            rhel               7.*
+            rocky              9.*
            rocky              8.*
            sles               12.*
            sles               15.*
@ -286,8 +288,8 @@ FLAGS
         short-name
            Short name of the OS.

-            Required. Allowed values: centos, debian, rhel, sles, sles_sap,
-            ubuntu.
+            Required. Allowed values: centos, debian, rhel, rocky, sles,
+            sles_sap, ubuntu.

            To inspect the exact OS short name of an instance, run:

--- a/gcloud/beta/compute/instances/set-scheduling
+++ b/gcloud/beta/compute/instances/set-scheduling
@ -11,8 +11,10 @@ SYNOPSIS
        [--[no-]restart-on-failure] [--zone=ZONE]
        [--clear-instance-termination-action
          | --instance-termination-action=INSTANCE_TERMINATION_ACTION]
+        [--clear-max-run-duration | --max-run-duration=MAX_RUN_DURATION]
        [--clear-node-affinities | --node=NODE
          | --node-affinity-file=NODE_AFFINITY_FILE | --node-group=NODE_GROUP]
+        [--clear-termination-time | --termination-time=TERMINATION_TIME]
        [GCLOUD_WIDE_FLAG ...]

 DESCRIPTION
@ -135,6 +137,33 @@ FLAGS
              Default. Stop the VM without preserving memory. The VM can be
              restarted later.

+     Max Run Duration
+
+     At most one of these can be specified:
+
+       --clear-max-run-duration
+          Removes the max-run-duration field from the scheduling options.
+
+       --max-run-duration=MAX_RUN_DURATION
+          Limits how long this VM instance can run, specified as a duration
+          relative to the VM instance's most-recent start time. Format the
+          duration, MAX_RUN_DURATION, as the number of days, hours, minutes,
+          and seconds followed by d, h, m, and s respectively. For example,
+          specify 30m for a duration of 30 minutes or specify 1d2h3m4s for a
+          duration of 1 day, 2 hours, 3 minutes, and 4 seconds. Alternatively,
+          to specify a timestamp, use --termination-time instead.
+
+          If neither --max-run-duration nor --termination-time is specified
+          (default), the VM instance runs until prompted by a user action or
+          system event. If either is specified, the VM instance is scheduled to
+          be automatically terminated using the action specified by
+          --instance-termination-action. For --max-run-duration, the VM
+          instance is automatically terminated when the VM's current runtime
+          reaches MAX_RUN_DURATION. Note: Anytime the VM instance is stopped or
+          suspended, --max-run-duration and (unless the VM uses
+          --provisioning-model=SPOT) --instance-termination-action are
+          automatically removed from the VM.
+
     Sole Tenancy.

     At most one of these can be specified:
@ -171,6 +200,29 @@ FLAGS
       --node-group=NODE_GROUP
          The name of the node group to schedule this instance on.

+     Termination Time
+
+     At most one of these can be specified:
+
+       --clear-termination-time
+          Removes the termination-time field from the scheduling options.
+
+       --termination-time=TERMINATION_TIME
+          Limits how long this VM instance can run, specified as a time. Format
+          the time, TERMINATION_TIME, as a RFC 3339 timestamp. For more
+          information, see https://tools.ietf.org/html/rfc3339. Alternatively,
+          to specify a duration, use --max-run-duration instead.
+
+          If neither --termination-time nor --max-run-duration is specified
+          (default), the VM instance runs until prompted by a user action or
+          system event. If either is specified, the VM instance is scheduled to
+          be automatically terminated using the action specified by
+          --instance-termination-action. For --termination-time, the VM
+          instance is automatically terminated at the specified timestamp.
+          Note: Anytime the VM instance is stopped or suspended,
+          --termination-time and (unless the VM uses --provisioning-model=SPOT)
+          --instance-termination-action are automatically removed from the VM.
+
 GCLOUD WIDE FLAGS
    These flags are available to all commands: --access-token-file, --account,
    --billing-project, --configuration, --flags-file, --flatten, --format,
--- a/gcloud/beta/compute/interconnects/attachments/dedicated/create
+++ b/gcloud/beta/compute/interconnects/attachments/dedicated/create
@ -9,9 +9,9 @@ SYNOPSIS
        [--candidate-subnets=[SUBNET,...]]
        [--cloud-router-ipv6-interface-id=INTERFACE_ID]
        [--customer-router-ipv6-interface-id=PEER_INTERFACE_ID]
-        [--description=DESCRIPTION] [--enable-admin] [--mtu=MTU]
-        [--region=REGION] [--stack-type=STACK_TYPE] [--vlan=VLAN]
-        [GCLOUD_WIDE_FLAG ...]
+        [--description=DESCRIPTION] [--enable-admin] [--encryption=ENCRYPTION]
+        [--ipsec-internal-addresses=[ADDRESSES]] [--mtu=MTU] [--region=REGION]
+        [--stack-type=STACK_TYPE] [--vlan=VLAN] [GCLOUD_WIDE_FLAG ...]

 DESCRIPTION
    (BETA) gcloud beta compute interconnects attachments dedicated create is
@ -100,6 +100,38 @@ OPTIONAL FLAGS
        is operational and will carry traffic. Use --no-enable-admin to disable
        it.

+     --encryption=ENCRYPTION
+        Indicates the user-supplied encryption option for this interconnect
+        attachment (VLAN attachment).
+
+        Possible values are:
+
+        NONE - This is the default value, which means the interconnect
+        attachment carries unencrypted traffic. VMs can send traffic to or
+        receive traffic from such interconnect attachment.
+
+        IPSEC - The interconnect attachment carries only traffic that is
+        encrypted by an IPsec device; for example, an HA VPN gateway or
+        third-party IPsec VPN. VMs cannot directly send traffic to or receive
+        traffic from such an interconnect attachment. To use HA VPN over Cloud
+        Interconnect, the interconnect attachment must be created with this
+        option.
+
+        ENCRYPTION must be one of: IPSEC, NONE.
+
+     --ipsec-internal-addresses=[ADDRESSES]
+        List of IP address range names that have been reserved for the
+        interconnect attachment (VLAN attachment). Use this option only for an
+        interconnect attachment that has its encryption option set as IPSEC.
+        Currently only one internal IP address range can be specified for each
+        attachment. When creating an HA VPN gateway for the interconnect
+        attachment, if the attachment is configured to use a regional internal
+        IP address, then the VPN gateway's IP address is allocated from the IP
+        address range specified here. If this field is not specified when
+        creating the interconnect attachment, then when creating any HA VPN
+        gateways for this interconnect attachment, the HA VPN gateway's IP
+        address is allocated from a regional external IP address pool.
+
     --mtu=MTU
        Maximum transmission unit (MTU) is the size of the largest IP packet
        passing through this interconnect attachment. Only 1440 and 1500 are
--- a/gcloud/beta/compute/interconnects/attachments/partner/create
+++ b/gcloud/beta/compute/interconnects/attachments/partner/create
@ -5,8 +5,9 @@ NAME
 SYNOPSIS
    gcloud beta compute interconnects attachments partner create NAME
        --edge-availability-domain=AVAILABILITY_DOMAIN --router=ROUTER
-        [--description=DESCRIPTION] [--enable-admin] [--mtu=MTU]
-        [--region=REGION] [GCLOUD_WIDE_FLAG ...]
+        [--description=DESCRIPTION] [--enable-admin] [--encryption=ENCRYPTION]
+        [--ipsec-internal-addresses=[ADDRESSES]] [--mtu=MTU] [--region=REGION]
+        [GCLOUD_WIDE_FLAG ...]

 DESCRIPTION
    (BETA) gcloud beta compute interconnects attachments partner create is used
@ -53,6 +54,38 @@ OPTIONAL FLAGS
        is operational and will carry traffic. Use --no-enable-admin to disable
        it.

+     --encryption=ENCRYPTION
+        Indicates the user-supplied encryption option for this interconnect
+        attachment (VLAN attachment).
+
+        Possible values are:
+
+        NONE - This is the default value, which means the interconnect
+        attachment carries unencrypted traffic. VMs can send traffic to or
+        receive traffic from such interconnect attachment.
+
+        IPSEC - The interconnect attachment carries only traffic that is
+        encrypted by an IPsec device; for example, an HA VPN gateway or
+        third-party IPsec VPN. VMs cannot directly send traffic to or receive
+        traffic from such an interconnect attachment. To use HA VPN over Cloud
+        Interconnect, the interconnect attachment must be created with this
+        option.
+
+        ENCRYPTION must be one of: IPSEC, NONE.
+
+     --ipsec-internal-addresses=[ADDRESSES]
+        List of IP address range names that have been reserved for the
+        interconnect attachment (VLAN attachment). Use this option only for an
+        interconnect attachment that has its encryption option set as IPSEC.
+        Currently only one internal IP address range can be specified for each
+        attachment. When creating an HA VPN gateway for the interconnect
+        attachment, if the attachment is configured to use a regional internal
+        IP address, then the VPN gateway's IP address is allocated from the IP
+        address range specified here. If this field is not specified when
+        creating the interconnect attachment, then when creating any HA VPN
+        gateways for this interconnect attachment, the HA VPN gateway's IP
+        address is allocated from a regional external IP address pool.
+
     --mtu=MTU
        Maximum transmission unit (MTU) is the size of the largest IP packet
        passing through this interconnect attachment. Only 1440 and 1500 are
--- a/gcloud/beta/compute/routers/create
+++ b/gcloud/beta/compute/routers/create
@ -4,8 +4,9 @@ NAME
 SYNOPSIS
    gcloud beta compute routers create NAME --network=NETWORK
        [--advertisement-mode=MODE] [--asn=ASN] [--async]
-        [--description=DESCRIPTION] [--keepalive-interval=KEEPALIVE_INTERVAL]
-        [--region=REGION] [--set-advertisement-groups=[GROUP,...]]
+        [--description=DESCRIPTION] [--encrypted-interconnect-router]
+        [--keepalive-interval=KEEPALIVE_INTERVAL] [--region=REGION]
+        [--set-advertisement-groups=[GROUP,...]]
        [--set-advertisement-ranges=[CIDR_RANGE=DESC,...]]
        [GCLOUD_WIDE_FLAG ...]

@ -42,6 +43,10 @@ OPTIONAL FLAGS
     --description=DESCRIPTION
        An optional description of this router.

+     --encrypted-interconnect-router
+        Indicates if a router is dedicated for use with encrypted interconnect
+        attachments (VLAN attachments).
+
     --keepalive-interval=KEEPALIVE_INTERVAL
        The interval between BGP keepalive messages that are sent to the peer.
        If set, this value must be between 20 and 60 seconds. The default is 20
--- a/gcloud/beta/compute/routers/nats/create
+++ b/gcloud/beta/compute/routers/nats/create
@ -11,6 +11,7 @@ SYNOPSIS
          | --nat-primary-subnet-ip-ranges) [--async]
        [--[no-]enable-dynamic-port-allocation]
        [--enable-endpoint-independent-mapping] [--enable-logging]
+        [--endpoint-types=[ENDPOINT_TYPE,...]]
        [--icmp-idle-timeout=ICMP_IDLE_TIMEOUT] [--log-filter=LOG_FILTER]
        [--max-ports-per-vm=MAX_PORTS_PER_VM]
        [--min-ports-per-vm=MIN_PORTS_PER_VM] [--region=REGION] [--rules=RULES]
@ -111,6 +112,20 @@ OPTIONAL FLAGS
        gcloud beta compute routers nats update MY-NAT \ --no-enable-logging
        --router ROUTER --region REGION

+     --endpoint-types=[ENDPOINT_TYPE,...]
+        Endpoint Types supported by the NAT Gateway.
+
+            ENDPOINT_TYPE must be one of:
+
+            ENDPOINT_TYPE_VM
+              For VM Endpoints
+            ENDPOINT_TYPE_SWG
+              For Secure Web Gateway Endpoints
+
+        The default is ENDPOINT_TYPE_VM.
+
+        ENDPOINT_TYPE must be one of: ENDPOINT_TYPE_VM, ENDPOINT_TYPE_SWG.
+
     --icmp-idle-timeout=ICMP_IDLE_TIMEOUT
        Timeout for ICMP connections. See
        https://cloud.google.com/sdk/gcloud/reference/topic/datetimes for
--- a/gcloud/beta/compute/vpn-gateways/create
+++ b/gcloud/beta/compute/vpn-gateways/create
@ -4,8 +4,9 @@ NAME

 SYNOPSIS
    gcloud beta compute vpn-gateways create NAME --network=NETWORK
-        [--description=DESCRIPTION] [--region=REGION] [--stack-type=STACK_TYPE]
-        [GCLOUD_WIDE_FLAG ...]
+        [--description=DESCRIPTION]
+        [--interconnect-attachments=[INTERCONNECT_ATTACHMENTS,...]]
+        [--region=REGION] [--stack-type=STACK_TYPE] [GCLOUD_WIDE_FLAG ...]

 DESCRIPTION
    (BETA) gcloud beta compute vpn-gateways create creates a new Highly
@ -35,6 +36,17 @@ OPTIONAL FLAGS
     --description=DESCRIPTION
        An optional, textual description for the VPN gateway.

+     --interconnect-attachments=[INTERCONNECT_ATTACHMENTS,...]
+        Names of interconnect attachments (VLAN attachments) associated with
+        the VPN gateway interfaces. You must specify this field when using a
+        VPN gateway for HA VPN over Cloud Interconnect. Otherwise, this field
+        is optional.
+
+        For example, --interconnect-attachments
+        attachment-a-zone1,attachment-a-zone2 associates VPN gateway with
+        attachment from zone1 on interface 0 and with attachment from zone2 on
+        interface 1.
+
     --region=REGION
        Region of the VPN Gateway to create. If not specified, you might be
        prompted to select a region (interactive mode only).