issue in rest api case Internal Server Error: java...
# ask-ai
n
issue in rest api case Internal Server Error: java.net.UnknownHostException: airbyte-abctl-airbyte-connector-builder-server-svc.airbyte-abctl
k
The error means Kubernetes DNS cannot resolve the service name
airbyte-abctl-airbyte-connector-builder-server-svc.airbyte-abctl
, i.e. that Service does not exist in your cluster/namespace. From the linked issues, there are two distinct situations: 1. Ingress points to connector-builder service that doesn’t exist In several
abctl
installs (v0.30.1, App 1.8.x), the generated Ingress contains a path:
Copy code
yaml    - path: /api/v1/connector_builder      backend:        service:          name: airbyte-abctl-airbyte-connector-builder-server-svc
but only these Services exist in `airbyte-abctl`:
airbyte-abctl-airbyte-server-svc
,
airbyte-abctl-temporal
,
airbyte-abctl-workload-api-server-svc
. [[Connector builder svc missing](https://github.com/airbytehq/airbyte/issues/66759)] In that case, any request to
/api/v1/connector_builder
will fail with
UnknownHostException
for the non‑existent service. 2. Connector Builder now served by
airbyte-server-svc
in newer charts
Official ingress examples for 1.7+ route: -
/api/v1/connector_builder/
→
airbyte-airbyte-connector-builder-server-svc
(when that service exists), and -
/
→
airbyte-airbyte-server-svc
. [[Ingress 1.7+](https://docs.airbyte.com/platform/deploying-airbyte/integrations/ingress-1-7#deploying-with-helm)] But with recent Helm charts used by
abctl
(e.g. 2.0.15, App 1.8.4/1.8.5), the dedicated
connector-builder-server-svc
is no longer created; everything is effectively behind
airbyte-...-server-svc
. [[Connector builder svc missing](https://github.com/airbytehq/airbyte/issues/66759)] Because your error matches the missing‑service pattern, the practical options (based on the issues) are: - Option A – Stop routing to the non‑existent service Edit your Ingress so that
/api/v1/connector_builder
is also routed to the main server service:
Copy code
yaml   - path: /api/v1/connector_builder     pathType: Prefix     backend:       service:         name: airbyte-abctl-airbyte-server-svc         port:           name: http   - path: /     pathType: Prefix     backend:       service:         name: airbyte-abctl-airbyte-server-svc         port:           name: http
This is effectively what one user did to fix 1.8.2/1.8.4 connector‑builder routing issues. [[Ingress routing fix](https://github.com/airbytehq/airbyte/issues/65568)] - Option B – (Hotfix from community) Enable webapp explicitly In some
abctl
versions, the ingress was still trying to use
webapp-svc
. A community hotfix was to re‑enable the webapp via
values.yaml
so the expected service exists again: [[Ingress/webapp hotfix](https://github.com/airbytehq/airbyte/issues/65539)]
Copy code
yaml   webapp:     enabled: true     image:       tag: 1.7.8       repository: airbyte/webapp       pullPolicy: IfNotPresent
However, this addresses missing
webapp
rather than missing connector‑builder specifically; for your
UnknownHostException
on
airbyte-abctl-airbyte-connector-builder-server-svc
, Option A (Ingress change) is the more directly relevant fix. If after updating the Ingress you still see
UnknownHostException
, verify:
Copy code
bash kubectl get svc -n airbyte-abctl kubectl describe ingress ingress-abctl -n airbyte-abctl
and ensure all Ingress backends reference only Services that actually appear in
kubectl get svc
.