gcloud alpha compute health-checks update http2 Stay organized with collections Save and categorize content based on your preferences.
- NAME
- gcloud alpha compute health-checks update http2 - update a HTTP2 health check
- SYNOPSIS
gcloud alpha compute health-checks update http2NAME[--check-interval=CHECK_INTERVAL][--description=DESCRIPTION][--enable-logging][--healthy-threshold=HEALTHY_THRESHOLD][--host=HOST][--proxy-header=PROXY_HEADER][--request-path=REQUEST_PATH][--response=RESPONSE][--timeout=TIMEOUT][--unhealthy-threshold=UNHEALTHY_THRESHOLD][--weight-report-mode=WEIGHT_REPORT_MODE][--global|--region=REGION][--port=PORT--port-name=PORT_NAME--use-serving-port][GCLOUD_WIDE_FLAG …]
- DESCRIPTION
(ALPHA)gcloud alpha compute health-checks updatehttp2is used to update an existing HTTP2 health check. Only argumentspassed in will be updated on the health check. Other attributes will remainunaffected.- EXAMPLES
- To update health check interval to 10s, run:
gcloudalphacomputehealth-checksupdatehttp2my-health-check-name--check-interval=10s - POSITIONAL ARGUMENTS
NAME- Name of the HTTP2 health check to update.
- FLAGS
--check-interval=CHECK_INTERVAL- How often to perform a health check for an instance. For example, specifying
will run the check every 10 seconds.See $gcloud topic datetimesfor information on duration formats.10s --description=DESCRIPTION- A textual description for the HTTP2 health check. Pass in an empty string tounset.
--enable-logging- Enable logging of health check probe results to Stackdriver. Logging is disabledby default.
Use --no-enable-logging to disable logging.
--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 HTTP health check request. The hostheader is empty by default. When empty, the health check will set the hostheader to the IP address of the backend VM or endpoint. You can set the hostheader to an empty value to return to this default behavior.
--proxy-header=PROXY_HEADER- The type of proxy protocol header to be sent to the backend.
PROXY_HEADERmust be one of:NONE- No proxy header is added.
PROXY_V1- Adds the header "PROXY UNKNOWN\r\n".
--request-path=REQUEST_PATH- The request path that this health check monitors. For example,
./healthcheck --response=RESPONSE- When empty, status code of the response determines health. When not empty,presence of specified string in first 1024 characters of response bodydetermines health. Only ASCII characters allowed.
--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, specifying
will cause the check to wait for 10seconds before considering the request a failure. See $gcloud topic datetimes forinformation on duration formats.10s --unhealthy-threshold=UNHEALTHY_THRESHOLD- The number of consecutive health check failures before a healthy instance ismarked as unhealthy.
--weight-report-mode=WEIGHT_REPORT_MODE- Defines whether Weighted Load Balancing is enabled.
WEIGHT_REPORT_MODEmust be one of:ENABLE,DISABLE,DRY_RUN. - At most one of these can be specified:
--global- If set, the HTTP2 health check is global.
--region=REGION- Region of the HTTP2 health check to update. If not specified, you might beprompted to select a region (interactive mode only).
To avoid prompting when this flag is omitted, you can set the
property:compute/regiongcloudconfigsetcompute/regionREGIONA list of regions can be fetched by running:
gcloudcomputeregionslistTo unset the property, run:
gcloudconfigunsetcompute/regionAlternatively, the region can be stored in the environment variable
.CLOUDSDK_COMPUTE_REGION
- These flags configure the port that the health check monitors. If both
--portand--port-nameare specified,--porttakes precedence.--port=PORT- The TCP port number that this health check monitors.
--port-name=PORT_NAME- The port name that this health check monitors. By default, this is empty.Setting this to an empty string will clear any existing port-name value.
--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-portmust be used whenusing a Network Endpoint Group as a backend as this flag specifies theportSpecificationoption for a Health Check object. - When health checking other backends, use the port or named port of the backendservice.
- When health checking network endpoints in a Network Endpoint Group, use the portspecified with each endpoint.
- GCLOUD WIDE FLAGS
- These flags are available to all commands:
--access-token-file,--account,--billing-project,--configuration,--flags-file,--flatten,--format,--help,--impersonate-service-account,--log-http,--project,--quiet,--trace-token,--user-output-enabled,--verbosity.Run
$gcloud helpfor details. - NOTES
- This command is currently in alpha and might change without notice. If thiscommand fails with API permission errors despite specifying the correct project,you might be trying to access an API with an invitation-only early accessallowlist. These variants are also available:
gcloudcomputehealth-checksupdatehttp2gcloudbetacomputehealth-checksupdatehttp2
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-05-07 UTC.