4.8.0 PCP-5531 updating host and workload clusters for MAAS LXD (#8722)

* pcp-5322: placeholder start

* pcp-5322: minor adjustments

* pcp-5531: update path for lxd host cluster

* deleting cloudstack updates from this branch

* ci: auto-formatting prettier issues

* Update docs/docs-content/clusters/data-center/maas/create-manage-maas-lxd-clusters.md

Co-authored-by: Amanda Churi Filanowski <[email protected]>

* Update docs/docs-content/clusters/data-center/maas/create-manage-maas-lxd-clusters.md

Co-authored-by: Amanda Churi Filanowski <[email protected]>

* ci: auto-formatting prettier issues

---------

Co-authored-by: Amanda Churi Filanowski <[email protected]>

Author: Linus-SpectroCloud

docs/docs-content/clusters/data-center/maas/create-manage-maas-lxd-clusters.md

@@ -231,11 +231,11 @@ changing the CPU or memory requirements, or picking a different availability zon
 a rolling repave of the cluster nodes. To learn more about managing a MAAS cluster, refer to
 [Manage Clusters](../../cluster-management/cluster-updates.md).
 
-:::danger
-
-Host cluster updates can cause critical disruptions in the workload clusters and should not be performed.
-
-:::
+Updating the host cluster causes a rolling repave across nodes. During the repave, nodes running older versions are
+removed, and the associated LXD VMs are deleted. If the leader node is deleted, the control plane components of the
+workload cluster undergo a new leader election process and choose a new leader on an LXD VM running on a different node.
+For this reason, it is _critical_ that the host and workload clusters are configured for high availability, consisting
+of at least three nodes per cluster, with the nodes spread across different availability zones.
 
 Workload cluster updates function the same as regular MAAS clusters. Instead of provisioning new bare-metal hosts, new
 LXD VMs are created for the control plane nodes.