Merge branch 'main' into 112484

Author: paigecalvert

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

@@ -8,10 +8,6 @@ import Prerequisites from "../partials/install/_ec-prereqs.mdx"
 
 This topic describes how to install applications with Embedded Cluster on a virtual machine (VM) or bare metal server with no outbound internet access.
 
-:::note
-Embedded Cluster installations in air gap environments is a beta feature. This feature is subject to change. To get access to this feature, reach out to Alex Parker at [[email protected]](mailto:[email protected]).
-:::
-
 ## Overview
 
 When an air gap bundle is built for a release containing an Embedded Cluster Config, both an application air gap bundle and an Embedded Cluster air gap bundle are built. The application air gap bundle can be used for air gap installations with Replicated kURL or with Replicated KOTS in an existing cluster. The Embedded Cluster air gap bundle is used for air gap installations with Embedded Cluster.
@@ -62,23 +58,17 @@ To install with Embedded Cluster in an air gap environment:
 
      [View a larger version of this image](/images/customer-install-instructions-dropdown.png)
 
-     The **Embedded Cluster install instructions** dialog is displayed.
+1. In the **Embedded Cluster install instructions** dialog, enable the **Install in an air gap environment** checkbox.
 
-     <img alt="Embedded cluster install instruction dialog" src="/images/embedded-cluster-install-dialog.png" width="500px"/>
+    <img alt="Embedded cluster install instruction dialog" src="/images/embedded-cluster-install-dialog-airgap.png" width="500px"/>
 
-     [View a larger version of this image](/images/embedded-cluster-install-dialog.png)
+    [View a larger version of this image](/images/embedded-cluster-install-dialog-airgap.png)
 
-1. (Optional) In the **Embedded Cluster install instructions** dialog, under **Select a version**, select a specific application version to install. By default, the latest version is selected.
+1. (Optional) For **Select a version**, select a specific application version to install. By default, the latest version is selected.
 
 1. SSH onto the machine where you will install.
 
-1. Modify the curl command provided in the first step in the **Embedded Cluster installation instructions** dialog by adding the `?airgap=true` query parameter to the end of the `replicated.app` endpoint:
-
-    ```bash
-    curl -f https://replicated.app/embedded/APP_SLUG/CHANNEL_SLUG?airgap=true -H "Authorization: LICENSE_ID" -o APP_SLUG-CHANNEL_SLUG.tgz
-    ```
-
-1. On a machine with internet access, run the modified curl command to download the air gap installation assets as a `.tgz`.
+1. On a machine with internet access, run the curl command to download the air gap installation assets as a `.tgz`.
 
 1. Move the downloaded `.tgz` to the air gapped machine where you will install. 
 

docs/enterprise/installing-embedded.mdx

@@ -10,6 +10,8 @@ Before you install, complete the following prerequisites:
 
 <Prerequisites/>
 
+* Ensure that the required domains are accessible from servers performing the installation. See [Firewall Openings for Online Installations](/enterprise/installing-general-requirements#firewall-openings-for-online-installations).
+
 ## Install
 
 To install an application with Embedded Cluster:
@@ -188,4 +190,22 @@ sudo ./my-app install --license license.yaml --pod-cidr 172.16.136.0/16
 
 #### Limitation
 
-The `--pod-cidr` and `--service-cidr` flags are not supported on Red Hat Enterprise Linux (RHEL) 9 operating systems.
+The `--pod-cidr` and `--service-cidr` flags are not supported on Red Hat Enterprise Linux (RHEL) 9 operating systems.
+
+## Change Admin Console and LAM Ports {#adm-lam-ports}
+
+By default, the Admin Console and Local Artifact Mirror (LAM) run on ports 30000 and 50000, respectively. If these ports are occupied, you can select different ports.
+
+To choose different ports for the Admin Console and LAM during installation with Embedded Cluster, use the `--admin-console-port` and `--local-artifact-mirror-port` flags with the Embedded Cluster `install` command.
+
+For example:
+
+```bash
+install --admin-console-port=20000 --local-artifact-mirror-port=40000
+```
+
+The Embedded Cluster host preflight checks verify the default ports or the user-supplied ports, so users will be alerted before installation if they need to choose new port(s). For more information about the host preflight checks for Embedded Cluster, see [About Host Preflight Checks](/vendor/embedded-overview#about-host-preflight-checks).
+
+### Limitation
+
+It is not possible to change the port for the Admin Console during a restore with Embedded Cluster. For more information, see [Disaster Recovery for Embedded Cluster (Alpha)](/vendor/embedded-disaster-recovery).

docs/enterprise/installing-existing-cluster-automation.mdx

@@ -41,7 +41,7 @@ One common use case for installing with the CLI is to automate installation, suc
 
 For more information about the advanced options for the `kots install` command, see [install](/reference/kots-cli-install) in the KOTS CLI documentation.
 
-For a tutorial that demonstrates how to install a sample application using the KOTS CLI, see [KOTS Tutorial (CLI)](/vendor/tutorial-cli-setup).
+For a tutorial that demonstrates how to install a sample application using the KOTS CLI, see [Install with KOTS in an Existing Cluster](/vendor/tutorial-cli-setup).
 
 ## Limitation
 

docs/enterprise/installing-general-requirements.mdx

@@ -2,6 +2,7 @@ import DockerCompatibility from "../partials/image-registry/_docker-compatibilit
 import KubernetesCompatibility from "../partials/install/_kubernetes-compatibility.mdx"
 import EmbeddedClusterRequirements from "../partials/embedded-cluster/_requirements.mdx"
 import EmbeddedClusterStorageReqs from "../partials/embedded-cluster/_storage-reqs.mdx"
+import EmbeddedClusterPortRequirements from "../partials/embedded-cluster/_port-reqs.mdx"
 
 # Installation Requirements
 
@@ -262,6 +263,10 @@ To install with the Embedded Cluster installer, your environment must meet the f
 
 <EmbeddedClusterStorageReqs/>
 
+### Port Requirements
+
+<EmbeddedClusterPortRequirements/>
+
 ## kURL Requirements {#kurl-requirements}
 
 To install with kURL, your environment must meet the following requirements.

docs/enterprise/installing-kurl-airgap.mdx

@@ -1,5 +1,4 @@
 import KurlAbout from "../partials/install/_kurl-about.mdx"
-import HaLoadBalancerAbout from "../partials/install/_ha-load-balancer-about.mdx"
 import IntroEmbedded from "../partials/install/_intro-embedded.mdx"
 import IntroAirGap from "../partials/install/_intro-air-gap.mdx"
 import PrereqsEmbeddedCluster from "../partials/install/_prereqs-embedded-cluster.mdx"
@@ -18,12 +17,6 @@ import ExtractKurlBundle from "../partials/install/_extract-kurl-bundle.mdx"
 
 <KurlAbout/>
 
-## About High Availability Mode
-
-Air gap installations can use high availability (HA) mode with the kURL installer.
-
-<HaLoadBalancerAbout/>
-
 ## Prerequisites
 
 Complete the following prerequisites:

docs/enterprise/installing-kurl.mdx

@@ -1,5 +1,4 @@
 import KurlAbout from "../partials/install/_kurl-about.mdx"
-import HaLoadBalancerAbout from "../partials/install/_ha-load-balancer-about.mdx"
 import IntroEmbedded from "../partials/install/_intro-embedded.mdx"
 import PrereqsEmbeddedCluster from "../partials/install/_prereqs-embedded-cluster.mdx"
 import HaLoadBalancerPrereq from "../partials/install/_ha-load-balancer-prereq.mdx"
@@ -14,12 +13,6 @@ import AppNameUI from "../partials/install/_placeholder-app-name-UI.mdx"
 
 <KurlAbout/>
 
-## About High Availability Mode
-
-Online installations can use high availability (HA) mode with the kURL installer.
-
-<HaLoadBalancerAbout/>
-
 ## Prerequisites
 
 Complete the following prerequisites:

docs/enterprise/updating-apps.mdx

@@ -34,7 +34,7 @@ To configure automatic updates:
 
    To turn off automatic updates, select **Never**. 
 
-   To define a custom cadence, select **Custom**, then enter a cron expression in the text field. For more information about cron expressions, see [Cron Expressions](/reference/cron-expressions) in _Reference_. Configured automatic update checks use the local server time. 
+   To define a custom cadence, select **Custom**, then enter a cron expression in the text field. For more information about cron expressions, see [Cron Expressions](/reference/cron-expressions). Configured automatic update checks use the local server time. 
 
    ![Configure automatic updates](/images/automatic-updates-config.png)
 

docs/enterprise/updating-embedded.mdx

@@ -9,7 +9,7 @@ import Overview from "../partials/embedded-cluster/_update-overview.mdx"
 This topic describes how to perform updates for [Replicated Embedded Cluster](/vendor/embedded-overview) installations.
 
 :::note
-Embedded cluster is in beta. If you are instead looking for information about Replicated kURL, see [Performing Updates in kURL Clusters](updating-kurl).
+If you are instead looking for information about Replicated kURL, see [Performing Updates in kURL Clusters](updating-kurl).
 :::
 
 ## Overview
@@ -68,11 +68,7 @@ To perform an update with Embedded Cluster:
    KOTS can experience downtime during an update, such as in single-node installations. If downtime occurs, refreshing the page results in a connection error. Users can refresh the page again after the update is complete to access the Admin Console.
    :::
 
-## Update in Air Gap Clusters (Alpha) 
-
-:::important
-Embedded Cluster installations in air gap environments 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]).
-:::
+## Update in Air Gap Clusters
 
 <DoNotDowngrade/>
 

docs/enterprise/updating-kurl.mdx

@@ -7,6 +7,8 @@ import AdminConsoleAirGap from "../partials/updating/_admin-console-air-gap.mdx"
 
 This topic describes how to perform updates in Replicated kURL installations. It includes procedures for updating an application, as well as for updating the versions of Kubernetes, Replicated KOTS, and add-ons in a kURL cluster.
 
+For more information about managing nodes in kURL clusters, including how to safely reset, reboot, and remove nodes when performing maintenance tasks, see [Managing Nodes](https://kurl.sh/docs/install-with-kurl/managing-nodes) in the open source kURL documentation.
+
 ## Update an Application
 
 For kURL installations, you can update an application from the Admin Console. You can also set up automatic updates. See [Configuring Automatic Updates](/enterprise/updating-apps).
@@ -23,6 +25,8 @@ For kURL installations, you can update an application from the Admin Console. Yo
 
 After updating the kURL installer spec, you can rerun the kURL installation script to update a kURL cluster. For more information about kURL cluster udpates, see [About kURL Cluster Updates](/enterprise/updating-kurl-about).
 
+For more information about managing nodes in kURL clusters, including how to safely reset, reboot, and remove nodes when performing maintenance tasks, see [Managing Nodes](https://kurl.sh/docs/install-with-kurl/managing-nodes) in the open source kURL documentation.
+
 :::important
 The Kubernetes scheduler automatically reschedules Pods to other nodes during maintenance. Any deployments or StatefulSets with a single replica experience downtime while being rescheduled.
 :::

docs/intro.md

@@ -46,7 +46,7 @@ pagination_next: null
       <a href="intro-replicated">Introduction to Replicated</a>
     </li>
     <li>
-      <a href="/vendor/distributing-overview">About Distributing Applications with Replicated</a>
+      <a href="/vendor/kots-faq">Replicated FAQs</a>
     </li>
     <li>
       <a href="/vendor/replicated-onboarding">Replicated Quick Start</a>
@@ -141,9 +141,6 @@ pagination_next: null
     <li>
       <a href="intro-kots">Introduction to KOTS</a>
     </li>
-    <li>
-      <a href="/vendor/kots-faq">KOTS Terminology and FAQs</a>
-    </li>
     <li>
       <a href="/vendor/distributing-workflow">Onboarding with KOTS</a>
     </li>