add ha arch to partial

Author: paigecalvert

docs/enterprise/embedded-manage-nodes.mdx

@@ -1,3 +1,5 @@
+import HaArchitecture from "../partials/embedded-cluster/_multi-node-ha-arch.mdx"
+
 # Managing Multi-Node Clusters with Embedded Cluster
 
 The topic describes managing nodes in clusters created with Replicated Embedded Cluster, including how to add nodes and enable high-availability for multi-node clusters.
@@ -87,6 +89,12 @@ Multi-node clusters are not highly available by default. The first node of the c
 High availability for Embedded Cluster in an Alpha feature. This feature is subject to change, including breaking changes. To get access to this feature, reach out to Alex Parker at [[email protected]](mailto:[email protected]).
 :::
 
+### HA Architecture
+
+<HaArchitecture/>
+
+For more information about the Embedded Cluster built-in extensions, see [Built-In Extensions](/vendor/embedded-overview#built-in-extensions) in _Embedded Cluster Overview_.
+
 ### Requirements
 
 Enabling high availability has the following requirements:

docs/partials/embedded-cluster/_multi-node-ha-arch.mdx

@@ -0,0 +1,9 @@
+The following diagram shows the architecture of an HA multi-node Embedded Cluster installation:
+
+![Embedded Cluster multi-node architecture](/images/embedded-architecture-multi-node-ha.png)
+
+[View a larger version of this image](/images/embedded-architecture-multi-node-ha.png)
+
+In HA multi-node installations, the Embedded Cluster Operator and the KOTS Admin Console are installed on the primary node only. All other built-in extenions, including the image registry for air gap installations, are installed on each node in the cluster. Any Helm [`extensions`](/reference/embedded-config#extensions) that you include in the Embedded Cluster Config can optionally be installed on one or more nodes. 
+
+Additionally, three replicas of rqlite are deployed for HA. Rqlite is used by KOTS to store information such as support bundles, version history, application metadata, and other small amounts of data needed to manage the application.

docs/vendor/embedded-overview.mdx

@@ -1,6 +1,7 @@
 import EmbeddedCluster from "../partials/embedded-cluster/_definition.mdx"
 import Requirements from "../partials/embedded-cluster/_requirements.mdx"
 import EmbeddedClusterPortRequirements from "../partials/embedded-cluster/_port-reqs.mdx"
+import HaArchitecture from "../partials/embedded-cluster/_multi-node-ha-arch.mdx"
 
 # Embedded Cluster Overview
 
@@ -44,29 +45,19 @@ The following diagram shows the architecture of a multi-node Embedded Cluster in
 
 [View a larger version of this image](/images/embedded-architecture-multi-node.png)
 
-As shown in the diagram above, in multi-node installations, the Embedded Cluster Operator, KOTS (including rqlite), and the image registry for air gap installations are all installed on the primary node only.
+As shown in the diagram above, in multi-node installations, the Embedded Cluster Operator, KOTS, and the image registry for air gap installations are all installed on the primary node only.
 
 For installations that include disaster recovery with Velero, the Velero Node Agent runs on each node in the cluster. The Node Agent is a Kubernetes DaemonSet that performs backup and restore tasks such as creating snapshots and transferring data during restores.
 
-Any Helm [`extensions`](/reference/embedded-config#extensions) included in the Embedded Cluster Config can be installed on one or more nodes. 
+Additionally, any Helm [`extensions`](/reference/embedded-config#extensions) that you include in the Embedded Cluster Config can optionally be installed on one or more nodes. 
 
 ### Multi-Node Architecture with High Availability
 
 :::note
 High availability (HA) for multi-node installations with Embedded Cluster is Alpha and is not enabled by default. For more informaiton about enabling HA, see [Enable High Availability for Multi-Node Clusters (Alpha)](/enterprise/embedded-manage-nodes#ha).
 :::
 
-The following diagram shows the architecture of an HA multi-node Embedded Cluster installation:
-
-![Embedded Cluster multi-node architecture](/images/embedded-architecture-multi-node-ha.png)
-
-[View a larger version of this image](/images/embedded-architecture-multi-node-ha.png)
-
-In HA multi-node installations, the Embedded Cluster Operator and the KOTS Admin Console are installed on the primary node only. All other built-in extenions, including the image registry for air gap installations, are installed on each node in the cluster.
-
-Additionally, three replicas of rqlite are deployed for HA. Rqlite is used by KOTS to store information such as support bundles, version history, application metadata, and other small amounts of data needed to manage the application.
-
-For installations that include disaster recovery with Velero, the Velero Node Agent runs on each node in the cluster. The Node Agent is a Kubernetes DaemonSet that performs backup and restore tasks such as creating snapshots and transferring data during restores.
+<HaArchitecture/>
 
 ## Built-In Extensions {#built-in-extensions}