more link fixes

This commit is contained in:
Jeff Escalante 2020-08-18 18:57:52 -04:00
parent b44a36ce01
commit 2448a34a2b
No known key found for this signature in database
GPG Key ID: 32D23C61AB5450DB
3 changed files with 3 additions and 3 deletions

View File

@ -37,7 +37,7 @@ Sometimes this prerequisite is difficult or undesirable to meet:
Operators looking to simplify their WAN deployment and minimize the exposed Operators looking to simplify their WAN deployment and minimize the exposed
security surface area can elect to join these datacenters together using [mesh security surface area can elect to join these datacenters together using [mesh
gateways](/docs/connect/mesh-gateways.html) to do so. gateways](/docs/connect/mesh-gateways) to do so.
## Architecture ## Architecture

View File

@ -148,7 +148,7 @@ and consider if they're appropriate for your deployment.
- `verify` ((#v-global-verify)) (`boolean: true`) - If true, `verify_outgoing`, `verify_server_hostname`, - `verify` ((#v-global-verify)) (`boolean: true`) - If true, `verify_outgoing`, `verify_server_hostname`,
and `verify_incoming_rpc` will be set to `true` for Consul servers and clients. and `verify_incoming_rpc` will be set to `true` for Consul servers and clients.
Set this to false to incrementally roll out TLS on an existing Consul cluster. Set this to false to incrementally roll out TLS on an existing Consul cluster.
Please see [Configuring TLS on an Existing Cluster](/docs/k8s/tls-on-existing-cluster) Please see [Configuring TLS on an Existing Cluster](/docs/k8s/operations/tls-on-existing-cluster)
for more details. for more details.
- `httpsOnly` ((#v-global-httpsonly)) (`boolean: true`) - If true, the Helm chart will configure Consul - `httpsOnly` ((#v-global-httpsonly)) (`boolean: true`) - If true, the Helm chart will configure Consul

View File

@ -179,7 +179,7 @@ construct the [Federation Secret](#federation-secret) in order to federate
Kubernetes clusters as secondaries. Kubernetes clusters as secondaries.
-> Your VM cluster must be running mesh gateways, and have mesh gateway WAN -> Your VM cluster must be running mesh gateways, and have mesh gateway WAN
federation enabled. See [WAN Federation via Mesh Gateways](/docs/connect/wan-federation-via-mesh-gateways). federation enabled. See [WAN Federation via Mesh Gateways](/docs/connect/gateways/wan-federation-via-mesh-gateways).
You'll need: You'll need: