imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-16 20:36:39 +00:00
Code Activity

gcloud: Wed Apr 27 09:13:09 UTC 2022

Browse source
This commit is contained in:
Automated 2022-04-27 09:13:09 +00:00
parent 72862dfe28
commit 532fac5ddb
131 changed files with 1510 additions and 390 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -534,36 +534,39 @@ FLAGS
same backend VM while that VM remains healthy.
GENERATED_COOKIE
(Applicable if --load-balancing-scheme is INTERNAL_MANAGED,
INTERNAL_SELF_MANAGED, or EXTERNAL) If the --load-balancing-scheme
is EXTERNAL or EXTERNAL_MANAGED, routes requests to backend VMs or
endpoints in a NEG, based on the contents of the GCLB cookie set by
the load balancer. Only applicable when --protocol is HTTP, HTTPS,
or HTTP2. If the --load-balancing-scheme is INTERNAL_MANAGED or
INTERNAL_SELF_MANAGED, EXTERNAL_MANAGED, or EXTERNAL) If the
--load-balancing-scheme is EXTERNAL or EXTERNAL_MANAGED, routes
requests to backend VMs or endpoints in a NEG, based on the
contents of the GCLB cookie set by the load balancer. Only
applicable when --protocol is HTTP, HTTPS, or HTTP2. If the
--load-balancing-scheme is INTERNAL_MANAGED or
INTERNAL_SELF_MANAGED, routes requests to backend VMs or endpoints
in a NEG, based on the contents of the GCILB cookie set by the
proxy. (If no cookie is present, the proxy chooses a backend VM or
endpoint and sends a Set-Cookie response for future requests.) If
the --load-balancing-scheme is INTERNAL_SELF_MANAGED, routes
requests to backend VMs or endpoints in a NEG, based on the
contents of a cookie set by Traffic Director.
contents of a cookie set by Traffic Director. This session affinity
is only valid if the load balancing locality policy is either
RING_HASH or MAGLEV.
HEADER_FIELD
(Applicable if --load-balancing-scheme is INTERNAL_MANAGED or
INTERNAL_SELF_MANAGED) Route requests to backend VMs or endpoints
in a NEG based on the value of the HTTP header named in the
--custom-request-header flag. This session affinity is only valid
if the load balancing locality policy is either RING_HASH or MAGLEV
and the backend service's consistent hash specifies the name of the
HTTP header.
(Applicable if --load-balancing-scheme is INTERNAL_MANAGED,
EXTERNAL_MANAGED, or INTERNAL_SELF_MANAGED) Route requests to
backend VMs or endpoints in a NEG based on the value of the HTTP
header named in the --custom-request-header flag. This session
affinity is only valid if the load balancing locality policy is
either RING_HASH or MAGLEV and the backend service's consistent
hash specifies the name of the HTTP header.
HTTP_COOKIE
(Applicable if --load-balancing-scheme is INTERNAL_MANAGED or
INTERNAL_SELF_MANAGED) Route requests to backend VMs or endpoints
in a NEG, based on an HTTP cookie named in the HTTP_COOKIE flag
(with the optional --affinity-cookie-ttl flag). If the client has
not provided the cookie, the proxy generates the cookie and returns
it to the client in a Set-Cookie header. This session affinity is
only valid if the load balancing locality policy is either
RING_HASH or MAGLEV and the backend service's consistent hash
specifies the HTTP cookie.
(Applicable if --load-balancing-scheme is INTERNAL_MANAGED,
EXTERNAL_MANAGED or INTERNAL_SELF_MANAGED) Route requests to
backend VMs or endpoints in a NEG, based on an HTTP cookie named in
the HTTP_COOKIE flag (with the optional --affinity-cookie-ttl
flag). If the client has not provided the cookie, the proxy
generates the cookie and returns it to the client in a Set-Cookie
header. This session affinity is only valid if the load balancing
locality policy is either RING_HASH or MAGLEV and the backend
service's consistent hash specifies the HTTP cookie.
NONE
Session affinity is disabled.

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

@ -340,36 +340,39 @@ FLAGS
same backend VM while that VM remains healthy.
GENERATED_COOKIE
(Applicable if --load-balancing-scheme is INTERNAL_MANAGED,
INTERNAL_SELF_MANAGED, or EXTERNAL) If the --load-balancing-scheme
is EXTERNAL or EXTERNAL_MANAGED, routes requests to backend VMs or
endpoints in a NEG, based on the contents of the GCLB cookie set by
the load balancer. Only applicable when --protocol is HTTP, HTTPS,
or HTTP2. If the --load-balancing-scheme is INTERNAL_MANAGED or
INTERNAL_SELF_MANAGED, EXTERNAL_MANAGED, or EXTERNAL) If the
--load-balancing-scheme is EXTERNAL or EXTERNAL_MANAGED, routes
requests to backend VMs or endpoints in a NEG, based on the
contents of the GCLB cookie set by the load balancer. Only
applicable when --protocol is HTTP, HTTPS, or HTTP2. If the
--load-balancing-scheme is INTERNAL_MANAGED or
INTERNAL_SELF_MANAGED, routes requests to backend VMs or endpoints
in a NEG, based on the contents of the GCILB cookie set by the
proxy. (If no cookie is present, the proxy chooses a backend VM or
endpoint and sends a Set-Cookie response for future requests.) If
the --load-balancing-scheme is INTERNAL_SELF_MANAGED, routes
requests to backend VMs or endpoints in a NEG, based on the
contents of a cookie set by Traffic Director.
contents of a cookie set by Traffic Director. This session affinity
is only valid if the load balancing locality policy is either
RING_HASH or MAGLEV.
HEADER_FIELD
(Applicable if --load-balancing-scheme is INTERNAL_MANAGED or
INTERNAL_SELF_MANAGED) Route requests to backend VMs or endpoints
in a NEG based on the value of the HTTP header named in the
--custom-request-header flag. This session affinity is only valid
if the load balancing locality policy is either RING_HASH or MAGLEV
and the backend service's consistent hash specifies the name of the
HTTP header.
(Applicable if --load-balancing-scheme is INTERNAL_MANAGED,
EXTERNAL_MANAGED, or INTERNAL_SELF_MANAGED) Route requests to
backend VMs or endpoints in a NEG based on the value of the HTTP
header named in the --custom-request-header flag. This session
affinity is only valid if the load balancing locality policy is
either RING_HASH or MAGLEV and the backend service's consistent
hash specifies the name of the HTTP header.
HTTP_COOKIE
(Applicable if --load-balancing-scheme is INTERNAL_MANAGED or
INTERNAL_SELF_MANAGED) Route requests to backend VMs or endpoints
in a NEG, based on an HTTP cookie named in the HTTP_COOKIE flag
(with the optional --affinity-cookie-ttl flag). If the client has
not provided the cookie, the proxy generates the cookie and returns
it to the client in a Set-Cookie header. This session affinity is
only valid if the load balancing locality policy is either
RING_HASH or MAGLEV and the backend service's consistent hash
specifies the HTTP cookie.
(Applicable if --load-balancing-scheme is INTERNAL_MANAGED,
EXTERNAL_MANAGED or INTERNAL_SELF_MANAGED) Route requests to
backend VMs or endpoints in a NEG, based on an HTTP cookie named in
the HTTP_COOKIE flag (with the optional --affinity-cookie-ttl
flag). If the client has not provided the cookie, the proxy
generates the cookie and returns it to the client in a Set-Cookie
header. This session affinity is only valid if the load balancing
locality policy is either RING_HASH or MAGLEV and the backend
service's consistent hash specifies the HTTP cookie.
NONE
Session affinity is disabled.

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

@ -841,7 +841,7 @@ FLAGS
practice to use --image-family when the latest version of an image is
needed.
By default, debian-10 is assumed for this flag.
By default, debian-11 is assumed for this flag.
Sole Tenancy.

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

@ -26,9 +26,8 @@ SYNOPSIS
[--disk=[auto-delete=AUTO-DELETE],
[boot=BOOT],[device-name=DEVICE-NAME],[mode=MODE],[name=NAME]]
[--labels=[KEY=VALUE,...]]
[--local-ssd=[device-name=DEVICE-NAME],
[interface=INTERFACE],[size=SIZE]] [--machine-type=MACHINE_TYPE]
[--maintenance-policy=MAINTENANCE_POLICY]
[--local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE]]
[--machine-type=MACHINE_TYPE] [--maintenance-policy=MAINTENANCE_POLICY]
[--metadata=KEY=VALUE,[KEY=VALUE,...]]
[--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]]
[--min-cpu-platform=PLATFORM] [--network=NETWORK]
@ -390,11 +389,9 @@ FLAGS
contain only hyphens (-), underscores (_), lowercase characters, and
numbers.
--local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE],[size=SIZE]
--local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE]
Attaches a local SSD to the instances.
This flag is currently in BETA and might change without notice.
device-name
Optional. A name that indicates the disk name the guest operating
system will see. Can only be specified if interface is SCSI. If
@ -406,13 +403,6 @@ FLAGS
supported by more guest operating systems. NVME might provide
higher performance.
size
Optional. Size of the SSD disk. The value must be a whole number
followed by a size unit of KB for kilobyte, MB for megabyte, GB for
gigabyte, or TB for terabyte. For example, 750GB will produce a 750
gigabyte disk. The size must be a multiple of 375 GB and the
default is 375 GB. For Alpha API only.
--machine-type=MACHINE_TYPE
Specifies the machine type used for the instances. To get a list of
available machine types, run 'gcloud compute machine-types list'. If
@ -722,7 +712,7 @@ FLAGS
practice to use --image-family when the latest version of an image is
needed.
By default, debian-10 is assumed for this flag.
By default, debian-11 is assumed for this flag.
At most one of these can be specified:

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

@ -743,7 +743,7 @@ OPTIONAL FLAGS
practice to use --image-family when the latest version of an image is
needed.
By default, debian-10 is assumed for this flag.
By default, debian-11 is assumed for this flag.
--source-snapshot=SOURCE_SNAPSHOT
The name of the source disk snapshot that the instance boot disk will

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

@ -924,7 +924,7 @@ FLAGS
practice to use --image-family when the latest version of an image is
needed.
By default, debian-10 is assumed for this flag.
By default, debian-11 is assumed for this flag.
--source-snapshot=SOURCE_SNAPSHOT
The name of the source disk snapshot that the instance boot disk will

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

@ -29,9 +29,8 @@ SYNOPSIS
[--host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS]
[--instance-termination-action=INSTANCE_TERMINATION_ACTION]
[--labels=[KEY=VALUE,...]]
[--local-ssd=[device-name=DEVICE-NAME],
[interface=INTERFACE],[size=SIZE]] [--machine-type=MACHINE_TYPE]
[--maintenance-policy=MAINTENANCE_POLICY]
[--local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE]]
[--machine-type=MACHINE_TYPE] [--maintenance-policy=MAINTENANCE_POLICY]
[--metadata=KEY=VALUE,[KEY=VALUE,...]]
[--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]]
[--min-cpu-platform=PLATFORM] [--network=NETWORK]
@ -424,11 +423,9 @@ FLAGS
contain only hyphens (-), underscores (_), lowercase characters, and
numbers.
--local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE],[size=SIZE]
--local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE]
Attaches a local SSD to the instances.
This flag is currently in BETA and might change without notice.
device-name
Optional. A name that indicates the disk name the guest operating
system will see. Can only be specified if interface is SCSI. If
@ -440,13 +437,6 @@ FLAGS
supported by more guest operating systems. NVME might provide
higher performance.
size
Optional. Size of the SSD disk. The value must be a whole number
followed by a size unit of KB for kilobyte, MB for megabyte, GB for
gigabyte, or TB for terabyte. For example, 750GB will produce a 750
gigabyte disk. The size must be a multiple of 375 GB and the
default is 375 GB. For Alpha API only.
--machine-type=MACHINE_TYPE
Specifies the machine type used for the instances. To get a list of
available machine types, run 'gcloud compute machine-types list'. If
@ -805,7 +795,7 @@ FLAGS
practice to use --image-family when the latest version of an image is
needed.
By default, debian-10 is assumed for this flag.
By default, debian-11 is assumed for this flag.
At most one of these can be specified:

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

@ -58,6 +58,11 @@ FLAGS
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.
For Private Service Connect NEGs, you can optionally specify --network
and --subnet if --psc-target-service points to a published service. If
--psc-target-service points to the regional service endpoint of a
Google API, do not specify --network or --subnet.
--network-endpoint-type=NETWORK_ENDPOINT_TYPE; default="gce-vm-ip-port"
Determines the spec of endpoints attached to this group.
@ -120,8 +125,12 @@ FLAGS
If not specified, network endpoints may belong to any subnetwork in the
region where the network endpoint group is created.
This is only supported for NEGs with endpoint type gce-vm-ip-port or
gce-vm-ip.
This is only supported for NEGs with endpoint type gce-vm-ip-port,
gce-vm-ip, or private-service-connect. For Private Service Connect
NEGs, you can optionally specify --network and --subnet if
--psc-target-service points to a published service. If
--psc-target-service points to the regional service endpoint of a
Google API, do not specify --network or --subnet.
The serverless routing configurations are only valid when endpoint type of
the network endpoint group is serverless.