gcloud beta compute health-checks update grpc-with-tls - update a gRPC with TLS health check

gcloud beta compute health-checks update grpc-with-tlsNAME[--check-interval=CHECK_INTERVAL][--description=DESCRIPTION][--enable-logging][--grpc-service-name=GRPC_SERVICE_NAME][--healthy-threshold=HEALTHY_THRESHOLD][--timeout=TIMEOUT][--unhealthy-threshold=UNHEALTHY_THRESHOLD][--global    |--region=REGION][--port=PORT--use-serving-port][GCLOUD_WIDE_FLAG …]

NAME

Name of the gRPC with TLS health check to update.

--check-interval=CHECK_INTERVAL

How often to perform a health check for an instance. For example, specifying10s will run the check every 10 seconds.See $gcloud topic datetimesfor information on duration formats.

--description=DESCRIPTION

A textual description for the gRPC with TLS health check. Pass in an emptystring to unset.

--enable-logging

Enable logging of health check probe results to Stackdriver. Logging is disabledby default.

Use --no-enable-logging to disable logging.

--grpc-service-name=GRPC_SERVICE_NAME

An optional gRPC service name string of up to 1024 characters to include in thegRPC health check request. Pass in an empty string to unset. Only ASCIIcharacters are allowed.

--healthy-threshold=HEALTHY_THRESHOLD

The number of consecutive successful health checks before an unhealthy instanceis marked as healthy.

--timeout=TIMEOUT

If Google Compute Engine doesn't receive a healthy response from the instance bythe time specified by the value of this flag, the health check request isconsidered a failure. For example, specifying10s will cause the check to wait for 10seconds before considering the request a failure. See $gcloud topic datetimes forinformation on duration formats.

--unhealthy-threshold=UNHEALTHY_THRESHOLD

The number of consecutive health check failures before a healthy instance ismarked as unhealthy.

At most one of these can be specified:

--global

If set, the gRPC with TLS health check is global.

--region=REGION

Region of the gRPC with TLS health check to update. If not specified, you mightbe prompted to select a region (interactive mode only).

To avoid prompting when this flag is omitted, you can set thecompute/region property:

gcloudconfigsetcompute/regionREGION

A list of regions can be fetched by running:

gcloudcomputeregionslist

To unset the property, run:

gcloudconfigunsetcompute/region

Alternatively, the region can be stored in the environment variableCLOUDSDK_COMPUTE_REGION.

These flags configure the port that the health check monitors.

--port=PORT

The TCP port number that this health check monitors.

--use-serving-port

If given, use the "serving port" for health checks:

• When health checking network endpoints in a Network Endpoint Group, use the portspecified with each endpoint.--use-serving-port must be used whenusing a Network Endpoint Group as a backend as this flag specifies theportSpecification option for a Health Check object.
• When health checking other backends, use the port of the backend service.

Run$gcloud help for details.