Fixed broken install links (#8674)
This commit is contained in:
Derek Strickland
GitHub
parent
51f048b21c
commit
86bf775b69
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -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)
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
|
|
|||
Loading…
Reference in New Issue