Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport of Vault documentation: fixed broken links into stable-website #13554

Merged
merged 2 commits into from
Jan 3, 2022
Merged

Backport of Vault documentation: fixed broken links into stable-website #13554

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d7025cf
backport of commit a9b1cc183ba12c2ef861466d4beb34c78adf832b
taoism4504 Jan 3, 2022
b321192
backport of commit 47487f7d734b8001283aa38fb5ebbd4c79331e53
taoism4504 Jan 3, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions website/content/docs/concepts/ha.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,7 +92,7 @@ the value can also be specified by the `VAULT_API_ADDR` environment variable,
which takes precedence.

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.

In both cases, the [`api_addr`](/docs/configuration#api_addr) should be a full
Expand All @@ -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
Expand Down Expand Up @@ -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
Expand Down