Damien Querbes
11/21/2025, 11:46 AMkapa.ai
11/21/2025, 11:47 AMvalues.yaml file ready: --- ### 1. Ensure Prerequisites - Make sure you have the [Helm client installed](https://helm.sh/docs/intro/install/) and available in your path. - Your Kubernetes cluster should be accessible from your VM. --- ### 2. Add the Airbyte Helm Repository bash helm repo add airbyte-v2 https://airbytehq.github.io/helm-charts/ helm repo update (This step is implied in the documentation, as you need the repo to install the chart.) --- ### 3. Identify the Helm Chart Version Check which Helm chart version matches the Airbyte version you want to deploy: bash helm search repo airbyte-v2 --versions You’ll see output like: NAME CHART VERSION APP VERSION airbyte-v2/airbyte 2.0.18 2.0.0 airbyte-v2/airbyte 2.0.17 1.8.5 ... Choose the appropriate chart version for your deployment.<br> [Reference](https://docs.airbyte.com/platform/deploying-airbyte#5-installing-airbyte) --- ### 4. Deploy Airbyte with Helm Chart V2 Use the following command, replacing the namespace, chart version, and values file as needed: bash helm install airbyte airbyte-v2/airbyte \ --namespace airbyte-v2 \ # Target Kubernetes namespace --values ./values.yaml \ # Your custom configuration --version 2.0.18 # Helm chart version to use (Adjust --namespace and --version as appropriate for your setup.) [Reference](https://docs.airbyte.com/platform/deploying-airbyte#5-installing-airbyte) --- ### 5. (Optional) Configure Ingress After installation, you may want to configure ingress for external access. Follow the [Ingress documentation](https://docs.airbyte.com/platform/deploying-airbyte/integrations/ingress) for your specific provider. --- Note: - If you are upgrading or redeploying, do not delete the namespace unless you intend to remove all resources. - Always back up your Airbyte internal Postgres database before making changes to your deployment. --- Let me know if you need the steps for uninstalling or upgrading, or if you have a specific Airbyte version in mind!Damien Querbes
11/21/2025, 11:48 AMkapa.ai
11/21/2025, 11:49 AMkapa.ai
11/21/2025, 11:49 AMhelm by following [these instructions](https://helm.sh/docs/intro/install/)" [source](https://docs.airbyte.com/platform/1.8/enterprise-setup/implementation-guide#infrastructure-prerequisites) 2. Install kubectl Install kubectl to interact with your Kubernetes cluster. > "Install kubectl by following [these instructions](https://kubernetes.io/docs/tasks/tools/)." [source](https://docs.airbyte.com/platform/1.8/enterprise-setup/implementation-guide#infrastructure-prerequisites) 3. Provision or Connect to a Kubernetes Cluster The Airbyte documentation assumes you already have a running Kubernetes cluster. If you do not, you will need to set one up. The documentation does not provide instructions for provisioning a Kubernetes cluster on a brand new VM, so you will need to follow Kubernetes' official guides or your cloud provider's documentation for this step. > "This guide assumes that you already have a running kubernetes cluster." [source](https://docs.airbyte.com/platform/1.6/deploying-airbyte#installation-guide) 4. Configure kubectl to Connect to Your Cluster Once your cluster is running, configure kubectl to connect to it. The documentation provides steps for EKS and GKE, but if you are running a local cluster, you may need to use kubectl config commands or your cluster's setup instructions. [source](https://docs.airbyte.com/platform/1.8/enterprise-setup/implementation-guide#infrastructure-prerequisites) 5. Create a Namespace for Airbyte bash kubectl create namespace airbyte [source](https://docs.airbyte.com/platform/1.8/enterprise-setup/implementation-guide#infrastructure-prerequisites) Summary: - Install Helm and kubectl on your VM. - Provision a Kubernetes cluster (not covered in detail in the Airbyte docs). - Configure kubectl to access your cluster. - Create a namespace for Airbyte. The Airbyte documentation does not provide detailed steps for provisioning a Kubernetes cluster on a brand new VM, so you will need to refer to Kubernetes' official documentation or your cloud provider's guides for that part.Damien Querbes
11/21/2025, 11:59 AMkapa.ai
11/21/2025, 11:59 AMkapa.ai
11/21/2025, 11:59 AMkubectl to your running Kubernetes cluster, you need to configure your local kubeconfig context. The exact steps depend on where your cluster is hosted: - Amazon EKS: 1. Configure your AWS CLI: bash aws configure 2. Install eksctl if you haven't already. 3. Run: bash eksctl utils write-kubeconfig --cluster=$CLUSTER_NAME 4. List available contexts: bash kubectl config get-contexts 5. Set the context for your cluster: bash kubectl config use-context $EKS_CONTEXT - Google Kubernetes Engine (GKE): 1. Authenticate with Google Cloud: bash gcloud auth login 2. Get credentials for your cluster (the Google Cloud Console "Connect" button provides this command): bash gcloud container clusters get-credentials $CLUSTER_NAME --zone $ZONE_NAME --project $PROJECT_NAME 3. List available contexts: bash kubectl config get-contexts 4. Set the context for your cluster: bash kubectl config use-context $GKE_CONTEXT These steps are directly referenced in the Airbyte documentation for both Enterprise and Flex deployments. If your cluster is hosted elsewhere, you should use the equivalent method provided by your Kubernetes provider to update your kubeconfig and set the context for kubectl to use your cluster [see example](https://docs.airbyte.com/platform/1.8/enterprise-setup/implementation-guide#infrastructure-prerequisites). Once configured, you can test your connection with: bash kubectl get nodes If you see your cluster's nodes listed, you're connected!Damien Querbes
11/21/2025, 12:01 PMkapa.ai
11/21/2025, 12:01 PMkapa.ai
11/21/2025, 12:01 PMgcloud auth login and related gcloud commands directly from your VM. This is necessary so that kubectl on your VM is configured to communicate with your GKE cluster. The Airbyte documentation specifically states: > Configure gcloud with gcloud auth login. > On the Google Cloud Console, the cluster page will have a "Connect" button, with a command to run locally: > gcloud container clusters get-credentials $CLUSTER_NAME --zone $ZONE_NAME --project $PROJECT_NAME > Use kubectl config get-contexts to show the available contexts. > Run kubectl config use-context $EKS_CONTEXT to access the cluster with kubectl [Deploy a data plane with Helm in Enterprise Flex – Prerequisites](https://docs.airbyte.com/platform/enterprise-flex/data-plane#prerequisites) So, run these commands from your VM to ensure your kubectl is properly configured to access your GKE cluster.Damien Querbes
11/21/2025, 12:13 PMairbyte-v2
What should I do next?kapa.ai
11/21/2025, 12:13 PMkapa.ai
11/21/2025, 12:13 PMairbyte-v2, here are your next steps to deploy Airbyte using Helm Chart V2: --- ### 1. Add the Airbyte Helm Repository (if not already done) bash helm repo add airbyte-v2 https://airbytehq.github.io/helm-charts/ helm repo update (This step is implied in the documentation as necessary to access the chart.) --- ### 2. Identify the Helm Chart Version Check which Helm chart version matches the Airbyte version you want to deploy: bash helm search repo airbyte-v2 --versions You’ll see output like: NAME CHART VERSION APP VERSION airbyte-v2/airbyte 2.0.18 2.0.0 airbyte-v2/airbyte 2.0.17 1.8.5 ... Choose the appropriate chart version for your deployment ([source](https://docs.airbyte.com/platform/deploying-airbyte#5-installing-airbyte)). --- ### 3. Deploy Airbyte Use the following command, replacing the chart version and values file as needed: bash helm install airbyte airbyte-v2/airbyte \ --namespace airbyte-v2 \ --values ./values.yaml \ --version 2.0.18 (Adjust --version to match your chosen chart version.) [Reference](https://docs.airbyte.com/platform/deploying-airbyte#5-installing-airbyte) --- ### 4. (Optional) Configure Ingress After installation, you may want to configure ingress for external access. Follow the [Ingress documentation](https://docs.airbyte.com/platform/deploying-airbyte/integrations/ingress) for your specific provider. --- That’s it! Airbyte will be deployed in your airbyte-v2 namespace using your custom configuration.Damien Querbes
11/21/2025, 12:17 PMDamien Querbes
11/21/2025, 12:19 PMkapa.ai
11/21/2025, 12:19 PMkapa.ai
11/21/2025, 12:19 PMkapa.ai
11/21/2025, 12:19 PMbash helm repo add airbyte-v2 https://airbytehq.github.io/helm-charts/ helm repo update This step ensures you have access to the latest Airbyte Helm charts. 2. Identify the Helm chart version you want to use: bash helm search repo airbyte-v2 --versions This command will list available chart versions and their corresponding Airbyte app versions. Choose the version that matches your requirements. Example output: NAME CHART VERSION APP VERSION airbyte-v2/airbyte 2.0.18 2.0.0 airbyte-v2/airbyte 2.0.17 1.8.5 ... [See documentation](https://docs.airbyte.com/platform/deploying-airbyte#5-installing-airbyte) 3. Deploy Airbyte using Helm: bash helm install airbyte airbyte-v2/airbyte \ --namespace airbyte-v2 \ --values ./values.yaml \ --version 2.0.18 Replace 2.0.18 with your chosen chart version and ensure your values.yaml file is in place. [See documentation](https://docs.airbyte.com/platform/deploying-airbyte#5-installing-airbyte) 4. (Optional) Configure Ingress: After installation, you may want to configure ingress for external access. The documentation recommends following the [Ingress setup guide](https://docs.airbyte.com/platform/deploying-airbyte/integrations/ingress) for your environment. These steps are directly supported by the knowledge sources. If you need to upgrade, uninstall, or restore Airbyte, let me know!kapa.ai
11/21/2025, 12:19 PMbash helm repo add airbyte-v2 https://airbytehq.github.io/helm-charts/ helm repo update This step ensures you have access to the latest Airbyte Helm charts. [Reference](https://docs.airbyte.com/platform/next/deploying-airbyte#5-installing-airbyte) --- ### 2. Identify the Helm Chart Version List available chart versions to select the one that matches your desired Airbyte version: bash helm search repo airbyte-v2 --versions You will see output similar to: NAME CHART VERSION APP VERSION airbyte-v2/airbyte 2.0.18 2.0.0 airbyte-v2/airbyte 2.0.17 1.8.5 ... Choose the chart version you want to deploy. [Reference](https://docs.airbyte.com/platform/next/deploying-airbyte#5-installing-airbyte) --- ### 3. Deploy Airbyte Run the following command, replacing the chart version and values file as needed: bash helm install airbyte airbyte-v2/airbyte \ --namespace airbyte-v2 \ --values ./values.yaml \ --version 2.0.18 Make sure to use the correct --version that matches your chosen chart version. [Reference](https://docs.airbyte.com/platform/next/deploying-airbyte#5-installing-airbyte) --- After this, Airbyte will be deployed in your airbyte-v2 namespace using your custom configuration. If you need to expose Airbyte externally, you can configure ingress as described in the documentation. If you need further steps (like configuring ingress or restoring a database), let me know!kapa.ai
11/21/2025, 12:20 PMkapa.ai
11/21/2025, 12:20 PMbash helm repo add airbyte-v2 https://airbytehq.github.io/helm-charts/ helm repo update This ensures you have access to the latest Airbyte Helm charts. 2. Identify the Helm chart version you want to use: bash helm search repo airbyte-v2 --versions This command will show you the available chart versions and their corresponding Airbyte app versions. Choose the version that matches your requirements. For example, you might see: airbyte-v2/airbyte 2.0.18 2.0.0 airbyte-v2/airbyte 2.0.17 1.8.5 ... [See documentation for details](https://docs.airbyte.com/platform/next/deploying-airbyte#5-installing-airbyte). 3. Deploy Airbyte using Helm: bash helm install airbyte airbyte-v2/airbyte \ --namespace airbyte-v2 \ --values ./values.yaml \ --version 2.0.18 Replace 2.0.18 with your chosen chart version. This will deploy Airbyte in your airbyte-v2 namespace using your custom configuration file. These steps are directly supported by the knowledge sources. If you need to configure ingress or perform additional setup after deployment, you can refer to the ingress documentation linked in the installation guide. If you have further questions or need help with a specific step, let me know!Damien Querbes
11/21/2025, 12:22 PMkapa.ai
11/21/2025, 12:22 PMkapa.ai
11/21/2025, 12:22 PMvalues.yaml file accordingly, based strictly on the provided knowledge sources: --- ### 1. Create a GCP Service Account and Key - Create a GCP service account with permissions to access both Google Cloud Storage (GCS) and Google Secret Manager (GSM). - Download the service account key as a JSON file (gcp.json). --- ### 2. Create a Kubernetes Secret with the Service Account Key - Store the gcp.json file in a Kubernetes secret. By default, Airbyte expects this secret to be named airbyte-config-secrets and the key to be gcp.json. bash kubectl create secret generic airbyte-config-secrets \ --from-file=gcp.json=</path/to/your/gcp.json> \ --namespace airbyte-v2 (Replace </path/to/your/gcp.json> with the actual path to your service account key and airbyte-v2 with your namespace if different.) --- ### 3. Adjust your values.yaml File Add or update the following section in your values.yaml to configure Airbyte to use Google Secret Manager: yaml global: secretsManager: type: googleSecretManager secretName: "airbyte-config-secrets" # Name of your Kubernetes secret googleSecretManager: projectId: <project-id> # Your GCP project ID credentialsSecretKey: gcp.json # The key in the Kubernetes secret (Replace <project-id> with your actual GCP project ID.) > Ensure you've already created a Kubernetes secret containing the credentials blob for the service account to be assumed by the cluster. By default, secrets are expected in the airbyte-config-secrets Kubernetes secret, under a gcp.json file. [Source](https://docs.airbyte.com/platform/deploying-airbyte/integrations/secrets#values) --- ### 4. Deploy or Upgrade Airbyte with the Updated Configuration If you are installing Airbyte for the first time: bash helm install airbyte airbyte-v2/airbyte \ --namespace airbyte-v2 \ --values ./values.yaml If you are updating an existing deployment: bash helm upgrade airbyte airbyte-v2/airbyte \ --namespace airbyte-v2 \ --values ./values.yaml --- Important: - Modifying the configuration of connector secret storage will cause all existing connectors to fail. You will need to recreate these connectors to ensure they are reading from the appropriate secret store. --- If you need to use a different secret name or key, adjust the secretName and credentialsSecretKey fields accordingly in your values.yaml file. Let me know if you need more details on any step!