Merge branch 'main' into emosbaugh/sc-108560/determine-all-the-directories-that-embedded

Author: emosbaugh

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.

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/vendor/custom-domains.md

@@ -19,13 +19,13 @@ The TXT records can be removed after the verification is complete.
 
 You can configure custom domains for the following services, so that customer-facing URLs reflect your company's brand:
 
-- **Replicated registry:** Images and Helm charts can be pulled from the Replicated registry. By default, this registry uses the domain `registry.replicated.com`.
+- **Replicated registry:** Images and Helm charts can be pulled from the Replicated registry. By default, this registry uses the domain `registry.replicated.com`. We suggest using a CNAME such as `registry.{your app name}.com`. 
 
-- **Proxy registry:** Images can be proxied from external private registries using the Replicated proxy registry. By default, the proxy registry uses the domain `proxy.replicated.com`.
+- **Proxy registry:** Images can be proxied from external private registries using the Replicated proxy registry. By default, the proxy registry uses the domain `proxy.replicated.com`. We suggest using a CNAME such as `proxy.{your app name}.com`. 
 
-- **Replicated app service:** Upstream application YAML and metadata, including a license ID, are pulled from replicated.app. By default, this service uses the domain `replicated.app`.
+- **Replicated app service:** Upstream application YAML and metadata, including a license ID, are pulled from replicated.app. By default, this service uses the domain `replicated.app`. We suggest using a CNAME such as `updates.{your app name}.com`. 
 
-- **Download Portal:** The Download Portal can be used to share customer license files, air gap bundles, and so on. By default, the Download Portal uses the domain `get.replicated.com`.
+- **Download Portal:** The Download Portal can be used to share customer license files, air gap bundles, and so on. By default, the Download Portal uses the domain `get.replicated.com`. We suggest using a CNAME such as `portal.{your app name}.com` or `enterprise.{your app name}.com`. 
 
 ## Limitations
 

docs/vendor/embedded-overview.mdx

@@ -51,7 +51,7 @@ Embedded Cluster has the following limitations:
 
 * **No automated migration from kURL**: There is no automated migration from an existing kURL instance to Embedded Cluster. For a manual migration procedure, reach out to Alex Parker at [email protected].
 
-* **Multi-node support is in alpha**: Support for multi-node embedded clusters is in alpha. Only single-node embedded clusters are in beta. For more information, see [Enable High Availability for Multi-Node Clusters (Alpha)](#ha) below.
+* **Multi-node support is in beta**: Support for multi-node embedded clusters is in beta, and enabling high availability for multi-node clusters is in alpha. Only single-node embedded clusters are generally available. For more information, see [Add Nodes (Beta)](#add-nodes) and [Enable High Availability for Multi-Node Clusters (Alpha)](#ha) below.
 
 * **Disaster recovery is in alpha**: Disaster Recovery for Embedded Cluster installations is in alpha. For more information, see [Disaster Recovery for Embedded Cluster (Alpha)](/vendor/embedded-disaster-recovery).
 
@@ -121,7 +121,7 @@ This section provides an overview of installing applications with Embedded Clust
 
 ### Installation Options
 
-Embedded Cluster supports installations in online (internet-connected) environments and has alpha support for installing in air gap environments with no outbound internet access.
+Embedded Cluster supports installations in online (internet-connected) environments and air gap environments with no outbound internet access.
 
 For online installations, Embedded Cluster also supports installing behind a proxy server.
 
@@ -264,7 +264,7 @@ You can then use the support bundle for troubleshooting or provide it to Replica
 
 The section describes managing nodes in clusters created with Embedded Cluster, including how to add or reset nodes.
 
-### Add Nodes (Alpha) {#add-nodes}
+### Add Nodes (Beta) {#add-nodes}
 
 You can add nodes and create a multi-node cluster. When adding nodes, you select one or more roles for that node, depending on which roles are defined in the Embedded Cluster config. The Admin Console provides the join command you use to join nodes to the cluster.
 

docs/vendor/telemetry-air-gap.mdx

@@ -1,13 +1,9 @@
 import AirGapTelemetry from "../partials/instance-insights/_airgap-telemetry.mdx"
 
-# Collecting Telemetry for Air Gap Instances (Beta)
+# Collecting Telemetry for Air Gap Instances
 
 This topic describes how to collect telemetry for instances in air gap environments.
 
-:::note
-Air gap telemetry is in beta. The functionality, requirements, and limitations of air gap telemetry are subject to change.
-:::
-
 ## Overview
 
 Air gap instances run in environments without outbound internet access. This limitation prevents these instances from periodically sending telemetry to the Replicated Vendor Portal through the Replicated SDK or Replicated KOTS. For more information about how the Vendor Portal collects telemetry from online (internet-connected) instances, see [About Instance and Event Data](/vendor/instance-insights-event-data#about-reporting).