Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

<@U04S8PLJWMT> Do we still want the webapp component in Airbyte 2.0? I'm upgrading from airbyte/helm chart version 1.6.0 to helm chart 2.0.19 and it appears the webapp image is not available?

You do **not** need (or want) the separate `webapp` component anymore in Airbyte 2.0.  - Starting in Airbyte **1.7**, the `webapp` service began being merged into `server`.   - As of **1.8**, Airbyte **no longer publishes an `airbyte-webapp` image** and it is **no longer independently deployable**; its functionality is bundled into `airbyte-server` (served on port 8001 by default). [[Ingress 1.7+](<https://docs.airbyte.com/platform/deploying-airbyte/integrations/ingress-1-7>); [1.8 breaking changes](<https://docs.airbyte.com/release_notes/v-1.8#breaking-changes>)] - Community users upgrading to 2.x are expected to update ingress and configuration to point to `airbyte-server` instead of `airbyte-webapp`. [[Breaking changes list](<https://docs.airbyte.com/release_notes/breaking-changes>)]  For Helm chart v2 (e.g. **2.0.19**):  - The presence of `webapp` bits in the chart is legacy; users report that `webapp` should be disabled because it’s no longer required. [[Multiple issues 2.0.0](<https://github.com/airbytehq/airbyte/issues/68134>)] - If you see references to `webapp` in the chart, set `webapp.enabled: false` in your `values.yaml` so it doesn’t try to deploy a non‑existent image. [[Multiple issues 2.0.0](<https://github.com/airbytehq/airbyte/issues/68134>); [Missing WEBAPP_URL](<https://github.com/airbytehq/airbyte/issues/68659>)]  So for your upgrade from chart **1.6.0 → 2.0.19**:  1. **Do not expect a `webapp` image**; that’s expected behavior. 2. **Disable the webapp component** in your Helm values:    ```yaml    webapp:      enabled: false    ``` 3. **Update your ingress** (or any external routing) to send traffic directly to the `airbyte-server` service instead of `airbyte-webapp`. [[Ingress 1.7+](<https://docs.airbyte.com/platform/deploying-airbyte/integrations/ingress-1-7>)]

<@U04S8PLJWMT> How should I configure the global ingress values then? ie, what is the default path expected for the connector-builder-server backend?

In Airbyte 2.0 with the Helm v2 chart, the **global ingress** should route:  - `/` → `server` backend   - `/connector-builder` → `connector-builder-server` backend    as configured in `values.yaml` like this: [[Ingress option 1](<https://docs.airbyte.com/platform/2.0/deploying-airbyte/integrations/ingress#option-1-use-airbytes-helm-chart>)]  ```yaml ingress:   enabled: true   className: "nginx"   annotations: {}   hosts:     - host: <http://airbyte.example.com|airbyte.example.com>       paths:         - path: /           pathType: Prefix           backend: server                 # airbyte-server (UI + API)         - path: /connector-builder           pathType: Prefix           backend: connector-builder-server  # connector-builder-server   tls: [] ```  If you **bring your own ingress** instead of using the Helm-managed one, the connector builder path is expected at `/api/v1/connector_builder/` and should route to the `*-airbyte-connector-builder-server-svc` service. [[BYO ingress](<https://docs.airbyte.com/platform/2.0/deploying-airbyte/integrations/ingress#option-2-bring-your-own-ingress>)]