edit ha diagram description

Author: paigecalvert

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

@@ -4,6 +4,11 @@ The following diagram shows the architecture of an HA multi-node Embedded Cluste
 
 [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.
+As shown in the diagram above, in HA installations with Embedded Cluster:
+* A single replica of the Embedded Cluster Operator is deployed and runs on a controller node.
+* A single replica of the KOTS Admin Console is deployed and runs on a controller node.
+* Three replicas of rqlite are deployed in the kotsadm namespace. 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 with disaster recovery, the Velero pod is deployed on one node and the Velero node-agent is deployed on all nodes.
+* For air gap installations, two replicas of the air gap image registry are deployed.
+
+Any Helm [`extensions`](/reference/embedded-config#extensions) that you include in the Embedded Cluster Config are installed in the cluster depending on the given chart and whether or not it is configured to be deployed with high availability.