Merge branch 'main' into automation/vendor-portal-release-notes-v2024.12.06-2

Author: alicenstar

docs/enterprise/embedded-manage-nodes.mdx

@@ -0,0 +1,135 @@
+# 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.
+
+## Limitations
+
+Multi-node clusters with Embedded Cluster have the following limitations:
+
+* Support for multi-node clusters with Embedded Cluster is Beta. Only single-node embedded clusters are Generally Available (GA).
+
+* 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]).
+
+## Add Nodes to a Cluster (Beta) {#add-nodes}
+
+You can add nodes to create a multi-node cluster in online (internet-connected) and air-gapped (limited or no outbound internet access) environments. The Admin Console provides the join command that you use to join nodes to the cluster.
+
+:::note
+Multi-node clusters are not highly available by default. For information about enabling high availability, see [Enable High Availability for Multi-Node Clusters (Alpha)](#ha) below.
+:::
+
+To add nodes to a cluster:
+
+1. (Optional) In the Embedded Cluster Config, configure the `roles` key to customize node roles. For more information, see [roles](/reference/embedded-config#roles) in _Embedded Cluster Config_. When you are done, create and promote a new release with the updated Config.
+
+1. Do one of the following to get the join command from the Admin Console:
+
+   1. To add nodes during the application installation process, follow the steps in [Online Installation with Embedded Cluster](/enterprise/installing-embedded) or [Air Gap Installation with Embedded Cluster](/enterprise/installing-embedded-air-gap) to install. A **Nodes** screen is displayed as part of the installation flow in the Admin Console that allows you to choose a node role and copy the relevant join command.
+
+   1. Otherwise, if you have already installed the application:
+
+         1. Log in to the Admin Console.
+         
+         1. If you promoted a new release that configures the `roles` key in the Embedded Cluster Config, update the instance to the new version. See [Performing Updates in Embedded Clusters](/enterprise/updating-embedded).
+         
+         1. Go to **Cluster Management > Add node** at the top of the page.
+
+            <img alt="Add node page in the Admin Console" src="/images/admin-console-add-node.png" width="600px"/>
+
+            [View a larger version of this image](/images/admin-console-add-node.png)
+   
+1. Either on the Admin Console **Nodes** screen that is displayed during installation or in the **Add a Node** dialog, select one or more roles for the new node that you will join. Copy the join command.
+
+     Note the following:
+
+     * If the Embedded Cluster Config [roles](/reference/embedded-config#roles) key is not configured, all new nodes joined to the cluster are assigned the `controller` role by default. The `controller` role designates nodes that run the Kubernetes control plane. Controller nodes can also run other workloads, such as application or Replicated KOTS workloads.
+
+     * Roles are not updated or changed after a node is added. If you need to change a node’s role, reset the node and add it again with the new role.
+
+     * For multi-node clusters with high availability (HA), at least three `controller` nodes are required. You can assign both the `controller` role and one or more `custom` roles to the same node. For more information about creating HA clusters with Embedded Cluster, see [Enable High Availability for Multi-Node Clusters (Alpha)](#ha) below.
+
+     * To add non-controller or _worker_ nodes that do not run the Kubernetes control plane, select one or more `custom` roles for the node and deselect the `controller` role.
+
+1. Do one of the following to make the Embedded Cluster installation assets available on the machine that you will join to the cluster:
+
+    * **For online (internet-connected) installations**: SSH onto the machine that you will join. Then, use the same commands that you ran during installation to download and untar the Embedded Cluster installation assets on the machine. See [Online Installation with Embedded Cluster](/enterprise/installing-embedded).
+
+    * **For air gap installations with limited or no outbound internet access**: On a machine that has internet access, download the Embedded Cluster installation assets (including the air gap bundle) using the same command that you ran during installation. See [Air Gap Installation with Embedded Cluster](/enterprise/installing-embedded-air-gap). Then, move the downloaded assets to the air-gapped machine that you will join, and untar. 
+
+    :::important
+    The Embedded Cluster installation assets on each node must all be the same version. If you use a different version than what is installed elsewhere in the cluster, the cluster will not be stable. To download a specific version of the Embedded Cluster assets, select a version in the **Embedded cluster install instructions** dialog.
+    :::
+
+1. On the machine that you will join to the cluster, run the join command that you copied from the Admin Console.
+
+    **Example:**
+
+    ```bash
+    sudo ./APP_SLUG join 10.128.0.32:30000 TxXboDstBAamXaPdleSK7Lid
+    ```
+    **Air Gap Example:**
+
+    ```bash
+    sudo ./APP_SLUG join --airgap-bundle APP_SLUG.airgap 10.128.0.32:30000 TxXboDstBAamXaPdleSK7Lid
+    ```
+
+1. In the Admin Console, either on the installation **Nodes** screen or on the **Cluster Management** page, verify that the node appears. Wait for the node's status to change to Ready.
+
+1. Repeat these steps for each node you want to add.    
+
+## Enable High Availability for Multi-Node Clusters (Alpha) {#ha}
+
+Multi-node clusters are not highly available by default. The first node of the cluster is special and holds important data for Kubernetes and KOTS, such that the loss of this node would be catastrophic for the cluster. Enabling high availability (HA) requires that at least three controller nodes are present in the cluster. Users can enable HA when joining the third node.
+
+:::important
+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]).
+:::
+
+### Requirements
+
+Enabling high availability has the following requirements:
+
+* High availability is supported with Embedded Cluster 1.4.1 or later.
+
+* High availability is supported only for clusters where at least three nodes with the `controller` role are present.
+
+### Limitations
+
+Enabling high availability has the following limitations:
+
+* 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]).
+
+* The `--enable-ha` flag serves as a feature flag during the Alpha phase. In the future, the prompt about migrating to high availability will display automatically if the cluster is not yet HA and you are adding the third or more controller node. 
+
+* HA multi-node clusters use rqlite to store support bundles up to 100 MB in size. Bundles over 100 MB can cause rqlite to crash and restart.
+
+### Best Practices for High Availability
+
+Consider the following best practices and recommendations for creating HA clusters:
+
+* At least three _controller_ nodes that run the Kubernetes control plane are required for HA. This is because clusters use a quorum system, in which more than half the nodes must be up and reachable. In clusters with three controller nodes, the Kubernetes control plane can continue to operate if one node fails because a quorum can still be reached by the remaining two nodes. By default, with Embedded Cluster, all new nodes added to a cluster are controller nodes. For information about customizing the `controller` node role, see [roles](/reference/embedded-config#roles) in _Embedded Cluster Config_.
+
+* Always use an odd number of controller nodes in HA clusters. Using an odd number of controller nodes ensures that the cluster can make decisions efficiently with quorum calculations. Clusters with an odd number of controller nodes also avoid split-brain scenarios where the cluster runs as two, independent groups of nodes, resulting in inconsistencies and conflicts.
+
+* You can have any number of _worker_ nodes in HA clusters. Worker nodes do not run the Kubernetes control plane, but can run workloads such as application or Replicated KOTS workloads.
+
+### Create a Multi-Node HA Cluster
+
+To create a multi-node HA cluster:
+
+1. Set up a cluster with at least two controller nodes. You can do an online (internet-connected) or air gap installation. For more information, see [Online Installation with Embedded Cluster](/enterprise/installing-embedded) or [Air Gap Installation with Embedded Cluster](/enterprise/installing-embedded-air-gap).
+
+1. SSH onto a third node that you want to join to the cluster as a controller.
+
+1. Run the join command provided in the Admin Console **Cluster Management** tab and pass the `--enable-ha` flag. For example:
+
+     ```bash
+     sudo ./APP_SLUG join --enable-ha 10.128.0.80:30000 tI13KUWITdIerfdMcWTA4Hpf
+     ```
+
+1. After the third node joins the cluster, type `y` in response to the prompt asking if you want to enable high availability.
+
+    ![high availability command line prompt](/images/embedded-cluster-ha-prompt.png)
+    [View a larger version of this image](/images/embedded-cluster-ha-prompt.png)
+
+1. Wait for the migration to complete.

docs/enterprise/installing-embedded-air-gap.mdx

@@ -123,7 +123,9 @@ To install with Embedded Cluster in an air gap environment:
 
 1. On the login page, enter the Admin Console password that you created during installation and click **Log in**.
 
-1. On the **Configure the cluster** screen, optionally add nodes to the cluster before deploying the application. Click **Continue**.
+1. On the **Nodes** page, you can view details about the machine where you installed, including its node role, status, CPU, and memory. 
+
+     Optionally, add nodes to the cluster before deploying the application. For more information about joining nodes, see [Managing Multi-Node Clusters with Embedded Cluster](/enterprise/embedded-manage-nodes). Click **Continue**.
 
 1. On the **Configure [App Name]** screen, complete the fields for the application configuration options. Click **Continue**.
 
@@ -137,32 +139,4 @@ On the Admin Console dashboard, the application status changes from Missing to U
 
 ![Admin console dashboard showing ready status](/images/gitea-ec-ready.png)
 
-[View a larger version of this image](/images/gitea-ec-ready.png)
-
-## Add Nodes to Air Gap Clusters
-
-You can add nodes to an air gap cluster. This involves downloading the Embedded Cluster assets to each node, copying a join command from the Admin Console, and running the join command on each node.
-
-### Prerequisites
-
-The Embedded Cluster binary and the air gap bundle must be present on each node you want to join to the cluster. Use the same commands as you did during installation to download and untar these assets on each node. For more information, see [Install](#install) above.
-
-:::note
-The binary and air gap bundles on each additional node must be the same version as what is currently installed. To download a specific version of these assets, you can select a version in the **Embedded Cluster install instructions** dialog. For more information, see [Install](#install) above.
-:::
-
-### Add Nodes
-
-To add nodes to a cluster after successfully installing the first node:
-
-1. Click the link in the install output to access the Admin Console. Proceed through the setup steps until you reach the **Nodes** page.
-
-1. Click **Add node**, choose one or more node roles (if present), and copy the join command.
-
-1. SSH onto another machine you want to join to the cluster. Run the join command on this node. For example:
-
-    ```bash
-    sudo ./APP_SLUG join --airgap-bundle APP_SLUG.airgap 10.128.0.32:30000 TxXboDstBAamXaPdleSK7Lid
-    ```
-
-1. When you have finished adding all nodes, return to the Admin Console and click **Continue**.
+[View a larger version of this image](/images/gitea-ec-ready.png)

docs/enterprise/installing-embedded.mdx

@@ -85,7 +85,9 @@ To install an application with Embedded Cluster:
 
 1. On the login page, enter the Admin Console password that you created during installation and click **Log in**.
 
-1. On the **Configure the cluster** screen, optionally add nodes to the cluster before deploying the application. Click **Continue**.
+1. On the **Nodes** page, you can view details about the machine where you installed, including its node role, status, CPU, and memory. 
+
+     Optionally, add nodes to the cluster before deploying the application. For more information about joining nodes, see [Managing Multi-Node Clusters with Embedded Cluster](/enterprise/embedded-manage-nodes). Click **Continue**.
 
 1. On the **Configure [App Name]** screen, complete the fields for the application configuration options. Click **Continue**.
 

docs/intro-replicated.mdx

@@ -27,13 +27,13 @@ The following diagram demonstrates the process of using the Replicated Platform
 
 [View a larger version of this image](/images/replicated-platform.png)
 
-The diagram above shows an application that is packaged with the [**Replicated SDK**](replicated-sdk-overview). The application is tested in clusters provisioned with the [**Replicated Compatibility Matrix**](testing-about), then added to a new release in the [**Vendor Portal**](/vendor/releases-about) using an automated CI/CD pipeline.
+The diagram above shows an application that is packaged with the [**Replicated SDK**](/vendor/replicated-sdk-overview). The application is tested in clusters provisioned with the [**Replicated Compatibility Matrix**](/vendor/testing-about), then added to a new release in the [**Vendor Portal**](/vendor/releases-about) using an automated CI/CD pipeline.
 
 The application is then installed by a customer ("Big Bank") on a VM. To install, the customer downloads their license, which grants proxy access to the application images through the [**Replicated proxy registry**](/vendor/private-images-about). They also download the installation assets for the [**Replicated Embedded Cluster**](/vendor/embedded-overview) installer.
 
-Embedded Cluster runs [**preflight checks**](preflight-support-bundle-about) to verify that the environment meets the installation requirements, provisions a cluster on the VM, and installs [**Replicated KOTS**](intro-kots) in the cluster. KOTS provides an [**Admin Console**](intro-kots#kots-admin-console) where the customer enters application-specific configurations, runs application preflight checks, optionally joins nodes to the cluster, and then deploys the application. After installation, customers can manage both the application and the cluster from the Admin Console.
+Embedded Cluster runs [**preflight checks**](/vendor/preflight-support-bundle-about) to verify that the environment meets the installation requirements, provisions a cluster on the VM, and installs [**Replicated KOTS**](intro-kots) in the cluster. KOTS provides an [**Admin Console**](intro-kots#kots-admin-console) where the customer enters application-specific configurations, runs application preflight checks, optionally joins nodes to the cluster, and then deploys the application. After installation, customers can manage both the application and the cluster from the Admin Console.
 
-Finally, the diagram shows how [**instance data**](instance-insights-event-data) is automatically sent from the customer environment to the Vendor Portal by the Replicated SDK API and the KOTS Admin Console. Additionally, tooling from the open source [**Troubleshoot**](https://troubleshoot.sh/docs/collect/) project is used to generate and send [**support bundles**](preflight-support-bundle-about), which include logs and other important diagnostic data.
+Finally, the diagram shows how [**instance data**](/vendor/instance-insights-event-data) is automatically sent from the customer environment to the Vendor Portal by the Replicated SDK API and the KOTS Admin Console. Additionally, tooling from the open source [**Troubleshoot**](https://troubleshoot.sh/docs/collect/) project is used to generate and send [**support bundles**](/vendor/preflight-support-bundle-about), which include logs and other important diagnostic data.
 
 ## Replicated Platform Features
 

docs/intro.md

@@ -139,19 +139,19 @@ pagination_next: null
   <ul>
     <li class="tile__header">
         <img src="images/icons/k8s_installer.png" alt="installer icon"></img>
-        <p>Embedded Cluster (Beta)</p>
+        <p>Embedded Cluster</p>
     </li>
     <li>
         <p>Embed Kubernetes with your application to support installations on VMs or bare metal servers.</p>
     </li>
     <li>
-      <a href="/vendor/embedded-overview">Using Embedded Cluster (Beta)</a>
+      <a href="/vendor/embedded-overview">Using Embedded Cluster</a>
     </li>
     <li>
-      <a href="/enterprise/installing-embedded">Installing with Embedded Cluster (Beta)</a>
+      <a href="/enterprise/installing-embedded">Installing with Embedded Cluster</a>
     </li>
     <li>
-      <a href="/vendor/tutorial-embedded-cluster-setup">Tutorial: Deploy a Helm Chart on a VM with Embedded Cluster (Beta)</a>
+      <a href="/vendor/tutorial-embedded-cluster-setup">Tutorial: Deploy a Helm Chart on a VM with Embedded Cluster</a>
     </li>
   </ul>
 </section>
@@ -210,7 +210,7 @@ pagination_next: null
       <a href="/vendor/releases-creating-customer">Creating and Managing Customers</a>
     </li>
     <li>
-      <a href="/vendor/licenses-adding-custom-fields">Managing Custom License Fields</a>
+      <a href="/vendor/licenses-adding-custom-fields">Managing Customer License Fields</a>
     </li>
   </ul>
 </section>

docs/partials/embedded-cluster/_requirements.mdx

@@ -6,6 +6,8 @@
 
 * At least 2GB of memory and 2 CPU cores
 
+* The disk on the host must have a maximum P99 write latency of 10 ms. This supports etcd performance and stability. For more information about the disk write latency requirements for etcd, see [Disks](https://etcd.io/docs/latest/op-guide/hardware/#disks) in _Hardware recommendations_ and [What does the etcd warning “failed to send out heartbeat on time” mean?](https://etcd.io/docs/latest/faq/) in the etcd documentation.
+
 * The filesystem at `/var/lib/embedded-cluster` has 40Gi or more of total space and must be less than 80% full
 
    :::note

docs/partials/replicated-sdk/_dependency-yaml.mdx

@@ -3,7 +3,7 @@
 dependencies:
 - name: replicated
   repository: oci://registry.replicated.com/library
-  version: 1.0.0-beta.31
+  version: 1.0.0-beta.32
 ```
 
 For the latest version information for the Replicated SDK, see the [replicated-sdk repository](https://github.com/replicatedhq/replicated-sdk/releases) in GitHub.