From a9b1cc183ba12c2ef861466d4beb34c78adf832b Mon Sep 17 00:00:00 2001 From: taoism4504 Date: Mon, 3 Jan 2022 13:16:17 -0800 Subject: [PATCH 1/2] fixed broken links --- website/content/docs/concepts/ha.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/website/content/docs/concepts/ha.mdx b/website/content/docs/concepts/ha.mdx index 6d7fd93bb603..d6456deb4ba8 100644 --- a/website/content/docs/concepts/ha.mdx +++ b/website/content/docs/concepts/ha.mdx @@ -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 @@ -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 From 47487f7d734b8001283aa38fb5ebbd4c79331e53 Mon Sep 17 00:00:00 2001 From: Loann Le <84412881+taoism4504@users.noreply.github.com> Date: Mon, 3 Jan 2022 13:35:54 -0800 Subject: [PATCH 2/2] Update ha.mdx removed extra slash --- website/content/docs/concepts/ha.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/concepts/ha.mdx b/website/content/docs/concepts/ha.mdx index d6456deb4ba8..10c83d7462e2 100644 --- a/website/content/docs/concepts/ha.mdx +++ b/website/content/docs/concepts/ha.mdx @@ -170,7 +170,7 @@ variable, which takes precedence. Currently there are several storage backends that support high availability mode, including [Consul](/docs/configuration/storage/consul), -[ZooKeeper](/docs/configuration/storage/zookeeper) and [etcd](/docs//configuration/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 referenced.