mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-20 21:20:07 +00:00
gcloud: Wed Jul 12 10:20:16 UTC 2023
This commit is contained in:
parent
f52bc665a7
commit
b4c2508b12
300 changed files with 7469 additions and 3231 deletions
|
|
@ -234,20 +234,21 @@ OPTIONAL FLAGS
|
|||
(https://cloud.google.com/load-balancing/docs/backend-service#balancing-mode-combos).
|
||||
|
||||
--preference=PREFERENCE
|
||||
Defines whether this backend should be fully utilized before sending
|
||||
traffic to backends with default preference. This cannot be used with
|
||||
regional managed instance groups and when the endpoint type of an
|
||||
attached network endpoint group is INTERNET_IP_PORT,
|
||||
Defines whether a backend should be fully utilized before sending
|
||||
traffic to backends with default preference. This parameter cannot be
|
||||
used with regional managed instance groups and when the endpoint type
|
||||
of an attached network endpoint group is INTERNET_IP_PORT,
|
||||
INTERNET_FQDN_PORT, or SERVERLESS. PREFERENCE must be one of:
|
||||
|
||||
DEFAULT
|
||||
If preferred backends don't have enough capacity, backends in this
|
||||
layer would be used and traffic would be assigned based on the load
|
||||
balancing algorithm you use. This is the default.
|
||||
This is the default setting. If the designated preferred backends
|
||||
don't have enough capacity, backends in the default category are
|
||||
used. Traffic is distributed between default backends based on the
|
||||
load balancing algorithm you use.
|
||||
|
||||
PREFERRED
|
||||
Backends with this preference level will be filled up to their
|
||||
capacity limits first, based on RTT.
|
||||
Backends with this preference setting are used up to their capacity
|
||||
limits first, while optimizing overall network latency.
|
||||
|
||||
At most one of these can be specified:
|
||||
|
||||
|
|
|
|||
|
|
@ -203,20 +203,21 @@ OPTIONAL FLAGS
|
|||
(https://cloud.google.com/load-balancing/docs/backend-service#balancing-mode-combos).
|
||||
|
||||
--preference=PREFERENCE
|
||||
Defines whether this backend should be fully utilized before sending
|
||||
traffic to backends with default preference. This cannot be used with
|
||||
regional managed instance groups and when the endpoint type of an
|
||||
attached network endpoint group is INTERNET_IP_PORT,
|
||||
Defines whether a backend should be fully utilized before sending
|
||||
traffic to backends with default preference. This parameter cannot be
|
||||
used with regional managed instance groups and when the endpoint type
|
||||
of an attached network endpoint group is INTERNET_IP_PORT,
|
||||
INTERNET_FQDN_PORT, or SERVERLESS. PREFERENCE must be one of:
|
||||
|
||||
DEFAULT
|
||||
If preferred backends don't have enough capacity, backends in this
|
||||
layer would be used and traffic would be assigned based on the load
|
||||
balancing algorithm you use. This is the default.
|
||||
This is the default setting. If the designated preferred backends
|
||||
don't have enough capacity, backends in the default category are
|
||||
used. Traffic is distributed between default backends based on the
|
||||
load balancing algorithm you use.
|
||||
|
||||
PREFERRED
|
||||
Backends with this preference level will be filled up to their
|
||||
capacity limits first, based on RTT.
|
||||
Backends with this preference setting are used up to their capacity
|
||||
limits first, while optimizing overall network latency.
|
||||
|
||||
At most one of these can be specified:
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue