diff --git a/website/pages/docs/k8s/connect/connect-ca-provider.mdx b/website/pages/docs/k8s/connect/connect-ca-provider.mdx index 36a3e1ede..edecadc15 100644 --- a/website/pages/docs/k8s/connect/connect-ca-provider.mdx +++ b/website/pages/docs/k8s/connect/connect-ca-provider.mdx @@ -101,7 +101,7 @@ connectInject: enabled: true ``` -Finally, [install](/docs/k8s/installation#installing-consul) the Helm chart using the above config file: +Finally, [install](/docs/k8s/installation/install#installing-consul) the Helm chart using the above config file: ```shell-session $ helm install consul -f config.yaml hashicorp/consul diff --git a/website/pages/docs/k8s/connect/index.mdx b/website/pages/docs/k8s/connect/index.mdx index 802b92851..9f2ad33d4 100644 --- a/website/pages/docs/k8s/connect/index.mdx +++ b/website/pages/docs/k8s/connect/index.mdx @@ -21,7 +21,7 @@ your cluster, making configuration for Kubernetes automatic. This functionality is provided by the [consul-k8s project](https://github.com/hashicorp/consul-k8s) and can be automatically installed and configured using the -[Consul Helm chart](/docs/k8s/installation). +[Consul Helm chart](/docs/k8s/installation/install). ## Usage @@ -332,7 +332,7 @@ provided by the [consul-k8s project](https://github.com/hashicorp/consul-k8s). This enables the automatic pod mutation shown in the usage section above. Installation of the mutating admission webhook is automated using the -[Helm chart](/docs/k8s/installation). +[Helm chart](/docs/k8s/installation/install). To install the Connect injector, enable the Connect injection feature using [Helm values](/docs/k8s/helm#configuration-values) and diff --git a/website/pages/docs/k8s/connect/ingress-gateways.mdx b/website/pages/docs/k8s/connect/ingress-gateways.mdx index a310d203f..abf1da71d 100644 --- a/website/pages/docs/k8s/connect/ingress-gateways.mdx +++ b/website/pages/docs/k8s/connect/ingress-gateways.mdx @@ -57,7 +57,7 @@ in the `ports` object for each gateway. By default ports 8080 and 8443 are expos ## Deploying the helm chart Ensure you have the latest consul-helm chart and install Consul via helm using the following -[guide](/docs/k8s/installation#installing-consul) while being sure to provide the yaml configuration +[guide](/docs/k8s/installation/install#installing-consul) while being sure to provide the yaml configuration as previously discussed. ## Configuring the gateway diff --git a/website/pages/docs/k8s/connect/terminating-gateways.mdx b/website/pages/docs/k8s/connect/terminating-gateways.mdx index 6e5d1c0a3..473ced318 100644 --- a/website/pages/docs/k8s/connect/terminating-gateways.mdx +++ b/website/pages/docs/k8s/connect/terminating-gateways.mdx @@ -42,7 +42,7 @@ terminatingGateways: ## Deploying the helm chart Ensure you have the latest consul-helm chart and install Consul via helm using the following -[guide](/docs/k8s/installation#installing-consul) while being sure to provide the yaml configuration +[guide](/docs/k8s/installation/install#installing-consul) while being sure to provide the yaml configuration as previously discussed. ## Accessing the Consul agent diff --git a/website/pages/docs/k8s/installation/install.mdx b/website/pages/docs/k8s/installation/install.mdx index db8c79649..d1998f81b 100644 --- a/website/pages/docs/k8s/installation/install.mdx +++ b/website/pages/docs/k8s/installation/install.mdx @@ -18,7 +18,7 @@ a server running inside or outside of Kubernetes. This page starts with a large how-to section for various specific tasks. To learn more about the general architecture of Consul on Kubernetes, scroll -down to the [architecture](/docs/k8s/installation#architecture) section. +down to the [architecture](/docs/k8s/installation/install#architecture) section. If you would like to get hands-on experience testing Consul as a service mesh for Kubernetes, check the guides in the [Getting Started with Consul service mesh](https://learn.hashicorp.com/consul/gs-consul-service-mesh/understand-consul-service-mesh?utm_source=WEBSITE&utm_medium=WEB_IO&utm_offer=ARTICLE_PAGE&utm_content=DOCS) track. @@ -185,7 +185,7 @@ has important caching behavior, and allows you to use the simpler [`/agent` endpoints for services and checks](/api/agent). For Consul installed via the Helm chart, a client agent is installed on -each Kubernetes node. This is explained in the [architecture](/docs/k8s/installation#client-agents) +each Kubernetes node. This is explained in the [architecture](/docs/k8s/installation/install#client-agents) section. To access the agent, you may use the [downward API](https://kubernetes.io/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/). @@ -297,7 +297,7 @@ The clients expose the Consul HTTP API via a static port (default 8500) bound to the host port. This enables all other pods on the node to connect to the node-local agent using the host IP that can be retrieved via the Kubernetes downward API. See -[accessing the Consul HTTP API](/docs/k8s/installation#accessing-the-consul-http-api) +[accessing the Consul HTTP API](/docs/k8s/installation/install#accessing-the-consul-http-api) for an example. There is a major limitation to this: there is no way to bind to a local-only diff --git a/website/pages/docs/k8s/installation/multi-cluster/kubernetes.mdx b/website/pages/docs/k8s/installation/multi-cluster/kubernetes.mdx index 713570970..dde7c78f7 100644 --- a/website/pages/docs/k8s/installation/multi-cluster/kubernetes.mdx +++ b/website/pages/docs/k8s/installation/multi-cluster/kubernetes.mdx @@ -113,7 +113,7 @@ Modifications: mesh gateway, for example using a Node Port service or a custom DNS entry, see the [Helm reference](/docs/k8s/helm#v-meshgateway) for that setting. -With your `config.yaml` ready to go, follow our [Installation Guide](/docs/k8s/installation) +With your `config.yaml` ready to go, follow our [Installation Guide](/docs/k8s/installation/install) to install Consul on your primary cluster and then skip ahead to the [Federation Secret](#federation-secret) section. @@ -337,7 +337,7 @@ Modifications: mesh gateway, for example using a Node Port service or a custom DNS entry, see the [Helm reference](/docs/k8s/helm#v-meshgateway) for that setting. -With your `config.yaml` ready to go, follow our [Installation Guide](/docs/k8s/installation) +With your `config.yaml` ready to go, follow our [Installation Guide](/docs/k8s/installation/install) to install Consul on your secondary cluster(s). ## Verifying Federation @@ -375,7 +375,7 @@ You can switch kubectl contexts and run the same command in `dc2` with the flag ### Consul UI We can also use the Consul UI to verify federation. -See [Viewing the Consul UI](/docs/k8s/installation#viewing-the-consul-ui) +See [Viewing the Consul UI](/docs/k8s/installation/install#viewing-the-consul-ui) for instructions on how to view the UI. ~> NOTE: If ACLs are enabled, your kubectl context must be in the primary datacenter diff --git a/website/pages/docs/k8s/installation/platforms/self-hosted-kubernetes.mdx b/website/pages/docs/k8s/installation/platforms/self-hosted-kubernetes.mdx index 6914ca0e9..afe59bcad 100644 --- a/website/pages/docs/k8s/installation/platforms/self-hosted-kubernetes.mdx +++ b/website/pages/docs/k8s/installation/platforms/self-hosted-kubernetes.mdx @@ -9,7 +9,7 @@ description: Installing Consul on Self Hosted Kubernetes Except for creating persistent volumes (see below), installing Consul on your self-hosted Kubernetes cluster is the same process as installing Consul on a -cloud-hosted Kubernetes cluster. See the [Installation Overview](/docs/k8s/installation) +cloud-hosted Kubernetes cluster. See the [Installation Overview](/docs/k8s/installation/install) for install instructions. ## Predefined Persistent Volume Claims (PVCs) diff --git a/website/pages/docs/k8s/service-sync.mdx b/website/pages/docs/k8s/service-sync.mdx index 4e474530d..46ab6a8d9 100644 --- a/website/pages/docs/k8s/service-sync.mdx +++ b/website/pages/docs/k8s/service-sync.mdx @@ -15,7 +15,7 @@ services are available to Consul agents and services in Consul can be available as first-class Kubernetes services. This functionality is provided by the [consul-k8s project](https://github.com/hashicorp/consul-k8s) and can be automatically installed and configured using the -[Consul Helm chart](/docs/k8s/installation). +[Consul Helm chart](/docs/k8s/installation/install). **Why sync Kubernetes services to Consul?** Kubernetes services synced to the Consul catalog enable Kubernetes services to be accessed by any node that