soma chandra sekhar attaluri
11/26/2025, 6:32 PMkapa.ai
11/26/2025, 6:32 PMsoma chandra sekhar attaluri
11/26/2025, 6:44 PMkapa.ai
11/26/2025, 6:44 PMkapa.ai
11/26/2025, 6:45 PMhelm list -n <your-namespace> This will show you the deployed releases in the specified namespace, including the chart version. The output will have a column named CHART that displays the chart name and version, for example: airbyte-1.9.1 or airbyte-v2-2.0.18. The knowledge sources do not provide a direct example of this command, but this is the standard Helm way to check the chart version of an installed release. If you need to see all available chart versions in a repository, you can use: helm search repo airbyte/airbyte --versions or helm search repo airbyte-v2/airbyte --versions This will list all available chart versions in the repository, as shown in the documentation and GitHub issues [Deploying Airbyte](https://docs.airbyte.com/platform/deploying-airbyte/chart-v2-community#deploy-airbyte) [Error while installing airbyte through helm chart](https://github.com/airbytehq/airbyte/issues/68136).soma chandra sekhar attaluri
11/26/2025, 6:46 PMkapa.ai
11/26/2025, 6:46 PMkapa.ai
11/26/2025, 6:46 PMsoma chandra sekhar attaluri
11/26/2025, 6:47 PMkapa.ai
11/26/2025, 6:47 PMkapa.ai
11/26/2025, 6:47 PMairbyte/airbyte and have chart versions like 1.9.1, 1.8.5, etc. Helm chart V2 uses a different repository (airbyte-v2/airbyte) and chart versions like 2.0.18, 2.0.17, etc. This is confirmed in the knowledge sources, which state that chart version 1.9.1 is part of Helm chart V1 and is used to deploy Airbyte 2.0.1 [Error while installing airbyte through helm chart](https://github.com/airbytehq/airbyte/issues/68136). So, chart 1.9.1 is Helm chart V1, not V2.soma chandra sekhar attaluri
11/26/2025, 6:48 PMkapa.ai
11/26/2025, 6:48 PMkapa.ai
11/26/2025, 6:49 PMvalues.yaml file [Upgrade to Helm chart V2 (Self-Managed Enterprise)](https://docs.airbyte.com/platform/enterprise-setup/chart-v2-enterprise). ### 3. Configuration Improvements - Many configuration options that required environment variables in V1 now have dedicated fields in V2, making configuration clearer and less error-prone. For example, node selectors and resource requests are now set directly in the values file, not as environment variables [Update your values.yaml file](https://docs.airbyte.com/platform/enterprise-setup/chart-v2-enterprise#update-your-valuesyaml-file). ### 4. Authentication - Helm chart V2 does not require Keycloak for authentication and supports generic OIDC, which is not possible with V1 [Upgrade to Helm chart V2 (Self-Managed Enterprise)](https://docs.airbyte.com/platform/enterprise-setup/chart-v2-enterprise). --- ### Can you use V1 instead of V2? - You can use Helm chart V1 with Airbyte 2.0.x, but you will not be able to upgrade to Airbyte 2.1 or later without migrating to Helm chart V2. Airbyte strongly encourages migrating to V2 as soon as practical to avoid blocking future upgrades and to benefit from improved configuration and features. ### Disadvantages of using Helm chart V1: - No support for Airbyte 2.1 and later. - Fewer configuration options and less alignment with Helm best practices. - More reliance on environment variables for configuration, which can be error-prone. - No support for generic OIDC authentication without Keycloak. - Potential for documentation and community support to focus on V2 going forward. In summary: Helm chart V1 is only suitable for legacy deployments and short-term use. For long-term support, new features, and future upgrades, you should migrate to Helm chart V2 [Final version with Helm chart V1 support](https://docs.airbyte.com/release_notes/v-2.0#final-version-with-helm-chart-v1-support) [Upgrade to Helm chart V2 (Self-Managed Enterprise)](https://docs.airbyte.com/platform/enterprise-setup/chart-v2-enterprise).soma chandra sekhar attaluri
11/26/2025, 6:52 PMkapa.ai
11/26/2025, 6:52 PMkapa.ai
11/26/2025, 6:52 PMvalues.yaml). - Easier customization and management of deployments. - No requirement for Keycloak for authentication; generic OIDC is supported in V2. - Ingress can now be managed directly via the chart in V2, rather than requiring manual setup [Upgrade to Helm chart V2 (Self-Managed Enterprise)](https://docs.airbyte.com/platform/enterprise-setup/chart-v2-enterprise) [Other improvements](https://docs.airbyte.com/release_notes/v-2.0#other-improvements). However, the Airbyte application features (such as connectors, UI capabilities, etc.) are not limited by the chart version. The main risk of staying on Helm chart V1 is that you will not be able to upgrade to Airbyte 2.1 or later, and you will miss out on future improvements, bug fixes, and new features as the project evolves [Final version with Helm chart V1 support](https://docs.airbyte.com/release_notes/v-2.0#final-version-with-helm-chart-v1-support). Summary: You are not missing any Airbyte application features by using Helm chart V1 instead of V2, but you are missing out on improved deployment/configuration options and will be unable to upgrade to future Airbyte versions.