Vault documentation: fixed broken links (#13553)
* fixed broken links * Update ha.mdx removed extra slash
This commit is contained in:
parent
504a8efd01
commit
e5999bba62
|
@ -104,8 +104,8 @@ When clients are able to access Vault directly, the
|
|||
[`api_addr`](/docs/configuration#api_addr) for each node should be that node's
|
||||
address. For instance, if there are two Vault nodes:
|
||||
|
||||
* `A`, accessed via `https://a.vault.mycompany.com:8200`
|
||||
* `B`, accessed via `https://b.vault.mycompany.com:8200`
|
||||
- `A`, accessed via `https://a.vault.mycompany.com:8200`
|
||||
- `B`, accessed via `https://b.vault.mycompany.com:8200`
|
||||
|
||||
Then node `A` would set its
|
||||
[`api_addr`](/docs/configuration#api_addr) to
|
||||
|
@ -169,12 +169,12 @@ variable, which takes precedence.
|
|||
## Storage Support
|
||||
|
||||
Currently there are several storage backends that support high availability
|
||||
mode, including [Consul](/docs/storage/consul),
|
||||
[ZooKeeper](/docs/storage/zookeeper) and [etcd](/docs/storage/etcd). These may
|
||||
mode, including [Consul](/docs/configuration/storage/consul),
|
||||
[ZooKeeper](/docs/configuration/storage/zookeeper) and [etcd](/docs/configuration/storage/etcd). These may
|
||||
change over time, and the [configuration page](/docs/configuration) should be
|
||||
referenced.
|
||||
|
||||
The [Consul backend](/docs/storage/consul) is the recommended HA backend, as it is used in production
|
||||
The [Consul backend](/docs/configuration/storage/consul) is the recommended HA backend, as it is used in production
|
||||
by HashiCorp and its customers with commercial support.
|
||||
|
||||
If you're interested in implementing another backend or adding HA support to
|
||||
|
|
Loading…
Reference in New Issue