Update YBA HA pre-reqs (#23865)

* Update high-availability.md * Update high-availability.md * Update high-availability.md * minor edits --------- Co-authored-by: Dwight Hodge <ghodge@yugabyte.com>
yugabyte · Sep 13, 2024 · 48e3c40 · 48e3c40
1 parent b98984a
commit 48e3c40
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 0 deletions.
diff --git a/...ent/preview/yugabyte-platform/administer-yugabyte-platform/high-availability.md b/...ent/preview/yugabyte-platform/administer-yugabyte-platform/high-availability.md
@@ -38,6 +38,8 @@ Before configuring a HA cluster for your YBA instances, ensure that you have the
 - [Two or more YBA instances](../../install-yugabyte-platform/) to be used in the HA cluster.
 - The YBA instances can connect to each other over the port where the YBA UI is reachable (443 by default).
 - Communication is open in both directions over port 443 and 9090 on all YBA instances.
+- The YBA instances were installed using the same installation method (YBA Installer, Replicated, or Helm (Kubernetes)).
+- The YBA instances are configured to use the same path for the installation root.
 - If you are using custom ports for Prometheus, all YBA instances are using the same custom port. (The default Prometheus port for YugabyteDB Anywhere is 9090.)
 - All YBA instances are running the same version of YBA software. (The YBA instances in a HA cluster should always be upgraded at approximately the same time.)
 - The YBA instances have the same login credentials.

diff --git a/...tent/stable/yugabyte-platform/administer-yugabyte-platform/high-availability.md b/...tent/stable/yugabyte-platform/administer-yugabyte-platform/high-availability.md
@@ -35,6 +35,8 @@ Before configuring a HA cluster for your YBA instances, ensure that you have the
 - [Two or more YBA instances](../../install-yugabyte-platform/) to be used in the HA cluster.
 - The YBA instances can connect to each other over the port where the YBA UI is reachable (443 by default).
 - Communication is open in both directions over port 443 and 9090 on all YBA instances.
+- The YBA instances were installed using the same installation method (YBA Installer, Replicated, or Helm (Kubernetes)).
+- The YBA instances are configured to use the same path for the installation root.
 - If you are using custom ports for Prometheus, all YBA instances are using the same custom port. (The default Prometheus port for YugabyteDB Anywhere is 9090.)
 - All YBA instances are running the same version of YBA software. (The YBA instances in a HA cluster should always be upgraded at approximately the same time.)
 - The YBA instances have the same login credentials.

diff --git a/...ntent/v2.20/yugabyte-platform/administer-yugabyte-platform/high-availability.md b/...ntent/v2.20/yugabyte-platform/administer-yugabyte-platform/high-availability.md
@@ -30,6 +30,8 @@ Before configuring a HA cluster for your YBA instances, ensure that you have the
 - [Multiple YBA instances](../../install-yugabyte-platform/) to be used in the HA cluster.
 - The YBA instances can connect to each other over the port where the YBA UI is reachable (typically 443).
 - Communication is open in both directions over ports 9000 and 9090 on all YBA instances.
+- The YBA instances were installed using the same installation method (YBA Installer, Replicated, or Helm (Kubernetes)).
+- The YBA instances are configured to use the same path for the installation root.
 - If you are using custom ports for Prometheus, all YBA instances are using the same custom port. The default Prometheus port for YugabyteDB Anywhere is 9090.
 - All YBA instances are running the same version of YBA software. (The YBA instances in a HA cluster should always be upgraded at approximately the same time.)