imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-20 13:10:18 +00:00
Code Activity

gcloud: Wed Aug 2 11:22:33 UTC 2023

Browse source
This commit is contained in:
Automated 2023-08-02 11:22:33 +00:00
parent 4558a00e48
commit 678b9afba9
240 changed files with 7837 additions and 521 deletions
Download patch file Download diff file Expand all files Collapse all files

53
gcloud/beta/compute/backend-services/create
View file

@ -180,13 +180,19 @@ FLAGS
AUTOMATIC.
--connection-drain-on-failover
Connection drain is enabled by default and on failover or failback
connections will be drained. If connection drain is disabled, the
existing connection state will be cleared immediately on a best effort
basis on failover or failback, all connections will then be served by
the active pool of instances. Not compatible with the --global flag,
load balancing scheme must be INTERNAL or EXTERNAL, and the protocol
must be TCP.
Applicable only for backend service-based external and internal
passthrough Network Load Balancers as part of a connection tracking
policy. Only applicable when the backend service protocol is TCP. Not
applicable to any other load balancer. Enabled by default, this option
instructs the load balancer to allow established TCP connections to
persist for up to 300 seconds on instances or endpoints in primary
backends during failover, and on instances or endpoints in failover
backends during failback. For details, see: Connection draining on
failover and failback for internal passthrough Network Load Balancers
(https://cloud.google.com/load-balancing/docs/internal/failover-overview#connection_draining)
and Connection draining on failover and failback for external
passthrough Network Load Balancers
(https://cloud.google.com/load-balancing/docs/network/networklb-failover-overview#connection_draining).
--connection-draining-timeout=CONNECTION_DRAINING_TIMEOUT
Connection draining timeout to be used during removal of VMs from
@ -246,16 +252,18 @@ FLAGS
An optional, textual description for the backend service.
--drop-traffic-if-unhealthy
Enable dropping of traffic if there are no healthy VMs detected in both
the primary and backup instance groups. Not compatible with the
--global flag. Applicable only for backend service-based external and
internal passthrough Network Load Balancers as part of a connection
tracking policy. For details, see: Connection persistence on unhealthy
backends for internal passthrough Network Load Balancers
(https://cloud.google.com/load-balancing/docs/internal#connection-persistence)
and Connection persistence on unhealthy backends for external
Applicable only for backend service-based external and internal
passthrough Network Load Balancers as part of a connection tracking
policy. Not applicable to any other load balancer. This option
instructs the load balancer to drop packets when all instances or
endpoints in primary and failover backends do not pass their load
balancer health checks. For details, see: Dropping traffic when all
backend VMs are unhealthy for internal passthrough Network Load
Balancers
(https://cloud.google.com/load-balancing/docs/internal/failover-overview#drop_traffic)
and Dropping traffic when all backend VMs are unhealthy for external
passthrough Network Load Balancers
(https://cloud.google.com/load-balancing/docs/network/networklb-backend-service#connection-persistence).
(https://cloud.google.com/load-balancing/docs/network/networklb-failover-overview#drop_traffic).
--[no-]enable-cdn
Enable or disable Cloud CDN for the backend service. Only available for
@ -277,9 +285,16 @@ FLAGS
and --no-enable-strong-affinity to disable.
--failover-ratio=FAILOVER_RATIO
If the ratio of the healthy VMs in the primary backend is at or below
this number, traffic arriving at the load-balanced IP will be directed
to the failover backend(s). Not compatible with the --global flag.
Applicable only to backend service-based external passthrough Network
load balancers and internal passthrough Network load balancers as part
of a failover policy. Not applicable to any other load balancer. This
option defines the ratio used to control when failover and failback
occur. For details, see: Failover ratio for internal passthrough
Network Load Balancers
(https://cloud.google.com/load-balancing/docs/internal/failover-overview#failover_ratio)
and Failover ratio for external passthrough Network Load Balancer
overview
(https://cloud.google.com/load-balancing/docs/network/networklb-failover-overview#failover_ratio).
--health-checks=HEALTH_CHECK,[...]
Specifies a list of health check objects for checking the health of the

53
gcloud/beta/compute/backend-services/update
View file

@ -127,13 +127,19 @@ FLAGS
AUTOMATIC.
--connection-drain-on-failover
Connection drain is enabled by default and on failover or failback
connections will be drained. If connection drain is disabled, the
existing connection state will be cleared immediately on a best effort
basis on failover or failback, all connections will then be served by
the active pool of instances. Not compatible with the --global flag,
load balancing scheme must be INTERNAL or EXTERNAL, and the protocol
must be TCP.
Applicable only for backend service-based external and internal
passthrough Network Load Balancers as part of a connection tracking
policy. Only applicable when the backend service protocol is TCP. Not
applicable to any other load balancer. Enabled by default, this option
instructs the load balancer to allow established TCP connections to
persist for up to 300 seconds on instances or endpoints in primary
backends during failover, and on instances or endpoints in failover
backends during failback. For details, see: Connection draining on
failover and failback for internal passthrough Network Load Balancers
(https://cloud.google.com/load-balancing/docs/internal/failover-overview#connection_draining)
and Connection draining on failover and failback for external
passthrough Network Load Balancers
(https://cloud.google.com/load-balancing/docs/network/networklb-failover-overview#connection_draining).
--connection-draining-timeout=CONNECTION_DRAINING_TIMEOUT
Connection draining timeout to be used during removal of VMs from
@ -154,16 +160,18 @@ FLAGS
An optional, textual description for the backend service.
--drop-traffic-if-unhealthy
Enable dropping of traffic if there are no healthy VMs detected in both
the primary and backup instance groups. Not compatible with the
--global flag. Applicable only for backend service-based external and
internal passthrough Network Load Balancers as part of a connection
tracking policy. For details, see: Connection persistence on unhealthy
backends for internal passthrough Network Load Balancers
(https://cloud.google.com/load-balancing/docs/internal#connection-persistence)
and Connection persistence on unhealthy backends for external
Applicable only for backend service-based external and internal
passthrough Network Load Balancers as part of a connection tracking
policy. Not applicable to any other load balancer. This option
instructs the load balancer to drop packets when all instances or
endpoints in primary and failover backends do not pass their load
balancer health checks. For details, see: Dropping traffic when all
backend VMs are unhealthy for internal passthrough Network Load
Balancers
(https://cloud.google.com/load-balancing/docs/internal/failover-overview#drop_traffic)
and Dropping traffic when all backend VMs are unhealthy for external
passthrough Network Load Balancers
(https://cloud.google.com/load-balancing/docs/network/networklb-backend-service#connection-persistence).
(https://cloud.google.com/load-balancing/docs/network/networklb-failover-overview#drop_traffic).
--edge-security-policy=EDGE_SECURITY_POLICY
The edge security policy that will be set for this backend service. To
@ -190,9 +198,16 @@ FLAGS
and --no-enable-strong-affinity to disable.
--failover-ratio=FAILOVER_RATIO
If the ratio of the healthy VMs in the primary backend is at or below
this number, traffic arriving at the load-balanced IP will be directed
to the failover backend(s). Not compatible with the --global flag.
Applicable only to backend service-based external passthrough Network
load balancers and internal passthrough Network load balancers as part
of a failover policy. Not applicable to any other load balancer. This
option defines the ratio used to control when failover and failback
occur. For details, see: Failover ratio for internal passthrough
Network Load Balancers
(https://cloud.google.com/load-balancing/docs/internal/failover-overview#failover_ratio)
and Failover ratio for external passthrough Network Load Balancer
overview
(https://cloud.google.com/load-balancing/docs/network/networklb-failover-overview#failover_ratio).
--health-checks=HEALTH_CHECK,[...]
Specifies a list of health check objects for checking the health of the

9
gcloud/beta/compute/commitments/create
View file

@ -98,10 +98,11 @@ 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, compute-optimized-c3,
general-purpose, general-purpose-e2, general-purpose-n2,
general-purpose-n2d, general-purpose-t2d, graphics-optimized,
memory-optimized, memory-optimized-m3.
accelerator-optimized-a3, compute-optimized, compute-optimized-c2d,
compute-optimized-c3, compute-optimized-h3, general-purpose,
general-purpose-e2, general-purpose-n2, general-purpose-n2d,
general-purpose-t2d, graphics-optimized, memory-optimized,
memory-optimized-m3.
Manage the reservations to be created with the commitment.

6
gcloud/beta/compute/instance-templates/create
View file

@ -319,6 +319,12 @@ FLAGS
among other restrictions. For more information, see
https://cloud.google.com/compute/docs/disks/sharing-disks-between-vms.
replica-zones
Required for each regional disk associated with the instance.
Specify the URLs of the zones where the disk should be replicated
to. You must provide exactly two replica zones, and one zone must
be the same as the instance zone.
--description=DESCRIPTION
Specifies a textual description for the instance template.

6
gcloud/beta/compute/instance-templates/create-with-container
View file

@ -351,6 +351,12 @@ FLAGS
among other restrictions. For more information, see
https://cloud.google.com/compute/docs/disks/sharing-disks-between-vms.
replica-zones
Required for each regional disk associated with the instance.
Specify the URLs of the zones where the disk should be replicated
to. You must provide exactly two replica zones, and one zone must
be the same as the instance zone.
--description=DESCRIPTION
Specifies a textual description for the instance template.

6
gcloud/beta/compute/instances/bulk/create
View file

@ -362,6 +362,12 @@ OPTIONAL FLAGS
Path to a Customer-Supplied Encryption Key (CSEK) key file for the
image. Must be specified with image-csek-required.
replica-zones
Required for each regional disk associated with the instance.
Specify the URLs of the zones where the disk should be replicated
to. You must provide exactly two replica zones, and one zone must
be the same as the instance zone.
--description=DESCRIPTION
Specifies a textual description of the instances.

3
gcloud/beta/compute/instances/create
View file

@ -358,8 +358,7 @@ FLAGS
Required for each regional disk associated with the instance.
Specify the URLs of the zones where the disk should be replicated
to. You must provide exactly two replica zones, and one zone must
be the same as the instance zone. You can't use this option with
boot disks.
be the same as the instance zone.
--csek-key-file=FILE
Path to a Customer-Supplied Encryption Key (CSEK) key file that maps

6
gcloud/beta/compute/instances/create-with-container
View file

@ -361,6 +361,12 @@ FLAGS
among other restrictions. For more information, see
https://cloud.google.com/compute/docs/disks/sharing-disks-between-vms.
replica-zones
Required for each regional disk associated with the instance.
Specify the URLs of the zones where the disk should be replicated
to. You must provide exactly two replica zones, and one zone must
be the same as the instance zone.
--description=DESCRIPTION
Specifies a textual description of the instances.

7
gcloud/beta/compute/network-endpoint-groups/create
View file

@ -41,8 +41,8 @@ FLAGS
If this flag isn't specified for a NEG with endpoint type
gce-vm-ip-port or non-gcp-private-ip-port, then every network endpoint
in the network endpoint group must have a port specified. For a NEG
with endpoint type internet-ip-port and internet-fqdn-port. If the
in the network endpoint group must have a port specified. For a global
NEG with endpoint type internet-ip-port and internet-fqdn-port if the
default port is not specified, the well-known port for your backend
protocol is used (80 for HTTP, 443 for HTTPS).
@ -56,7 +56,8 @@ FLAGS
network is used if unspecified.
This is only supported for NEGs with endpoint type gce-vm-ip-port,
non-gcp-private-ip-port, gce-vm-ip, or private-service-connect.
non-gcp-private-ip-port, gce-vm-ip, private-service-connect,
internet-ip-port, or internet-fqdn-port.
For Private Service Connect NEGs, you can optionally specify --network
and --subnet if --psc-target-service points to a published service. If

25
gcloud/beta/compute/network-endpoint-groups/list-network-endpoints
View file

@ -4,8 +4,9 @@ NAME
SYNOPSIS
gcloud beta compute network-endpoint-groups list-network-endpoints NAME
[--global | --zone=ZONE] [--filter=EXPRESSION] [--limit=LIMIT]
[--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...]
[--global | --region=REGION | --zone=ZONE] [--filter=EXPRESSION]
[--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) List network endpoints in a network endpoint group.
@ -27,6 +28,26 @@ FLAGS
--global
If set, the network endpoint group is global.
--region=REGION
Region of the network endpoint group to operate on. 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.
--zone=ZONE
Zone of the network endpoint group to operate on. If not specified
and the compute/zone property isn't set, you might be prompted to

24
gcloud/beta/compute/network-endpoint-groups/update
View file

@ -6,8 +6,8 @@ SYNOPSIS
gcloud beta compute network-endpoint-groups update NAME
(--add-endpoint=[fqdn=FQDN],[instance=INSTANCE],[ip=IP],[port=PORT]
| --remove-endpoint=[fqdn=FQDN],
[instance=INSTANCE],[ip=IP],[port=PORT]) [--global | --zone=ZONE]
[GCLOUD_WIDE_FLAG ...]
[instance=INSTANCE],[ip=IP],[port=PORT])
[--global | --region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Update a Compute Engine network endpoint group.
@ -160,6 +160,26 @@ OPTIONAL FLAGS
--global
If set, the network endpoint group is global.
--region=REGION
Region of the network endpoint group to operate on. 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.
--zone=ZONE
Zone of the network endpoint group to operate on. If not specified
and the compute/zone property isn't set, you might be prompted to

6
gcloud/beta/compute/networks/subnets/create
View file

@ -101,6 +101,8 @@ OPTIONAL FLAGS
--purpose=PURPOSE
The purpose of this subnetwork. PURPOSE must be one of:
GLOBAL_MANAGED_PROXY
Reserved for Global HTTP(S) Load Balancing.
INTERNAL_HTTPS_LOAD_BALANCER
Reserved for Internal HTTP(S) Load Balancing.
PRIVATE
@ -154,8 +156,8 @@ OPTIONAL FLAGS
--role=ROLE
The role of subnetwork. This field is required when the purpose is set
to REGIONAL_MANAGED_PROXY or INTERNAL_HTTPS_LOAD_BALANCER. ROLE must be
one of:
to GLOBAL_MANAGED_PROXY, REGIONAL_MANAGED_PROXY or
INTERNAL_HTTPS_LOAD_BALANCER. ROLE must be one of:
ACTIVE
The ACTIVE subnet that is currently used.

5
gcloud/beta/compute/routers/nats/create
View file

@ -128,10 +128,13 @@ OPTIONAL FLAGS
For VM Endpoints
ENDPOINT_TYPE_SWG
For Secure Web Gateway Endpoints
ENDPOINT_TYPE_MANAGED_PROXY_LB
For regional Application Load Balancers (internal and external) and regional proxy Network Load Balancers (internal and external) endpoints
The default is ENDPOINT_TYPE_VM.
ENDPOINT_TYPE must be one of: ENDPOINT_TYPE_VM, ENDPOINT_TYPE_SWG.
ENDPOINT_TYPE must be one of: ENDPOINT_TYPE_VM, ENDPOINT_TYPE_SWG,
ENDPOINT_TYPE_MANAGED_PROXY_LB.
--icmp-idle-timeout=ICMP_IDLE_TIMEOUT
Timeout for ICMP connections. See

7
gcloud/beta/compute/ssl-policies/create
View file

@ -14,9 +14,10 @@ DESCRIPTION
An SSL policy specifies the server-side support for SSL features. An SSL
policy can be attached to a TargetHttpsProxy or a TargetSslProxy. This
affects connections between clients and the HTTPS or SSL proxy load
balancer. SSL policies do not affect the connection between the load
balancers and the backends.
affects connections between clients and the load balancer. SSL policies do
not affect the connection between the load balancers and the backends. SSL
policies are used by Application Load Balancers and proxy Network Load
Balancers.
POSITIONAL ARGUMENTS
SSL_POLICY

7
gcloud/beta/compute/ssl-policies/delete
View file

@ -14,9 +14,10 @@ DESCRIPTION
An SSL policy specifies the server-side support for SSL features. An SSL
policy can be attached to a TargetHttpsProxy or a TargetSslProxy. This
affects connections between clients and the HTTPS or SSL proxy load
balancer. SSL policies do not affect the connection between the load
balancers and the backends.
affects connections between clients and the load balancer. SSL policies do
not affect the connection between the load balancers and the backends. SSL
policies are used by Application Load Balancers and proxy Network Load
Balancers.
POSITIONAL ARGUMENTS
SSL_POLICY [SSL_POLICY ...]

7
gcloud/beta/compute/ssl-policies/describe
View file

@ -12,9 +12,10 @@ DESCRIPTION
An SSL policy specifies the server-side support for SSL features. An SSL
policy can be attached to a TargetHttpsProxy or a TargetSslProxy. This
affects connections between clients and the HTTPS or SSL proxy load
balancer. SSL policies do not affect the connection between the load
balancers and the backends.
affects connections between clients and the load balancer. SSL policies do
not affect the connection between the load balancers and the backends. SSL
policies are used by Application Load Balancers and proxy Network Load
Balancers.
POSITIONAL ARGUMENTS
SSL_POLICY

7
gcloud/beta/compute/ssl-policies/list-available-features
View file

@ -14,9 +14,10 @@ DESCRIPTION
An SSL policy specifies the server-side support for SSL features. An SSL
policy can be attached to a TargetHttpsProxy or a TargetSslProxy. This
affects connections between clients and the HTTPS or SSL proxy load
balancer. SSL policies do not affect the connection between the load
balancers and the backends.
affects connections between clients and the load balancer. SSL policies do
not affect the connection between the load balancers and the backends. SSL
policies are used by Application Load Balancers and proxy Network Load
Balancers.
FLAGS
--region=REGION

7
gcloud/beta/compute/ssl-policies/update
View file

@ -14,9 +14,10 @@ DESCRIPTION
An SSL policy specifies the server-side support for SSL features. An SSL
policy can be attached to a TargetHttpsProxy or a TargetSslProxy. This
affects connections between clients and the HTTPS or SSL proxy load
balancer. SSL policies do not affect the connection between the load
balancers and the backends.
affects connections between clients and the load balancer. SSL policies do
not affect the connection between the load balancers and the backends. SSL
policies are used by Application Load Balancers and proxy Network Load
Balancers.
POSITIONAL ARGUMENTS
SSL_POLICY

3
gcloud/beta/compute/target-pools/help
View file

@ -6,7 +6,8 @@ SYNOPSIS
gcloud beta compute target-pools COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Control Compute Engine target pools for Network Load Balancing.
(BETA) Control Compute Engine target pools for external passthrough Network
Load Balancers.
For more information about target pools, see the target pools documentation
(https://cloud.google.com/load-balancing/docs/target-pools).