imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-18 14:56:05 +00:00
Code Activity

gcloud: Mon Oct 23 11:10:08 UTC 2023

Browse source
This commit is contained in:
Automated 2023-10-23 11:10:09 +00:00
parent c30bb7b4ce
commit a15665661a
123 changed files with 3724 additions and 306 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -24,6 +24,7 @@ SYNOPSIS
[--iap=disabled|enabled,[oauth2-client-id=OAUTH2-CLIENT-ID,
oauth2-client-secret=OAUTH2-CLIENT-SECRET]]
[--idle-timeout-sec=IDLE_TIMEOUT_SEC]
[--ip-address-selection-policy=IP_ADDRESS_SELECTION_POLICY]
[--load-balancing-scheme=LOAD_BALANCING_SCHEME; default="EXTERNAL"]
[--locality-lb-policy=LOCALITY_LB_POLICY]
[--logging-optional=LOGGING_OPTIONAL]
@ -337,6 +338,32 @@ FLAGS
service-based external and internal passthrough Network Load Balancers
as part of a connection tracking policy.
--ip-address-selection-policy=IP_ADDRESS_SELECTION_POLICY
Specifies a preference for traffic sent from the proxy to the backend
(or from the client to the backend for proxyless gRPC).
Can only be set if load balancing scheme is INTERNAL_SELF_MANAGED,
INTERNAL_MANAGED or EXTERNAL_MANAGED.
The possible values are:
IPV4_ONLY
Only send IPv4 traffic to the backends of the backend service,
regardless of traffic from the client to the proxy. Only IPv4
health checks are used to check the health of the backends.
PREFER_IPV6
Prioritize the connection to the endpoint's IPv6 address over its IPv4
address (provided there is a healthy IPv6 address).
IPV6_ONLY
Only send IPv6 traffic to the backends of the backend service,
regardless of traffic from the client to the proxy. Only IPv6
health checks are used to check the health of the backends.
IP_ADDRESS_SELECTION_POLICY must be one of: IPV4_ONLY, PREFER_IPV6,
IPV6_ONLY.
--load-balancing-scheme=LOAD_BALANCING_SCHEME; default="EXTERNAL"
Specifies the load balancer type. Choose EXTERNAL for the classic
Application Load Balancers, the external passthrough Network Load

14
gcloud/beta/compute/backend-services/list-usable
View file

@ -9,10 +9,10 @@ SYNOPSIS
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) $ gcloud beta compute backend-services list-usable retrieves the
list of backend service resources in the specified project for which you
have compute.backendService.get and compute.backendService.use permissions.
This command is useful when you're creating load balancers in a Shared VPC
(BETA) gcloud beta compute backend-services list-usable retrieves the list
of backend service resources in the specified project for which you have
compute.backendService.get and compute.backendService.use permissions. This
command is useful when you're creating load balancers in a Shared VPC
environment and you want to use cross-project service referencing
(https://cloud.google.com/load-balancing/docs/https#cross-project). You can
use this command to find out which backend services in other projects are
@ -82,8 +82,10 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud compute backend-services list-usable
$ gcloud alpha compute backend-services list-usable

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

@ -20,6 +20,7 @@ SYNOPSIS
[--iap=disabled|enabled,[oauth2-client-id=OAUTH2-CLIENT-ID,
oauth2-client-secret=OAUTH2-CLIENT-SECRET]]
[--idle-timeout-sec=IDLE_TIMEOUT_SEC]
[--ip-address-selection-policy=IP_ADDRESS_SELECTION_POLICY]
[--locality-lb-policy=LOCALITY_LB_POLICY]
[--logging-optional=LOGGING_OPTIONAL]
[--logging-optional-fields=[LOGGING_OPTIONAL_FIELDS,...]]
@ -256,6 +257,32 @@ FLAGS
service-based external and internal passthrough Network Load Balancers
as part of a connection tracking policy.
--ip-address-selection-policy=IP_ADDRESS_SELECTION_POLICY
Specifies a preference for traffic sent from the proxy to the backend
(or from the client to the backend for proxyless gRPC).
Can only be set if load balancing scheme is INTERNAL_SELF_MANAGED,
INTERNAL_MANAGED or EXTERNAL_MANAGED.
The possible values are:
IPV4_ONLY
Only send IPv4 traffic to the backends of the backend service,
regardless of traffic from the client to the proxy. Only IPv4
health checks are used to check the health of the backends.
PREFER_IPV6
Prioritize the connection to the endpoint's IPv6 address over its IPv4
address (provided there is a healthy IPv6 address).
IPV6_ONLY
Only send IPv6 traffic to the backends of the backend service,
regardless of traffic from the client to the proxy. Only IPv6
health checks are used to check the health of the backends.
IP_ADDRESS_SELECTION_POLICY must be one of: IPV4_ONLY, PREFER_IPV6,
IPV6_ONLY.
--locality-lb-policy=LOCALITY_LB_POLICY
The load balancing algorithm used within the scope of the locality.
LOCALITY_LB_POLICY must be one of: INVALID_LB_POLICY, ROUND_ROBIN,

10
gcloud/beta/compute/sole-tenancy/node-groups/create
View file

@ -43,12 +43,14 @@ OPTIONAL FLAGS
MAINTENANCE_INTERVAL must be one of:
as-needed
VMs are eligible to receive infrastructure and hypervisor updates
hosts are eligible to receive infrastructure and hypervisor updates
as they become available.
recurrent
VMs receive infrastructure and hypervisor updates on a periodic
basis, minimizing the number of maintenance operations (live
migrations or terminations) on an individual VM.
hosts receive planned infrastructure and hypervisor updates on a
periodic basis, but not more frequently than every 28 days. This
minimizes the number of planned maintenance operations on
individual hosts and reduces the frequency of disruptions, both
live migrations and terminations, on individual VMs.
--maintenance-policy=MAINTENANCE_POLICY
Determines the maintenance behavior during host maintenance events. For