Tom Dobson
12/10/2025, 4:12 PMkapa.ai
12/10/2025, 4:12 PMairbyte-v2/airbyte is described as the main Helm chart to deploy Airbyte (the full platform / control plane). [[Deploy Airbyte](https://docs.airbyte.com/platform/deploying-airbyte/chart-v2-community#deploy-airbyte); [Enterprise deploy](https://docs.airbyte.com/platform/enterprise-setup/chart-v2-enterprise#deploy-airbyte)] - airbyte-v2/airbyte-data-plane is described as “A Helm chart for installing an Airbyte Data Plane.” [[Deploy Airbyte](https://docs.airbyte.com/platform/deploying-airbyte/chart-v2-community#deploy-airbyte); [Next deploy](https://docs.airbyte.com/platform/next/deploying-airbyte/chart-v2-community#deploy-airbyte)] Beyond those short descriptions, the knowledge sources you provided do not explain what components are included in the airbyte-data-plane chart, how it is intended to be used relative to the main airbyte chart, or any architectural differences between them. The GitHub issue you shared only confirms that Helm chart V2 and Airbyte “2.0” are separate concerns and links back to the same docs, without further detail on airbyte-data-plane. [[Github issue 68134](https://github.com/airbytehq/airbyte/issues/68134)] So, based solely on these sources: - airbyte chart: deploys the primary Airbyte platform. - airbyte-data-plane chart: separately deploys an “Airbyte Data Plane,” but the exact differences and use cases are not documented in the materials you provided. If you need specifics about what runs where or how to combine these charts, the current knowledge set does not contain enough information to answer confidently.Tom Dobson
12/10/2025, 4:30 PMkapa.ai
12/10/2025, 4:30 PMkapa.ai
12/10/2025, 4:30 PMpostgresql.enabled flag controls whether Helm deploys the bundled Bitnami PostgreSQL instance or not. From the docs and examples: - It is described as: “**Switch to enable or disable the PostgreSQL Helm chart**.” [[Compose/api issue](https://github.com/airbytehq/airbyte/issues/49843)] - Setting postgresql.enabled: false is explicitly used when you want to use an external Postgres (RDS, Cloud SQL, your own Postgres, etc.) instead of the internal one. [[External DB docs 1.8](https://docs.airbyte.com/platform/1.8/deploying-airbyte/integrations/database#values); [Enterprise DB config](https://docs.airbyte.com/platform/enterprise-setup/implementation-guide#configuring-the-airbyte-database)] ### What it does yaml postgresql: enabled: false - Disables deployment of the internal Postgres chart (airbyte/db based on Bitnami PostgreSQL). - Airbyte will then expect database connection details under global.database (for Helm v2) or the older externalDatabase section (for older charts) to point to your own Postgres. [[External DB docs 1.8](https://docs.airbyte.com/platform/1.8/deploying-airbyte/integrations/database#values); [Forum example](https://github.com/airbytehq/airbyte/issues/51036)] yaml postgresql: enabled: true - Enables the bundled Bitnami PostgreSQL sub‑chart so Airbyte runs with an in‑cluster Postgres database, managed by the Helm release. [[Compose/api issue](https://github.com/airbytehq/airbyte/issues/49843)] ### When to set it to true vs false Set postgresql.enabled: true when: - You are fine using the default, in‑cluster Postgres managed by Helm (typical for quick tests / non‑prod). Set postgresql.enabled: false when: - You want to use an external database (AWS RDS, GCP Cloud SQL, your own Postgres in another cluster, etc.). - In that case, you must also configure global.database (host, port, db name, user, and secrets) so Airbyte knows how to connect. [[External DB docs platform](https://docs.airbyte.com/platform/deploying-airbyte/integrations/database#values); [Enterprise DB config](https://docs.airbyte.com/platform/1.8/enterprise-setup/implementation-guide#configuring-the-airbyte-database)]