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 Jul 26 10:48:49 UTC 2023

Browse source
This commit is contained in:
Automated 2023-07-26 10:48:49 +00:00
parent 64e67b443c
commit 4558a00e48
204 changed files with 2787 additions and 1591 deletions
Download patch file Download diff file Expand all files Collapse all files

110
gcloud/compute/backend-services/create
View file

@ -207,8 +207,8 @@ FLAGS
--custom-request-header "another-header:"
--custom-response-header=CUSTOM_RESPONSE_HEADER
Custom headers that the external HTTP(S) load balancer adds to proxied
responses. For the list of headers, see Creating custom headers
Custom headers that the external Application Load Balancer adds to
proxied responses. For the list of headers, see Creating custom headers
(https://cloud.google.com/load-balancing/docs/custom-headers).
Variables are not case-sensitive.
@ -243,13 +243,13 @@ FLAGS
--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 network load
balancers and internal TCP/UDP load balancers as part of a connection
--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 TCP/UDP load balancing
backends for internal passthrough Network Load Balancers
(https://cloud.google.com/load-balancing/docs/internal#connection-persistence)
and Connection persistence on unhealthy backends for network load
balancing
and Connection persistence on unhealthy backends for external
passthrough Network Load Balancers
(https://cloud.google.com/load-balancing/docs/network/networklb-backend-service#connection-persistence).
--[no-]enable-cdn
@ -262,9 +262,9 @@ FLAGS
--[no-]enable-logging
The logging options for the load balancer traffic served by this
backend service. If logging is enabled, logs will be exported to Cloud
Logging. Disabled by default. This field cannot be specified for SSL
Proxy and TCP Proxy Load Balancing. Use --enable-logging to enable and
--no-enable-logging to disable.
Logging. Disabled by default. This field cannot be specified for global
external proxy Network Load Balancers. Use --enable-logging to enable
and --no-enable-logging to disable.
--[no-]enable-strong-affinity
Enable or disable strong session affinity. This is only available for
@ -287,9 +287,9 @@ FLAGS
health of the backend service.
Legacy health checks are not recommended for backend services. It is
possible to use a legacy health check on a backend service for a
HTTP(S) load balancer if that backend service uses instance groups. For
more information, refer to this guide:
possible to use a legacy health check on a backend service for an
Application Load Balancer if that backend service uses instance groups.
For more information, refer to this guide:
https://cloud.google.com/load-balancing/docs/health-check-concepts#lb_guide.
--https-health-checks=HTTPS_HEALTH_CHECK,[...]
@ -297,9 +297,9 @@ FLAGS
health of the backend service.
Legacy health checks are not recommended for backend services. It is
possible to use a legacy health check on a backend service for a
HTTP(S) load balancer if that backend service uses instance groups. For
more information, refer to this guide:
possible to use a legacy health check on a backend service for an
Application Load Balancer if that backend service uses instance groups.
For more information, refer to this guide:
https://cloud.google.com/load-balancing/docs/health-check-concepts#lb_guide.
--iap=disabled|enabled,[oauth2-client-id=OAUTH2-CLIENT-ID,oauth2-client-secret=OAUTH2-CLIENT-SECRET]
@ -314,19 +314,20 @@ FLAGS
--idle-timeout-sec=IDLE_TIMEOUT_SEC
Specifies how long to keep a connection tracking table entry while
there is no matching traffic (in seconds). Applicable only for backend
service-based network load balancers and internal TCP/UDP load
balancers as part of a connection tracking policy.
service-based external and internal passthrough Network Load Balancers
as part of a connection tracking policy.
--load-balancing-scheme=LOAD_BALANCING_SCHEME; default="EXTERNAL"
Specifies the load balancer type. Choose EXTERNAL for the classic
HTTP(S) load balancers, the external TCP/UDP network load balancers,
and the external TCP/SSL proxy load balancers. Choose EXTERNAL_MANAGED
for the Envoy-based global and regional external HTTP(S) load
balancers. Choose INTERNAL for internal TCP/UDP load balancers. Choose
INTERNAL_MANAGED for Envoy-based internal load balancers such as the
internal HTTP(S) load balancers and the internal TCP proxy load
balancers. Choose INTERNAL_SELF_MANAGED for Traffic Director. For more
information, refer to this guide:
Application Load Balancers, the external passthrough Network Load
Balancers, and the global external proxy Network Load Balancers. Choose
EXTERNAL_MANAGED for the Envoy-based global and regional external
Application Load Balancers, and the regional external proxy Network
Load Balancers. Choose INTERNAL for the internal passthrough Network
Load Balancers. Choose INTERNAL_MANAGED for Envoy-based internal load
balancers such as the internal Application Load Balancers and the
internal proxy Network Load Balancers. Choose INTERNAL_SELF_MANAGED for
Traffic Director. For more information, refer to this guide:
https://cloud.google.com/load-balancing/docs/choosing-load-balancer.
LOAD_BALANCING_SCHEME must be one of: INTERNAL, EXTERNAL,
INTERNAL_SELF_MANAGED, EXTERNAL_MANAGED, INTERNAL_MANAGED.
@ -341,8 +342,8 @@ FLAGS
This field can only be specified if logging is enabled for the backend
service. Configures whether all, none, or a subset of optional fields
should be added to the reported logs. Default is EXCLUDE_ALL_OPTIONAL.
This field can only be specified for Internal TCP/UDP Load Balancing
and External Network Load Balancing. LOGGING_OPTIONAL must be one of:
This field can only be specified for internal and external passthrough
Network Load Balancers. LOGGING_OPTIONAL must be one of:
EXCLUDE_ALL_OPTIONAL, INCLUDE_ALL_OPTIONAL, CUSTOM.
--logging-optional-fields=[LOGGING_OPTIONAL_FIELDS,...]
@ -351,7 +352,7 @@ FLAGS
comma-separated list of optional fields you want to include in the
logs. For example: serverInstance, serverGkeDetails.cluster,
serverGkeDetails.pod.podNamespace. This can only be specified for
Internal TCP/UDP Load Balancing and External Network Load Balancing.
internal and external passthrough Network Load Balancers.
--logging-sample-rate=LOGGING_SAMPLE_RATE
This field can only be specified if logging is enabled for the backend
@ -444,9 +445,9 @@ FLAGS
load-balancing-scheme is INTERNAL.
--port-name=PORT_NAME
Backend services for external HTTP(S) load balancing, internal HTTP(S)
load balancing, TCP proxy load balancing, and SSL proxy load balancing
must reference exactly one named port if using instance group backends.
Backend services for Application Load Balancers and proxy Network Load
Balancers must reference exactly one named port if using instance group
backends.
Each instance group backend exports one or more named ports, which map
a user-configurable name to a port number. The backend service's named
@ -461,8 +462,8 @@ FLAGS
◆ For any load balancer, if the backends are not instance groups (for
example, GCE_VM_IP_PORT NEGs).
◆ For any type of backend on a backend service for internal TCP/UDP
load balancing or external TCP/UDP network load balancing.
◆ For any type of backend on a backend service for internal or
external passthrough Network Load Balancers.
See also
https://cloud.google.com/load-balancing/docs/backend-service#named_ports.
@ -470,26 +471,26 @@ FLAGS
--protocol=PROTOCOL
Protocol for incoming requests.
If the load-balancing-scheme is INTERNAL (Internal TCP/UDP Load
Balancing), the protocol must be one of: TCP, UDP, UNSPECIFIED.
If the load-balancing-scheme is INTERNAL (Internal passthrough Network
Load Balancer), the protocol must be one of: TCP, UDP, UNSPECIFIED.
If the load-balancing-scheme is INTERNAL_SELF_MANAGED (Traffic
Director), the protocol must be one of: HTTP, HTTPS, HTTP2, GRPC.
If the load-balancing-scheme is INTERNAL_MANAGED (Internal HTTP(S) Load
Balancing), the protocol must be one of: HTTP, HTTPS, HTTP2.
If the load-balancing-scheme is INTERNAL_MANAGED (Internal Application
Load Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2.
If the load-balancing-scheme is EXTERNAL and region is not set
(HTTP(S), SSL Proxy, or TCP Proxy Load Balancing), the protocol must be
one of: HTTP, HTTPS, HTTP2, SSL, TCP.
If the load-balancing-scheme is EXTERNAL and region is not set (Classic
Application Load Balancer and global external proxy Network Load
Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2, SSL, TCP.
If the load-balancing-scheme is EXTERNAL and region is set (External
Network Load Balancing), the protocol must be one of: TCP, UDP,
UNSPECIFIED.
passthrough Network Load Balancer), the protocol must be one of: TCP,
UDP, UNSPECIFIED.
If the load-balancing-scheme is EXTERNAL_MANAGED (Envoy based External
HTTP(S) Load Balancing), the protocol must be one of: HTTP, HTTPS,
HTTP2.
If the load-balancing-scheme is EXTERNAL_MANAGED (Envoy based Global
and regional external Application Load Balancers), the protocol must be
one of: HTTP, HTTPS, HTTP2.
--[no-]request-coalescing
Enables request coalescing to the backend (recommended).
@ -610,11 +611,11 @@ FLAGS
one of: NONE, CONSISTENT_HASH_SUBSETTING.
--timeout=TIMEOUT; default="30s"
Applicable to all load balancing products except Internal TCP/UDP Load
Balancing and External TCP/UDP Network Load Balancing. For Internal
TCP/UDP Load Balancing (load-balancing-scheme set to INTERNAL) and
External TCP/UDP Network Load Balancing (global not set and
load-balancing-scheme set to EXTERNAL), timeout is ignored.
Applicable to all load balancing products except passthrough Network
Load Balancers. For internal passthrough Network Load Balancers
(load-balancing-scheme set to INTERNAL) and external passthrough
Network Load Balancers (global not set and load-balancing-scheme set to
EXTERNAL), timeout is ignored.
If the protocol is HTTP, HTTPS, or HTTP2, timeout is a request/response
timeout for HTTP(S) traffic, meaning the amount of time that the load
@ -639,11 +640,12 @@ FLAGS
--tracking-mode=TRACKING_MODE
Specifies the connection key used for connection tracking. The default
value is PER_CONNECTION. Applicable only for backend service-based
network load balancers and internal TCP/UDP load balancers as part of a
external and internal passthrough Network Load Balancers as part of a
connection tracking policy. For details, see: Connection tracking mode
for internal TCP/UDP load balancing
for internal passthrough Network Load Balancers balancing
(https://cloud.google.com/load-balancing/docs/internal#tracking-mode)
and Connection tracking mode for network load balancing
and Connection tracking mode for external passthrough Network Load
Balancers
(https://cloud.google.com/load-balancing/docs/network/networklb-backend-service#tracking-mode).
TRACKING_MODE must be one of: PER_CONNECTION, PER_SESSION.