website: highlight how to use agent certs for tls checks (#5086)

Also clarifies that HTTP and gRPC checks both use the same
TLS configuration.
This commit is contained in:
Jack Pearkes 2018-12-18 16:47:52 -08:00 committed by GitHub
parent 03d7406fa5
commit 1237bf5d11
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 7 additions and 1 deletions

View File

@ -328,6 +328,12 @@ In the above configuration, if the web-app health check begins failing, it will
only affect the availability of the web-app service. All other services
provided by the node will remain unchanged.
## Agent Certificates for TLS Checks
The [enable_agent_tls_for_checks](/docs/agent/options.html#enable_agent_tls_for_checks)
agent configuration option can be utilized to have HTTP or gRPC health checks
to use the agent's credentials when configured for TLS.
## Multiple Check Definitions
Multiple check definitions can be defined using the `checks` (plural)

View File

@ -1032,7 +1032,7 @@ default will automatically work with some tooling.
* <a name="enable_agent_tls_for_checks"></a><a href="#enable_agent_tls_for_checks">`enable_agent_tls_for_checks`</a>
When set, uses a subset of the agent's TLS configuration (`key_file`, `cert_file`, `ca_file`, `ca_path`, and
`server_name`) to set up the HTTP client for HTTP health checks. This allows services requiring 2-way TLS to
`server_name`) to set up the client for HTTP or gRPC health checks. This allows services requiring 2-way TLS to
be checked using the agent's credentials. This was added in Consul 1.0.1 and defaults to false.
* <a name="enable_debug"></a><a href="#enable_debug">`enable_debug`</a> When set, enables some