docs: Remove Helm Chart V1 documentation for v2.1.0 release (#75964)

Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

Author: ian-at-airbyte

docs/platform/access-management/sso-providers/azure-entra-id.md

@@ -3,9 +3,6 @@ sidebar_label: Entra ID
 products: cloud, oss-enterprise
 ---
 
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
 # Set up single sign on using Entra ID
 
 This guide shows you how to set up Microsoft Entra ID (formerly Azure ActiveDirectory) and Airbyte so your users can log into Airbyte using your organization's identity provider (IdP) and OpenID Connect (OIDC).
@@ -197,11 +194,6 @@ To set up single sign on for Airbyte Self-Managed Enterprise, complete the follo
 - [Update Airbyte's values.yaml file](#sme-update-values)
 - [Redeploy Airbyte](#sme-deploy)
 
-:::note
-You can only use generic OIDC after you migrate to Helm chart V2.
-<!-- [Helm chart V2](../../enterprise-setup/chart-v2-enterprise). -->
-:::
-
 ### Create application {#sme-entra-id-app}
 
 To start, you create a new Entra ID application for Airbyte.
@@ -317,8 +309,8 @@ You collect these values from Microsoft in the locations shown below.
 In your command-line tool, deploy Airbyte using your updated values file.
 
 ```bash
-helm upgrade airbyte-enterprise airbyte-v2/airbyte \
-  --namespace airbyte-v2 \       # Target Kubernetes namespace
+helm upgrade airbyte-enterprise airbyte/airbyte \
+  --namespace airbyte \           # Target Kubernetes namespace
   --values ./values.yaml \       # Custom configuration values
   --version 2.x.x                # Helm chart version to use
 ```

docs/platform/access-management/sso-providers/okta.md

@@ -3,9 +3,6 @@ sidebar_label: Okta
 products: oss-enterprise, cloud
 ---
 
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
 # Set up single sign on using Okta
 
 This guide shows you how to set up Okta and Airbyte so your users can log into Airbyte using your organization's identity provider (IdP).
@@ -203,10 +200,10 @@ Create the application with the following parameters:
 
 Once your Okta app is set up, you're ready to deploy Airbyte with SSO. Take note of the following configuration values, as you will need them to configure Airbyte to use your new Okta SSO app integration:
 
-* Okta domain ([How to find your Okta domain](https://developer.okta.com/docs/guides/find-your-domain/main/))
-* App Integration Name
-* Client ID
-* Client Secret
+- Okta domain ([How to find your Okta domain](https://developer.okta.com/docs/guides/find-your-domain/main/))
+- App Integration Name
+- Client ID
+- Client Secret
 
 (Optional) To allow users to access Airbyte directly from their Okta dashboard, configure IdP-Initiated Login. In the **General** tab of your Airbyte application, scroll to **Login initiated by** and configure the following settings:
 
@@ -229,11 +226,6 @@ To set up single sign using generic OIDC for Airbyte Self-Managed Enterprise, co
 - [Update Airbyte's values.yaml file](#sme-values)
 - [Redeploy Airbyte](#sme-deploy)
 
-:::note
-You can only use generic OIDC after you migrate to Helm chart V2.
-<!-- [Helm chart V2](../../enterprise-setup/chart-v2-enterprise). -->
-:::
-
 ### Create an Okta app for Airbyte {#sme-create-okta-app}
 
 Follow these steps to set up an Okta app integration for Airbyte. If you need more help setting up an app integration, see [Okta's documentation](https://help.okta.com/en-us/content/topics/apps/apps_app_integration_wizard_oidc.htm).
@@ -370,6 +362,6 @@ helm upgrade -i \
 --namespace airbyte \
 --values ./values.yaml \
 airbyte \
-airbyte-v2/airbyte \
+airbyte/airbyte \
 --version 2.x.x
 ```

docs/platform/connector-development/connector-builder-ui/custom-components.md

@@ -2,9 +2,6 @@
 products: oss-community, oss-enterprise
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 # Custom components for the Connector Builder
 
 Use Custom Components to extend the Connector Builder with your own Python implementations when Airbyte's built-in components don't meet your specific needs.
@@ -59,22 +56,6 @@ If you deploy Airbyte with abctl, follow the steps below to update your values a
 
 1. Edit your existing `values.yaml` file or create a new override file with this configuration:
 
-    <Tabs groupId="helm-chart-version">
-    <TabItem value='helm-1' label='Helm chart V1' default>
-
-      ```yaml title="values.yaml"
-      workload-launcher:
-        extraEnv:
-          - name: AIRBYTE_ENABLE_UNSAFE_CODE
-            value: "true"
-      connector-builder-server:
-        extraEnv:
-          - name: AIRBYTE_ENABLE_UNSAFE_CODE
-            value: "true"
-      ```
-    </TabItem>
-    <TabItem value='helm-2' label='Helm chart V2' default>
-
     ```yaml title="values.yaml"
     workloadLauncher:
       extraEnv:
@@ -86,10 +67,6 @@ If you deploy Airbyte with abctl, follow the steps below to update your values a
           value: "true"
     ```
 
-    </TabItem>
-    </Tabs>
-
-
 2. Use this file during deployment with the abctl command:
 
    ```bash
@@ -102,22 +79,6 @@ If you're deploying Airbyte using public Helm charts without abctl, follow the s
 
 1. Edit your existing `values.yaml` file or create a new override file with this configuration:
 
-    <Tabs groupId="helm-chart-version">
-    <TabItem value='helm-1' label='Helm chart V1' default>
-
-      ```yaml title="values.yaml"
-      workload-launcher:
-        extraEnv:
-          - name: AIRBYTE_ENABLE_UNSAFE_CODE
-            value: "true"
-      connector-builder-server:
-        extraEnv:
-          - name: AIRBYTE_ENABLE_UNSAFE_CODE
-            value: "true"
-      ```
-    </TabItem>
-    <TabItem value='helm-2' label='Helm chart V2' default>
-
     ```yaml title="values.yaml"
     workloadLauncher:
       extraEnv:
@@ -129,34 +90,15 @@ If you're deploying Airbyte using public Helm charts without abctl, follow the s
           value: "true"
     ```
 
-    </TabItem>
-    </Tabs>
-
 2. Apply the configuration during Helm installation or upgrade:
 
-    <Tabs groupId="helm-chart-version">
-    <TabItem value='helm-1' label='Helm chart V1' default>
-
     ```bash
-    helm upgrade airbyte airbyte-v2/airbyte \
-      --namespace airbyte \       # Target Kubernetes namespace
-      --values ./values.yaml \    # Custom configuration values
-    ```
-
-    </TabItem>
-    <TabItem value='helm-2' label='Helm chart V2' default>
-
-    ```bash
-    helm upgrade airbyte airbyte-v2/airbyte \
-      --namespace airbyte-v2 \       # Target Kubernetes namespace
+    helm upgrade airbyte airbyte/airbyte \
+      --namespace airbyte \           # Target Kubernetes namespace
       --values ./values.yaml \       # Custom configuration values
       --version 2.x.x                # Helm chart version to use
     ```
 
-    </TabItem>
-    </Tabs>
-
-
 :::caution
 Monitor your deployment for any security or performance issues. Remember that this feature allows execution of arbitrary code in your Airbyte environment.
 :::

docs/platform/deploying-airbyte/chart-v2-community.mdx

@@ -9,21 +9,19 @@ import HelmSyntaxConversion from '@site/static/_helm-chart-2-syntax-changes.md';
 
 # Upgrade to Helm chart V2 (Core)
 
-Airbyte has upgraded its Helm chart to a new version called "V2." Using Helm chart V2 is currently optional. At some future date the V2 Helm chart will become the standard, so we advise that you upgrade your existing deployment to use the new chart before the transition. If you're a new Airbyte user, you can skip the upgrade altogether and start with the new chart.
+As of Airbyte v2.1.0, Helm chart V1 is no longer supported. Helm chart V2 is now the only supported chart. If you haven't already upgraded, you must migrate to Helm chart V2 to continue receiving updates. If you're a new Airbyte user, you can skip this guide and start directly with the current chart — see [Deploying Airbyte](../deploying-airbyte/deploying-airbyte.md).
 
 :::important Enterprise customers
 Follow the [Self-Managed Enterprise guide](../enterprise-setup/chart-v2-enterprise) instead.
 :::
 
-## Why you should upgrade
+## Why you must upgrade
 
-Upgrading to the new Helm chart now has the following benefits.
+Helm chart V1 is no longer supported as of Airbyte v2.1.0. You must upgrade to Helm chart V2 to continue receiving Airbyte updates. In addition to being required, the new chart has the following benefits:
 
-1. By upgrading in advance, you can schedule this upgrade for a convenient time. Avoid blocking yourself from upgrading Airbyte to a future version when the new chart is mandatory and you're busy.
+1. The new Helm chart is more aligned with Helm's best practices for chart design.
 
-2. The new Helm chart is more aligned with Helm's best practices for chart design.
-
-3. The new Helm chart has broader and more detailed options to customize your deployment. In most cases, it's no longer necessary to specify environment variables in your `values.yaml` file because the chart offers a more detailed interface for customization. If you do need to use environment variables, you can use fewer of them.
+2. The new Helm chart has broader and more detailed options to customize your deployment. In most cases, it's no longer necessary to specify environment variables in your `values.yaml` file because the chart offers a more detailed interface for customization. If you do need to use environment variables, you can use fewer of them.
 
 ## Which versions can upgrade to Helm chart V2
 
@@ -33,9 +31,9 @@ The following versions of Airbyte can use Helm chart V2:
 
 - Airbyte version 1.6.0 and later, if installed and managed with abctl version 0.30.0 or later (abctl uses Helm chart V2 by default starting with version 0.30.0)
 
-The following versions of Airbyte _can't_ use Helm chart V2:
+The following versions of Airbyte _can't_ use Helm chart V2 directly:
 
-- Airbyte versions before 1.6.0
+- Airbyte versions before 1.6.0 — you must first upgrade to at least 1.6.0 on Helm chart V1 before migrating to V2
 
 - Airbyte installed and managed with abctl versions before 0.30.0