-
--balancing-mode
BALANCING_MODE
-
Defines the strategy for balancing load.
UTILIZATION
will
rely on the CPU utilization of the tasks in the group when
balancing load. When using UTILIZATION
,
--max-utilization
can be used to set a maximum target CPU
utilization for each task. RATE
will spread load based on
how many requests per second (RPS) the group can handle. There
are two ways to specify max RPS: --max-rate
which defines
the max RPS for the whole group or --max-rate-per-task
which
defines the max RPS on a per-task basis.
- In
UTILIZATION
, you can optionally limit based on RPS in
addition to CPU by setting either --max-rate-per-task
or
--max-rate
.
-
--capacity-scaler
CAPACITY_SCALER
-
A float in the range [0.0, 1.0] that scales the maximum
parameters for the group (e.g., max rate). A value of 0.0 will
cause no requests to be sent to the group (i.e., it adds the
group in a
drained
state). The default is 1.0.
-
--description
DESCRIPTION
-
An optional, textual description for the backend.
-
--group
GROUP
-
The name or URI of a Google Cloud Resource View that can receive traffic.
-
--max-rate
MAX_RATE
-
Maximum requests per second (RPS) that the group can handle.
-
--max-rate-per-instance
MAX_RATE_PER_INSTANCE
-
The maximum per-instance requests per second (RPS).
-
--max-utilization
MAX_UTILIZATION
-
The target CPU utilization for the group as a float in the range
[0, 1e6]. This flag can only be provided when the balancing
mode is
UTILIZATION
.
-
--zone
ZONE
-
The zone of the resource view to add to the backend service. If not specified, you will be prompted to select a zone.
- To avoid prompting when this flag is omitted, you can set the
compute/zone
property:
$ gcloud config set compute/zone ZONE
- A list of zones can fetched by running:
$ gcloud compute zones list
- To unset the property, run:
$ gcloud config unset compute/zone
- Alternatively, the zone can be stored in the environment variable
CLOUDSDK_COMPUTE_ZONE
.