luxolus/open-vault
2
0
Fork 0
Code Issues 1 Pull requests Releases Activity

Vault documentation: fixed broken links (#13553)

Browse source 
* fixed broken links

* Update ha.mdx

removed extra slash
This commit is contained in:
Loann Le 2022-01-03 13:53:10 -08:00 committed by GitHub
parent 504a8efd01
commit e5999bba62
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
website/content/docs/concepts/ha.mdx
View file

@ -92,7 +92,7 @@ the value can also be specified by the `VAULT_API_ADDR` environment variable,
which takes precedence. which takes precedence.
What the [`api_addr`](/docs/configuration#api_addr) value should be set to What the [`api_addr`](/docs/configuration#api_addr) value should be set to
depends on how Vault is set up. There are two common scenarios: Vault servers depends on how Vault is set up. There are two common scenarios: Vault servers
accessed directly by clients, and Vault servers accessed via a load balancer. accessed directly by clients, and Vault servers accessed via a load balancer.
In both cases, the [`api_addr`](/docs/configuration#api_addr) should be a full In both cases, the [`api_addr`](/docs/configuration#api_addr) should be a full
@ -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 [`api_addr`](/docs/configuration#api_addr) for each node should be that node's
address. For instance, if there are two Vault nodes: address. For instance, if there are two Vault nodes:
* `A`, accessed via `https://a.vault.mycompany.com:8200` - `A`, accessed via `https://a.vault.mycompany.com:8200`
* `B`, accessed via `https://b.vault.mycompany.com:8200` - `B`, accessed via `https://b.vault.mycompany.com:8200`
Then node `A` would set its Then node `A` would set its
[`api_addr`](/docs/configuration#api_addr) to [`api_addr`](/docs/configuration#api_addr) to
@ -169,12 +169,12 @@ variable, which takes precedence.
## Storage Support ## Storage Support
Currently there are several storage backends that support high availability Currently there are several storage backends that support high availability
mode, including [Consul](/docs/storage/consul), mode, including [Consul](/docs/configuration/storage/consul),
[ZooKeeper](/docs/storage/zookeeper) and [etcd](/docs/storage/etcd). These may [ZooKeeper](/docs/configuration/storage/zookeeper) and [etcd](/docs/configuration/storage/etcd). These may
change over time, and the [configuration page](/docs/configuration) should be change over time, and the [configuration page](/docs/configuration) should be
referenced. 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. by HashiCorp and its customers with commercial support.
If you're interested in implementing another backend or adding HA support to If you're interested in implementing another backend or adding HA support to