Mogileeswar
12/04/2025, 5:07 PMkapa.ai
12/04/2025, 5:08 PMairbyte-server, not by a separate webapp service. Your ALB ingress should point / to the server service, and a separate path to the connector builder service. [[Ingress via Helm](https://docs.airbyte.com/platform/deploying-airbyte/integrations/ingress#option-1-use-airbytes-helm-chart)] For Helm v2, the recommended values.yaml ingress section looks like: yaml ingress: enabled: true className: "alb" # or nginx, etc. annotations: { } hosts: - host: <http://airbyte.example.com|airbyte.example.com> paths: - path: / pathType: Prefix backend: server # routes to airbyte-server - path: /connector-builder pathType: Prefix backend: connector-builder-server If you’re still seeing a webapp pod even though webapp.enabled is false, the docs and issues don’t explain this behavior; they only state that from 1.8 onward there is no longer an airbyte-webapp image and it’s not independently deployable. [[Ingress 1.7+](https://docs.airbyte.com/platform/deploying-airbyte/integrations/ingress-1-7); [Missing WEBAPP_URL issue](https://github.com/airbytehq/airbyte/issues/68659)] Given the sources, I can’t see why a webapp pod would still be created on Helm v2 with webapp.enabled: false. To move forward based on the docs: 1. Ensure your ingress is using backend: server for / and backend: connector-builder-server for the builder path as above. [[Ingress via Helm](https://docs.airbyte.com/platform/deploying-airbyte/integrations/ingress#option-1-use-airbytes-helm-chart)] 2. Ignore/remove any webapp-targeting ingress rules (they’re obsolete from 1.8+). [[Ingress 1.7+](https://docs.airbyte.com/platform/deploying-airbyte/integrations/ingress-1-7#deploying-with-helm)] 3. If the 404 persists on /, double‑check that the ingress really targets the airbyte-*-server-svc service (not webapp-svc) in the generated Kubernetes Ingress resource. [[abctl ingress issue](https://github.com/airbytehq/airbyte/issues/65539)] If you can share your actual values.yaml ingress section and the generated kubectl get ingress -o yaml, that would help pinpoint whether the chart is still wiring something to webapp-svc.Mogileeswar
12/04/2025, 5:08 PMkapa.ai
12/04/2025, 5:08 PMkapa.ai
12/04/2025, 5:09 PM/ with Helm v2 almost always comes from Ingress still pointing to the wrong backend service or path, even if your values.yaml looks correct. From the official Helm v2 ingress config, / must route to the server backend (which resolves to *-airbyte-server-svc), and the connector builder must be on its own path. [[Helm v2 ingress](https://docs.airbyte.com/platform/deploying-airbyte/integrations/ingress#option-1-use-airbytes-helm-chart)] Example (what Airbyte expects): yaml ingress: enabled: true className: "alb" # or nginx, etc. hosts: - host: <http://airbyte.example.com|airbyte.example.com> paths: - path: / pathType: Prefix backend: server - path: /connector-builder pathType: Prefix backend: connector-builder-server Given you “have same above setup but still coming 404”, the next step (per the docs and related issues) is to inspect the generated Ingress and services, because Helm values can be correct while the rendered Ingress still targets the wrong service (e.g., *-airbyte-webapp-svc). [[abctl ingress target bug](https://github.com/airbytehq/airbyte/issues/65539)] Please run and check: bash kubectl get ingress -n <your-namespace> -o yaml kubectl get svc -n <your-namespace> Verify in the Ingress YAML that: - The / rule’s backend service name is ...-airbyte-server-svc (not webapp-svc). [[Ingress 1.7+ examples](https://docs.airbyte.com/platform/deploying-airbyte/integrations/ingress-1-7#deploying-with-helm)] - The connector builder path points to ...-airbyte-connector-builder-server-svc. [[Ingress 1.7+ examples](https://docs.airbyte.com/platform/deploying-airbyte/integrations/ingress-1-7#deploying-with-helm)] If the generated Ingress is still pointing to webapp-svc or some other service, that matches the known mis‑targeting behavior described in the issue, and you’ll need to correct the Ingress to target *-airbyte-server-svc. [[abctl ingress target bug](https://github.com/airbytehq/airbyte/issues/65539)] The knowledge sources don’t provide more specific troubleshooting steps beyond checking and fixing those Ingress backends, so if your Ingress already matches this exactly and you still get 404, that’s outside what the current docs and issues cover.