Summary
The user is facing an issue with path prefix configuration in Airbyte Community Edition deployed in EKS using Helm. The user has set up an ingress with a path prefix ‘/airbyte’ but is encountering a 404 Not Found error as the path prefix is not being maintained in the URLs. The user is seeking tips to fix this issue.
Question
Hello new here attempting to setup airbyte community edition in EKS with helm and face issue on the path prefix fixing…
helm airbyte APP version : 0.64.3
i have an web application as pod having ingress with path {my-domain}/airbyte prefix. i am using ALB to handle the ingress with configuration as such:
<http://alb.ingress.kubernetes.io/conditions.airbyte|alb.ingress.kubernetes.io/conditions.airbyte>: >
[{"field":"host-header","hostHeaderConfig":{"values":["my-domain"]}}]
<http://alb.ingress.kubernetes.io/actions.airbyte|alb.ingress.kubernetes.io/actions.airbyte>: >
{"type":"forward","forwardConfig":{"targetGroups":[{"serviceName":"airbyte-airbyte-webapp-svc","servicePort":"80","weight":100}]}}
spec:
ingressClassName: alb
rules:
- http:
paths:
- path: /airbyte
pathType: Prefix
backend:
service:
name: airbyte
port:
name: use-annotation```
and helm `global.airbyteUrl` set to `my-domain/airbyte/` .
once upgrading the helm the endpoint url is considered healthy, but when i surf it the path prefix is still maintain at
`my-domain/assets/all-the-page.js` ( this return error 404 Not Found )
instead of expected
`my-domain/airbyte/assets/all-the-page.js`
is there anything i've done wrong? appreciate any tips in fixing the path issue.
<br>
---
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1726208463285079) if you want
to access the original thread.
[Join the conversation on Slack](https://slack.airbyte.com)
<sub>
["airbyte-community-edition", "EKS", "Helm", "path-prefix", "ALB", "404-error"]
</sub>