gcloud beta compute https-health-checks update - update a legacy HTTPS health check

gcloud beta compute https-health-checks updateNAME[--check-interval=CHECK_INTERVAL][--description=DESCRIPTION][--healthy-threshold=HEALTHY_THRESHOLD][--host=HOST][--port=PORT][--request-path=REQUEST_PATH][--timeout=TIMEOUT][--unhealthy-threshold=UNHEALTHY_THRESHOLD][GCLOUD_WIDE_FLAG …]

NAME

Name of the HTTPS 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 HTTPS health check. Pass in an empty string tounset.

--healthy-threshold=HEALTHY_THRESHOLD

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

--host=HOST

The value of the host header used in this HTTPS health check request. Bydefault, this is empty and Compute Engine automatically sets the host header inhealth requests to the same external IP address as the forwarding ruleassociated with the target pool. Setting this to an empty string will clear anyexisting host value.

--port=PORT

The TCP port number that this health check monitors.

--request-path=REQUEST_PATH

The request path that this health check monitors. For example,/healthcheck.

--timeout=TIMEOUT

If Compute Engine doesn't receive an HTTPS 200 response from the instance by thetime specified by the value of this flag, the health check request is considereda failure. For example, specifying10s willcause the check to wait for 10 seconds before considering the request a failure.See $gcloud topic datetimesfor information on duration formats.

--unhealthy-threshold=UNHEALTHY_THRESHOLD

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

Run$gcloud help for details.