From 695bb7ffcf90fc9455152dadd2a504bc4499e3b3 Mon Sep 17 00:00:00 2001 From: Tim Gross Date: Fri, 15 Mar 2024 08:44:58 -0400 Subject: [PATCH] docs: improve wording around autoconfiguration via Consul (#20139) Fixes: https://github.com/hashicorp/nomad/issues/20132 --- website/content/docs/configuration/consul.mdx | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/website/content/docs/configuration/consul.mdx b/website/content/docs/configuration/consul.mdx index e67a72670f7..fd5e05df90d 100644 --- a/website/content/docs/configuration/consul.mdx +++ b/website/content/docs/configuration/consul.mdx @@ -28,9 +28,10 @@ consul { A default `consul` block is automatically merged with all Nomad agent configurations. These sensible defaults automatically enable Consul integration if Consul is detected on the system. This allows for seamless bootstrapping of -the cluster with zero configuration. To put it another way: if you have a -Consul agent running on the same host as the Nomad agent with the default -configuration, Nomad will automatically connect and configure with Consul. +the cluster with zero configuration. To put it another way: if you have a Consul +agent running on the same host as the Nomad agent with the default +configuration, Nomad will be able to automatically connect to the rest of the +Nomad cluster. If the local Consul agent is configured and accessible by the Nomad agents, the Nomad cluster will [automatically bootstrap][bootstrap] provided @@ -157,13 +158,13 @@ agents with [`client.enabled`][] set to `true`. agents. Will default to the `CONSUL_GRPC_CACERT` environment variable if set. - + Consul does not support incoming TLS verification of Envoy sidecars. You should set `tls.grpc.verify_incoming = false` in your - Consul configuration when using Connect. See + Consul configuration when using Connect. See [Consul/#13088](https://github.com/hashicorp/consul/issues/13088) for more details. - + - `share_ssl` `(bool: true)` - Specifies whether the Nomad client should share