From 2448a34a2b38905f394ca33be2ac864bddffd1bd Mon Sep 17 00:00:00 2001 From: Jeff Escalante Date: Tue, 18 Aug 2020 18:57:52 -0400 Subject: [PATCH] more link fixes --- .../docs/connect/gateways/wan-federation-via-mesh-gateways.mdx | 2 +- website/pages/docs/k8s/helm.mdx | 2 +- .../docs/k8s/installation/multi-cluster/vms-and-kubernetes.mdx | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/website/pages/docs/connect/gateways/wan-federation-via-mesh-gateways.mdx b/website/pages/docs/connect/gateways/wan-federation-via-mesh-gateways.mdx index 44154cc0a3..1883f5b818 100644 --- a/website/pages/docs/connect/gateways/wan-federation-via-mesh-gateways.mdx +++ b/website/pages/docs/connect/gateways/wan-federation-via-mesh-gateways.mdx @@ -37,7 +37,7 @@ Sometimes this prerequisite is difficult or undesirable to meet: Operators looking to simplify their WAN deployment and minimize the exposed 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 diff --git a/website/pages/docs/k8s/helm.mdx b/website/pages/docs/k8s/helm.mdx index d485695a0d..e181a18429 100644 --- a/website/pages/docs/k8s/helm.mdx +++ b/website/pages/docs/k8s/helm.mdx @@ -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`, 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. - 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. - `httpsOnly` ((#v-global-httpsonly)) (`boolean: true`) - If true, the Helm chart will configure Consul diff --git a/website/pages/docs/k8s/installation/multi-cluster/vms-and-kubernetes.mdx b/website/pages/docs/k8s/installation/multi-cluster/vms-and-kubernetes.mdx index f1ac428c06..b38029ad5f 100644 --- a/website/pages/docs/k8s/installation/multi-cluster/vms-and-kubernetes.mdx +++ b/website/pages/docs/k8s/installation/multi-cluster/vms-and-kubernetes.mdx @@ -179,7 +179,7 @@ construct the [Federation Secret](#federation-secret) in order to federate Kubernetes clusters as secondaries. -> 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: