docs: multi-node airgap documentation

docs/docs-content/clusters/edge/local-ui/cluster-management/create-cluster.md

@@ -1,23 +1,25 @@
 ---
 sidebar_label: "Create Local Cluster"
 title: "Create Local Cluster"
-description: "Instructions for creating a locally manageg cluster in Edge Host Management Console."
+description: "Instructions for creating a locally managed cluster in Edge Host Management Console."
 hide_table_of_contents: false
 sidebar_position: 30
 tags: ["edge"]
 ---
 
-You can create and manage a single-node cluster on an airgapped Edge host locally from Local UI. This page guides you
-through how to create a cluster using Local UI.
+You can create and manage single-node as well as multi-node clusters on airgapped hosts locally from Local UI. This page
+guides you through how to create a cluster using Local UI.
 
 :::preview
 
 :::
 
 ## Limitations
 
-- You can only create single-node clusters consisting solely of the Edge host you create the cluster from. You cannot
-  include other Edge hosts in the same local or remote network.
+- For multi-node clusters, all hosts must be deployed in the same deployment mode. For more information, refer to
+  [Deployment Modes](../../../../deployment-modes/deployment-modes.md).
+
+- For multi-node clusters composed of hosts deployed in agent mode, all hosts must share the same Operating System (OS).
 
 ## Prerequisites
 
@@ -29,15 +31,17 @@ through how to create a cluster using Local UI.
   ISO during EdgeForge. For more information, refer to [Upload Content Bundle](./upload-content-bundle.md) and
   [Build Content Bundle](../../edgeforge-workflow/palette-canvos/build-content-bundle.md).
 
-- You must ensure that the Edge host has a stable IP address. You have the following options to achieve a stable IP
-  address:
+- You must ensure your hosts have stable IP addresses. You have the following options to achieve a stable IP address:
 
   - Use a static IP address. Contact your network administrator to assign the Edge host a static IP address.
   - Use Dynamic Host Configuration Protocol (DHCP) reservations to reserve an IP address in a DHCP network. Contact your
     network administrator to reserve IP addresses for your Edge hosts in a DHCP network.
   - Enable network overlay on your Edge cluster. Network overlay can only be enabled during cluster creation. For more
     information about network overlay, refer to [Enable Overlay Network](../../networking/vxlan-overlay.md).
 
+- To create multi-node clusters, all nodes to be included in the cluster must be linked. For more information, refer to
+  [Link Hosts](./link-hosts.md).
+
 ## Create Local Cluster
 
 1. Log into Local UI by visiting the 5080 port of your Edge device's IP address or domain name. For more information,
@@ -84,7 +88,11 @@ through how to create a cluster using Local UI.
    more information, refer to [Enable Overlay Network](../../networking/vxlan-overlay.md). If you enable the overlay
    network, you need to specify a CIDR range to be used by the overlay network.
 
-8. In the **Node Config** step, you can specify configurations for the control plane pool of your single-node cluster.
+8. In the **Node Config** step, you can specify configurations for worker pools and control plane pools. To assign a
+   host to a node pool, click **Add Edge Hosts** in the corresponding node pool and select the host to add to the pool.
+   For multi-node clusters, the leader node is a mandatory control plane node and cannot be unassigned. Additionally,
+   you must ensure that you have an odd number of nodes in the control plane.
+
    For more information about node pool configurations, refer to [Node pools](../../../cluster-management/node-pool.md).
    After you finish configuration, click **Next**.
 
@@ -93,6 +101,6 @@ through how to create a cluster using Local UI.
 
 ## Validate
 
-1. Log in to Local UI.
+1. Log in to [Local UI](../host-management/access-console.md).
 
 2. Click **Cluster**. Verify that your cluster has entered the running status.

docs/docs-content/clusters/edge/local-ui/cluster-management/delete-cluster.md

@@ -0,0 +1,40 @@
+---
+sidebar_label: "Delete a Cluster"
+title: "Delete a Cluster"
+description: "Learn how to delete a cluster with Local UI."
+hide_table_of_contents: false
+sidebar_position: 90
+tags: ["edge"]
+---
+
+You can delete an active cluster using Local UI. Deleting a cluster will free up all the hosts in the cluster for new
+workloads. Deleting a cluster does not unlink the linked hosts. For more information about leader nodes, refer to
+[Link Hosts](./link-hosts.md).
+
+## Prerequisites
+
+- Access to [Local UI](../host-management/access-console.md). Any Operating System (OS) user can be used to log in to
+  Local UI.
+
+- An active cluster deployed and managed by Local UI.
+
+## Delete a Cluster
+
+1. Log in to [Local UI](../host-management/access-console.md) on the leader node where your cluster is deployed.
+
+2. From the left **Main Menu**, click **Cluster**.
+
+3. In the upper-right corner of the **Cluster** page, click **Actions**.
+
+4. In the **drop-down Menu** that appears, click **Delete**.
+
+5. In the pop-up window that appears, click **Confirm**. During the deletion of the cluster, Local UI will become
+   unavailable as the nodes reboot after cluster deletion.
+
+## Validate
+
+1. Log in to [Local UI](../host-management/access-console.md) on the leader of the linked hosts.
+
+2. From the left **Main Menu**, click **Cluster**.
+
+3. Confirm that there is no active cluster and that the cluster has been deleted.

docs/docs-content/clusters/edge/local-ui/cluster-management/link-hosts.md

@@ -0,0 +1,61 @@
+---
+sidebar_label: "Link Hosts"
+title: "Link Hosts"
+description: "Instructions for linking hosts to prepare for multi-node cluster creation."
+hide_table_of_contents: false
+sidebar_position: 50
+tags: ["edge"]
+---
+
+To provision a multi-node cluster with hosts are provisioned in `airgap` installation mode, the hosts must first be able
+identify and securely communicate with each other. By default, hosts that are provisioned in `airgap` installation mode
+are not aware of each other even if they are on the same network, and they do not have the credentials to communicate
+with each other securely.
+
+Host linking provides the hosts with the necessary network and security infrastructure to form a cluster together. In a
+group of linked hosts, hosts can broadcast information to all its peers. Every group has a leader node, which provides
+tokens with its IP and a One-Time Password (OTP) credentials encrypted that you can use to link other nodes.
+
+Linked hosts will sync images for the Palette agent, provider images, cluster definitions, as well as host status with
+each other. In a group of linked hosts that have not formed a cluster, only the leader node has access to functionality
+such as change host settings, upload content, and create clusters. Once a cluster is created, only the control plane
+nodes have access to features such as cluster management and can change host settings.
+
+## Prerequisites
+
+- Two or more hosts deployed in the same deployment mode on the same network. For more information, refer to
+  [Appliance Mode Installation](../../site-deployment/stage.md) or
+  [Agent Mode Installation](../../../../deployment-modes/agent-mode/install-agent-host.md).
+
+## Procedure
+
+1. Decide on a node that you plan to use as the leader of the group. Log in to
+   [Local UI](../host-management/access-console.md) of that node. The leader node may or may not already be in a
+   cluster, but the follower nodes must be idle and cannot be in a cluster.
+
+2. From the left **Main Menu**, click **Linked Edge Hosts**.
+
+3. Click **Generate token**. This will generate a token you will use to link this host with other hosts. The token
+   contains the encrypted IP address of the node, as well as an OTP that will expire in two minutes.
+
+4. Click the **Copy** button to copy the token.
+
+5. Log in to [Local UI](../host-management/access-console.md) on the node that you want to link to the leader node.
+
+6. From the left **Main Menu**, click **Linked Edge Hosts**.
+
+7. Click **Link this device to another**.
+
+8. In the pop-up box that appears, enter the token you coped from the leader node.
+
+9. Click confirm.
+
+10. Repeat this process for every node you want to link to the leader node.
+
+## Validate
+
+1. Log in to [Local UI](../host-management/access-console.md) on the leader node.
+
+2. From the left **Main Menu**, click **Linked Edge Hosts**.
+
+3. Confirm that all nodes you linked together show up in the **Linked Edge Hosts** table.

docs/docs-content/clusters/edge/local-ui/cluster-management/scale-cluster.md

@@ -0,0 +1,92 @@
+---
+sidebar_label: "Scale a Cluster"
+title: "Scale a Cluster"
+description: "Learn how to scale up or scale down a cluster."
+hide_table_of_contents: false
+sidebar_position: 30
+tags: ["edge"]
+---
+
+Once a cluster is operational, you have the option of scaling up the cluster by adding additional nodes, or scale down
+the cluster by removing nodes from the cluster using Local UI.
+
+## Scale up a Cluster
+
+To scale up a cluster is to add additional nodes to an active cluster. You can scale up a cluster deployed on hosts
+installed in airgap mode in Local UI.
+
+### Prerequisites
+
+- You have an active cluster composed of hosts installed in airgap mode. For more information, refer to
+  [Create Local Cluster](./create-cluster.md).
+
+- The new nodes you plan to add to the cluster are linked with the nodes in the existing cluster. For more information,
+  refer to [Link Hosts](./link-hosts.md).
+
+- You have access to the leader node of the cluster. For more information about leader nodes, refer to
+  [Link Hosts](./link-hosts.md).
+
+### Procedure
+
+1. Log in to [Local UI](../host-management/access-console.md) on the leader node where your cluster is deployed.
+
+2. From the left **Main Menu**, click **Cluster**.
+
+3. On the **Cluster** page, click **Nodes** to view the **Nodes** tab.
+
+4. Select a node pool you'd like to edit. You can either edit the control plane or the worker pool.
+
+5. In the pop-up window,scroll down to **Pool Configuration** and click on **Add Item**.
+
+6. Select a host that you'd like to add to the cluster.
+
+7. Click **Confirm** to confirm your changes. It may take 15 to 25 mins for the change to take effect depending on your
+   environment and workload.
+
+### Validate
+
+1. Log in to [Local UI](../host-management/access-console.md) on the leader node where your cluster is deployed.
+
+2. From the left **Main Menu**, click **Cluster**.
+
+3. On the **Cluster** page, click **Nodes** to view the **Nodes** tab.
+
+4. Confirm that the new node you added to the cluster is in the **Running** status.
+
+## Scale down a Cluster
+
+To scale down a cluster is to remove existing nodes from an active cluster. You can scale down a cluster deployed on
+hosts installed in airgap mode in Local UI.
+
+### Prerequisites
+
+- You have an active multi-node cluster composed of hosts installed in airgap mode. For more information, refer to
+  [Create Local Cluster](./create-cluster.md).
+
+- You have access to the leader node of the cluster. For more information about leader nodes, refer to
+  [Link Hosts](./link-hosts.md).
+
+### Procedure
+
+1. Log in to [Local UI](../host-management/access-console.md) on the leader node where your cluster is deployed.
+
+2. From the left **Main Menu**, click **Cluster**.
+
+3. On the **Cluster** page, click **Nodes** to view the **Nodes** tab.
+
+4. Select a node pool you'd like to edit. You can either edit the control plane or the worker pool.
+
+5. In the pop-up window,scroll down to **Pool Configuration**. Click the **Delete** button next to the nodes you want to
+   remove.
+
+6. When you are done removing nodes, Click **Confirm** to confirm your changes. It may take 15 to 25 mins for the change
+   to take effect depending on your environment and workload.
+
+### Validate
+
+1. Log in to [Local UI](../host-management/access-console.md) on the leader node where your cluster is deployed.
+
+2. From the left **Main Menu**, click **Cluster**.
+
+3. On the **Cluster** page, click **Nodes** to view the **Nodes** tab. Confirm that the node you removed is no longer in
+   the cluster.

docs/docs-content/clusters/edge/local-ui/host-management/reset-reboot.md

@@ -48,7 +48,8 @@ Edge host is rebooting.
 You can reset an airgapped Edge host to factory default from Local UI. This restores the Edge host to the state right
 after the [initial configuration](../../site-deployment/site-installation/initial-setup.md) is completed in the Terminal
 User Interface (TUI). Reset to factory default removes all workloads, content, and cluster definition from the Edge
-host. This includes content bundles that were built into the ISO image during EdgeForge.
+host. This includes content bundles that were built into the ISO image during EdgeForge. If your host was
+[linked](../cluster-management/link-hosts.md) with another host, resetting the host will unlink the host.
 
 If your Edge host has a connection to Palette, you cannot reset the Edge host to factory default through Local UI as the
 cluster is managed through Palette.