Anyone has ever encountered an issue with connector builder on K8s installation via helm chart v2? We are at version 1.8.5 and (only) the endpoint

/api/v1/connector_builder_projects/read_stream

replies from Airbyte's UI with a 404 - it does also by using the example of API random jokes in the docs

Yes, issues with the Connector Builder returning 404 errors on certain endpoints (including

/api/v1/connector_builder_projects/read_stream

) have been reported by other users running Airbyte on Kubernetes via Helm, especially around versions 1.7.x and 1.8.x. The most common root cause is misconfigured ingress rules. Specifically, if your ingress is not routing requests for

/api/v1/connector_builder

(and related endpoints) to the

airbyte-connector-builder-server-svc

, those API calls will return 404 errors, even though the UI is accessible and other endpoints work. This has been confirmed in several user reports and is not a bug in Airbyte itself, but rather a networking/routing issue in the Kubernetes setup. The fix: You need to ensure your ingress definition explicitly routes

/api/v1/connector_builder/

(note the trailing slash) to the

airbyte-connector-builder-server-svc

service. All other traffic (such as

/

) should go to the

airbyte-server-svc

. Here’s an example from the official documentation:

yaml apiVersion: <http://networking.k8s.io/v1|networking.k8s.io/v1> kind: Ingress metadata:   name: airbyte-ingress spec:   rules:     - host: <http://airbyte.example.com|airbyte.example.com>       http:         paths:           - path: /api/v1/connector_builder/             pathType: Prefix             backend:               service:                 name: airbyte-airbyte-connector-builder-server-svc                 port:                   number: 80           - path: /             pathType: Prefix             backend:               service:                 name: airbyte-airbyte-server-svc                 port:                   number: 8001

Make sure the path for the connector builder ends with a

/

to avoid routing issues with subpaths like

/api/v1/connector_builder_projects/read_stream

 [see discussion here](https://github.com/airbytehq/airbyte/issues/61677). References and further reading: - [Official ingress configuration for 1.7+](https://docs.airbyte.com/platform/deploying-airbyte/integrations/ingress-1-7#deploying-with-helm) - [User report and solution for 404 on builder endpoints](https://github.com/airbytehq/airbyte/issues/61677) - [Another user confirming the fix by routing builder endpoints correctly](https://github.com/airbytehq/airbyte/issues/65568) If you update your ingress as above and still see 404s, double-check that the

airbyte-connector-builder-server-svc

service is running and not disabled (e.g., by low-resource mode). If the service is missing, see [this note](https://github.com/airbytehq/airbyte/issues/66759). In summary: This is a known and common issue, and updating your ingress rules as described should resolve the 404 errors for the Connector Builder endpoints.

yes I have seen that fix, and it doesn't belong to this case. in fact all other endpoints work, and we can see the request being routed to the right pod what happens is that if we run this with no payload, the endpoint replies 500 (meaning it's there but didn't get the right parameters) while adding payload becomes 404