version: 7.0.4 type: DeclarativeSource check: ...
# ask-ai
n
version: 7.0.4 type: DeclarativeSource check: type: CheckStream stream_names: - neeraj api test streams: - type: DeclarativeStream retriever: type: SimpleRetriever record_selector: type: RecordSelector extractor: type: DpathExtractor field_path: - results requester: type: HttpRequester http_method: GET url: https://randomuser.me/api/ decoder: type: JsonDecoder name: api test - type: DeclarativeStream retriever: type: AsyncRetriever record_selector: type: RecordSelector extractor: type: DpathExtractor field_path: [] creation_requester: type: HttpRequester http_method: GET url: https://randomuser.me/api/ polling_requester: type: HttpRequester http_method: GET download_requester: type: HttpRequester http_method: GET status_mapping: type: AsyncJobStatusMap running: [] completed: [] failed: [] timeout: [] status_extractor: type: DpathExtractor field_path: [] download_target_extractor: type: DpathExtractor field_path: [] decoder: type: CsvDecoder encoding: utf-8 delimiter: "," name: neeraj api test spec: type: Spec connection_specification: type: object properties: {} metadata: autoImportSchema: neeraj api test: true api test: true getting issue Internal Server Error: java.net.UnknownHostException: airbyte-abctl-airbyte-connector-builder-server-svc.airbyte-abctl: Name or service not known
k
Your error message:
Copy code
Internal Server Error: java.net.UnknownHostException: airbyte-abctl-airbyte-connector-builder-server-svc.airbyte-abctl: Name or service not known
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 that has been reported by other users when deploying Airbyte with
abctl
and certain Helm chart versions. The root cause is that the connector builder service is expected by the ingress and/or the Airbyte UI, but is not deployed by default in some configurations or chart versions. Key points from the knowledge sources: - The ingress configuration for Airbyte 1.7+ expects the
airbyte-connector-builder-server-svc
service to exist and be routable for the Connector Builder UI to function properly. If this service is missing, you will see errors like the one you reported [[Update ingress for version 1.7 and later](https://docs.airbyte.com/platform/deploying-airbyte/integrations/ingress-1-7#deploying-with-helm)]. - Multiple users have reported that, after deploying with
abctl
and Helm chart version 2.0.15 (App Version 1.8.x), the
airbyte-abctl-airbyte-connector-builder-server-svc
is missing, leading to ingress and UI errors [[Github Issue 66759](https://github.com/airbytehq/airbyte/issues/66759)]. - A suggested workaround is to explicitly enable the webapp in your
values.yml
file, which may help resolve missing services in some cases. For example:
Copy code
yaml   webapp:     enabled: true     image:       tag: 1.7.8       repository: airbyte/webapp       pullPolicy: IfNotPresent
[[Github Issue 65539](https://github.com/airbytehq/airbyte/issues/65539)] What you should do: 1. Check your Helm values: Ensure that the connector builder and webapp components are enabled in your Helm values file. 2. Upgrade abctl and Helm chart: If possible, upgrade to the latest versions of
abctl
and the Airbyte Helm chart, as this issue may have been addressed in newer releases. 3. Manually deploy the missing service: If the service is still missing, you may need to manually deploy or enable the connector builder server as per the official documentation or by adjusting your Helm values. Summary: Your error is due to a missing Kubernetes service (
airbyte-abctl-airbyte-connector-builder-server-svc
) that is required for the Connector Builder UI. This is a known issue with certain Airbyte deployments using
abctl
and specific Helm chart versions. Review your deployment configuration and consider the workaround above to resolve the issue. If the problem persists, upgrading your deployment tools and chart versions is recommended. If you need more detailed steps for your specific environment, please provide your current
values.yml
or Helm configuration.