diff --git a/website/source/guides/operations/deployment-guide.html.md b/website/source/guides/operations/deployment-guide.html.md
index 87cdfb0684..f521d9463e 100644
--- a/website/source/guides/operations/deployment-guide.html.md
+++ b/website/source/guides/operations/deployment-guide.html.md
@@ -6,7 +6,7 @@ description: |-
   This deployment guide covers the steps required to install and
   configure a single HashiCorp Vault cluster as defined in the
   Vault Reference Architecture
-product_version: 0.11
+product_version: 1.0
 ---
 
 # Vault Deployment Guide
@@ -264,6 +264,20 @@ The `telemetry` stanza specifies various configurations for Vault to publish met
 
 If you decide to configure Vault to publish telemtery data, you should review the [telemetry configuration section](/docs/configuration/telemetry.html) of our documentation.
 
+### High Availability Parameters
+
+The `api_addr` parameter configures the API address used in high availability scenarios, when client redirection is used instead of request forwarding. Client redirection is the fallback method used when request forwarding is turned off or there is an error performing the forwarding. As such, a redirect address is always required for all HA setups.
+
+This parameter value defaults to the `address` specified in the `listener` stanza, but Vault will log a `[WARN]` message if it is not explicitly configured.
+
+Add the below configuration to the Vault configuration file:
+
+```hcl
+api_addr = "{{ full URL to Vault API endpoint }}"
+```
+
+[More information about high availability configuration](/docs/configuration/#high-availability-parameters).
+
 ### Vault UI
 
 Vault features a web-based user interface, allowing you to easily create, read, update, and delete secrets, authenticate, unseal, and more using a graphical user interface, rather than the CLI or API.