Merge pull request #3047 from replicatedhq/AmberAlston-patch-1

Remove Alpha and Beta label references on Helm Air Gap

Author: paigecalvert

docs/vendor/helm-install-airgap.mdx

@@ -1,10 +1,6 @@
 import Prerequisites from "../partials/helm/_helm-install-prereqs.mdx"
 
-# Installing and Updating with Helm in Air Gap Environments (Beta)
-
-:::note
-Air gap Helm installations are an Beta feature. If you are interested in trying Helm air gap installations and providing feedback, please reach out to your account rep to enable this feature.
-:::
+# Installing and Updating with Helm in Air Gap Environments
 
 ## Overview
 
@@ -106,4 +102,4 @@ Unless the customer has set up the `values` to preserve the updated tag (for exa
 
 ## Use a Harbor or Artifactory Registry Proxy
 
-You can integrate the Replicated proxy registry with an existing Harbor or jFrog Artifactory instance to proxy and cache images on demand. For more information, see [Using a Registry Proxy for Helm Air Gap Installations (Alpha)](using-third-party-registry-proxy).
+You can integrate the Replicated proxy registry with an existing Harbor or jFrog Artifactory instance to proxy and cache images on demand. For more information, see [Using a Registry Proxy for Helm Air Gap Installations](using-third-party-registry-proxy).

docs/vendor/kots-faq.mdx

@@ -55,7 +55,7 @@ Replicated supports installations into air-gapped environments. In an air gap in
 
 For more information, see:
 * [Air Gap Installation with Embedded Cluster](/enterprise/installing-embedded-air-gap)
-* [Installing and Updating with Helm in Air Gap Environments (Alpha)](/vendor/helm-install-airgap)
+* [Installing and Updating with Helm in Air Gap Environments](/vendor/helm-install-airgap)
 
 ### What is the Commercial Sotware Distribution Lifecycle?
 
@@ -208,4 +208,4 @@ For instances running in online (internet-connected) customer environments, eith
 
 For air gap instances, Replicated KOTS and the Replicated SDK collect and store instance telemetry in a Kubernetes Secret in the customer environment. The telemetry stored in the Secret is collected when a support bundle is generated in the environment. When the support bundle is uploaded to the Vendor Portal, the telemetry is associated with the correct customer and instance ID, and the Vendor Portal updates the instance insights and event data accordingly.
 
-For more information, see [About Instance and Event Data](/vendor/instance-insights-event-data).
+For more information, see [About Instance and Event Data](/vendor/instance-insights-event-data).

docs/vendor/using-third-party-registry-proxy.mdx

@@ -1,4 +1,4 @@
-# Using a Registry Proxy for Helm Air Gap Installations (Beta)
+# Using a Registry Proxy for Helm Air Gap Installations
 
 This topic describes how to connect the Replicated proxy registry to a Harbor or jFrog Artifactory instance to support pull-through image caching. It also includes information about how to set up replication rules in Harbor for image mirroring.