mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-08 18:45:13 +00:00
87 lines
3.5 KiB
Text
87 lines
3.5 KiB
Text
NAME
|
|
gcloud compute https-health-checks create - create a legacy HTTPS health
|
|
check
|
|
|
|
SYNOPSIS
|
|
gcloud compute https-health-checks create NAME
|
|
[--check-interval=CHECK_INTERVAL; default="5s"]
|
|
[--description=DESCRIPTION]
|
|
[--healthy-threshold=HEALTHY_THRESHOLD; default=2] [--host=HOST]
|
|
[--port=PORT; default=443] [--request-path=REQUEST_PATH; default="/"]
|
|
[--timeout=TIMEOUT; default="5s"]
|
|
[--unhealthy-threshold=UNHEALTHY_THRESHOLD; default=2]
|
|
[GCLOUD_WIDE_FLAG ...]
|
|
|
|
DESCRIPTION
|
|
Though you can use legacy HTTPS health checks in certain Google Cloud
|
|
Platform load balancing configurations and for managed instance group
|
|
autohealing, you should consider a non-legacy HTTPS health check created
|
|
with health-checks create https instead.
|
|
|
|
For more information about the differences between legacy and non-legacy
|
|
health checks see:
|
|
https://cloud.google.com/load-balancing/docs/health-check-concepts#category_and_protocol
|
|
|
|
For information about what type of health check to use for a particular
|
|
load balancer, see:
|
|
https://cloud.google.com/load-balancing/docs/health-check-concepts#lb_guide
|
|
|
|
POSITIONAL ARGUMENTS
|
|
NAME
|
|
Name of the HTTPS health check to create.
|
|
|
|
FLAGS
|
|
--check-interval=CHECK_INTERVAL; default="5s"
|
|
How often to perform a health check for an instance. For example,
|
|
specifying 10s will run the check every 10 seconds. The default value
|
|
is 5s. See $ gcloud topic datetimes for information on duration
|
|
formats.
|
|
|
|
--description=DESCRIPTION
|
|
An optional, textual description for the HTTPS health check.
|
|
|
|
--healthy-threshold=HEALTHY_THRESHOLD; default=2
|
|
The number of consecutive successful health checks before an unhealthy
|
|
instance is marked as healthy. The default is 2.
|
|
|
|
--host=HOST
|
|
The value of the host header used in this HTTPS health check request.
|
|
By default, this is empty and Compute Engine automatically sets the
|
|
host header in health requests to the same external IP address as the
|
|
forwarding rule associated with the target pool.
|
|
|
|
--port=PORT; default=443
|
|
The TCP port number that this health check monitors. The default value
|
|
is 443.
|
|
|
|
--request-path=REQUEST_PATH; default="/"
|
|
The request path that this health check monitors. For example,
|
|
/healthcheck. The default value is ``/''.
|
|
|
|
--timeout=TIMEOUT; default="5s"
|
|
If Compute Engine doesn't receive an HTTPS 200 response from the
|
|
instance by the time specified by the value of this flag, the health
|
|
check request is considered a failure. For example, specifying 10s will
|
|
cause the check to wait for 10 seconds before considering the request a
|
|
failure. The default value is 5s. See $ gcloud topic datetimes for
|
|
information on duration formats.
|
|
|
|
--unhealthy-threshold=UNHEALTHY_THRESHOLD; default=2
|
|
The number of consecutive health check failures before a healthy
|
|
instance is marked as unhealthy. The default is 2.
|
|
|
|
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 help for details.
|
|
|
|
NOTES
|
|
These variants are also available:
|
|
|
|
$ gcloud alpha compute https-health-checks create
|
|
|
|
$ gcloud beta compute https-health-checks create
|
|
|