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

gcloud: Thu Apr 6 10:23:36 UTC 2023

Browse source
This commit is contained in:
Automated 2023-04-06 10:23:36 +00:00
parent 5fabf24be7
commit 32e56b8b99
209 changed files with 5396 additions and 561 deletions
Download patch file Download diff file Expand all files Collapse all files

27
gcloud/alpha/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]
@ -322,6 +323,32 @@ FLAGS
service-based network load balancers and internal TCP/UDP load
balancers as part of a connection tracking policy.
--ip-address-selection-policy=IP_ADDRESS_SELECTION_POLICY
Specifies preference of traffic to the backend (from the proxy and from
the client 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 endpoints 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 load balancers
that receive traffic from external clients. Choose EXTERNAL_MANAGED for

27
gcloud/alpha/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,...]]
@ -241,6 +242,32 @@ FLAGS
service-based network load balancers and internal TCP/UDP load
balancers as part of a connection tracking policy.
--ip-address-selection-policy=IP_ADDRESS_SELECTION_POLICY
Specifies preference of traffic to the backend (from the proxy and from
the client 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 endpoints 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,