<@U04S8PLJWMT> I have setup the airbyte on EKS clu...
# ask-ai
r
@kapa.ai I have setup the airbyte on EKS cluster using the helm chart of version 8.5.0. When I am trying to create the custom connector after one time testing it doesn't allow me to update it again if I wanted to I need to create the new custom connector also it converts the UI into the yaml
k
What you're experiencing is a known issue with recent Airbyte versions (including 1.7.x and 1.8.x) deployed via Helm on Kubernetes, where users are unable to edit custom connectors after initial creation, and the Connector Builder UI switches to YAML mode, often accompanied by errors like "An unknown error has occurred." This issue has been reported by multiple users after upgrading from earlier versions (such as 1.6.x) to 1.7.x or later. Even following the official tutorial YAML results in the same problem, and there are no clear error logs to help diagnose it further. The problem does not occur in local quickstart environments, only in Kubernetes/Helm deployments [[Github Issue #65568](https://github.com/airbytehq/airbyte/issues/65568)]. Additionally, a related issue was reported where users received 403 errors or could not edit old connectors, and a temporary workaround was to downgrade to an earlier chart version (e.g., 1.6.3) [[Github Issue #61677](https://github.com/airbytehq/airbyte/issues/61677)]. Key points: - This is a known bug in Airbyte's recent Helm/Kubernetes deployments. - The issue is not present in local (abctl) deployments. - Downgrading to an earlier Helm chart version (such as 1.6.3) is a temporary workaround. - There is no official fix yet for Helm/Kubernetes deployments as of the latest reports. Recommendation: If editing custom connectors is critical for your workflow, consider downgrading your Airbyte deployment to a Helm chart version prior to 1.7.x (such as 1.6.3) until a fix is released. You can track progress and updates on the official GitHub issues linked above. If you need guidance on downgrading or further troubleshooting, let me know!
r
@kapa.ai any reference document
k
A message from kapa.ai
Yes, there are several reference documents in the knowledge sources that discuss the issue you're experiencing with editing custom connectors in Airbyte after upgrading and deploying via Helm on Kubernetes. Users have reported that after upgrading to Airbyte versions 1.7.x and above, they are unable to edit or update custom connectors, and the Connector Builder UI often switches to YAML mode with errors. This issue is documented in detail in the following GitHub issue, where users describe the exact symptoms you mentioned and discuss workarounds such as downgrading to an earlier version (e.g., 1.6.3) to restore functionality: - Users report being unable to edit or create custom connectors after upgrading, and the UI switches to YAML mode. The problem is specific to Kubernetes/Helm deployments and does not occur in local quickstart environments. Downgrading to an earlier version is suggested as a workaround [[Github Issue #65568](https://github.com/airbytehq/airbyte/issues/65568)]. - Another related issue describes similar symptoms and confirms that downgrading to an earlier chart version (such as 1.6.3) allows users to continue working while waiting for a fix [[Github Issue #61677](https://github.com/airbytehq/airbyte/issues/61677)]. These references provide direct documentation of the problem and the current state of workarounds. If you need more details or step-by-step instructions, please let me know!
r
@kapa.ai the <http://<airbyte%20url>/api/v1/connector_builder_projects/resolve|http://<airbyte url>/api/v1/connector_builder_projects/resolve> is not working even after I have exposed the connector endpoint
k
A message from kapa.ai
If the endpoint
/api/v1/connector_builder_projects/resolve
is not working even after exposing the connector endpoint, there are a few important points to consider based on the knowledge sources: 1. Correct Ingress Routing is Critical: Many users have reported that issues with the Connector Builder endpoints (including
/resolve
) are often due to incorrect Kubernetes Ingress configuration. The Ingress must specifically route
/api/v1/connector_builder/
(note the trailing slash) to the
airbyte-airbyte-connector-builder-server-svc
service. If this is not set up, requests may be routed to the wrong service (such as the webapp), resulting in 404 or 5xx errors [[Ingress Example](https://docs.airbyte.com/platform/1.8/deploying-airbyte/integrations/ingress-1-7#deploying-with-helm)]. Example Ingress snippet:
Copy code
yaml    - 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 rule for
/api/v1/connector_builder/
comes before the catch-all
/
rule. 2. Endpoint Path Differences: The endpoint you mentioned (
/api/v1/connector_builder_projects/resolve
) is different from the one most commonly referenced in the documentation and issues (
/api/v1/connector_builder/manifest/resolve
). If your frontend is calling
/api/v1/connector_builder_projects/resolve
, ensure that your Airbyte version actually supports this endpoint, as some versions may have changed the API path [[Github Issue #65568](https://github.com/airbytehq/airbyte/issues/65568)]. 3. Version Compatibility: There have been reports of frontend/backend mismatches in certain Airbyte versions, where the frontend calls an endpoint that does not exist in the backend, resulting in 404 errors. This was especially noted in Airbyte 1.7.1, but similar issues may persist in later versions if the frontend and backend are not in sync [[Github Issue #63770](https://github.com/airbytehq/airbyte/issues/63770)]. 4. Service Health: Ensure that the
airbyte-connector-builder-server
pod is running and healthy. If the service is not up, the endpoint will not be reachable even with correct ingress rules. Summary: - Double-check your Ingress rules to ensure
/api/v1/connector_builder/
is routed to the correct service. - Verify that your Airbyte version supports the
/api/v1/connector_builder_projects/resolve
endpoint. - Make sure all relevant pods are running and healthy. - If the issue persists, it may be due to a frontend/backend version mismatch or a bug in your Airbyte version. If you have already done all of the above and the endpoint still does not work, the knowledge sources do not provide a more specific solution for this exact endpoint, and you may need to consult the Airbyte GitHub issues for updates or consider downgrading to a version where the Connector Builder is known to work as expected.
r
@kapa.ai Now I have used the /api/v1/connector_builder/manifest/resolve endpoint and it shows now 405 error
k
A message from kapa.ai
A 405 error on the
/api/v1/connector_builder/manifest/resolve
endpoint typically means that the HTTP method used (e.g., GET, POST) is not allowed for that endpoint. According to the knowledge sources, this endpoint is expected to be accessed via a POST request by the Connector Builder UI when testing or validating a connector [[Github Issue #63770](https://github.com/airbytehq/airbyte/issues/63770)]. Key things to check: 1. Ingress Configuration: Ensure your Kubernetes Ingress is correctly routing all
/api/v1/connector_builder/
traffic to the
airbyte-airbyte-connector-builder-server-svc
service. If this is misconfigured, requests may be routed to the wrong service, which could return a 405 error [[Ingress Example](https://docs.airbyte.com/platform/1.8/deploying-airbyte/integrations/ingress-1-7#deploying-with-helm)]. 2. HTTP Method: Make sure the request to
/api/v1/connector_builder/manifest/resolve
is a POST request, as this is the expected method for this endpoint. 3. Path Suffix: The path in your Ingress should be
/api/v1/connector_builder/
(with a trailing slash) to ensure all subpaths, including
/manifest/resolve
, are routed correctly [[Github Issue #61677](https://github.com/airbytehq/airbyte/issues/61677)]. 4. Service Health: Confirm that the
airbyte-connector-builder-server
pod is running and healthy. If all of the above are correct and you are still seeing a 405 error, the knowledge sources do not provide further troubleshooting steps for this specific error. The most common root cause in similar reports has been incorrect Ingress routing or using the wrong HTTP method. If you need an example Ingress configuration, here is a reference:
Copy code
yaml - 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
[[Ingress Example](https://docs.airbyte.com/platform/1.8/deploying-airbyte/integrations/ingress-1-7#deploying-with-helm)] If you continue to experience issues, please provide more details about your Ingress configuration and the exact request being made.