Internal Server Error: java.net.UnknownHostExcepti...
# ask-ai
n
Internal Server Error: java.net.UnknownHostException: airbyte-abctl-airbyte-connector-builder-server-svc.airbyte-abctl
k
The error
java.net.UnknownHostException: airbyte-abctl-airbyte-connector-builder-server-svc.airbyte-abctl
indicates that the Airbyte deployment is trying to route traffic to the
airbyte-abctl-airbyte-connector-builder-server-svc
service, but this service does not exist in your Kubernetes namespace. This is a known issue reported by several users after upgrading Airbyte or using certain abctl/Helm chart versions. From the knowledge sources: - Users have reported that after installing Airbyte with abctl (e.g., v0.30.1) and Helm chart version 2.0.15 (App Version 1.8.4+), the
airbyte-abctl-airbyte-connector-builder-server-svc
service is missing, even though the ingress is configured to route
/api/v1/connector_builder
to it. Only a few services are present:
airbyte-abctl-airbyte-server-svc
,
airbyte-abctl-temporal
, and
airbyte-abctl-workload-api-server-svc
[[source]](https://github.com/airbytehq/airbyte/issues/66759). - This results in errors like:
Copy code
/api/v1/connector_builder   airbyte-abctl-airbyte-connector-builder-server-svc:http (<error: services "airbyte-abctl-airbyte-connector-builder-server-svc" not found>)
and
Copy code
Internal Server Error: java.net.UnknownHostException: airbyte-abctl-airbyte-connector-builder-server-svc.airbyte-abctl
[[source]](https://github.com/airbytehq/airbyte/issues/65539) - A suggested workaround (not a fix for the missing service, but for a related ingress issue) is to explicitly enable the webapp in your `values.yaml`:
Copy code
yaml   webapp:     enabled: true     image:       tag: 1.7.8       repository: airbyte/webapp       pullPolicy: IfNotPresent
However, this does not create the missing connector builder service itself [[source]](https://github.com/airbytehq/airbyte/issues/65539). - The root cause appears to be that the Helm chart or abctl installation does not always deploy the connector builder service, but the ingress expects it to exist. This is a deployment/configuration issue, not a DNS/networking issue. What you should do: - Check your Helm values and deployment configuration to ensure the connector builder component is enabled. - If you are using abctl, be aware that some versions may not deploy all required services by default. - Monitor the Airbyte GitHub issues for updates or fixes regarding this missing service, as it is a known problem. If you need the connector builder, you may need to manually adjust your deployment or wait for an updated abctl/Helm chart that resolves this issue. The knowledge sources do not provide a definitive fix for creating the missing service, only workarounds and confirmation of the issue.