Workload Launcher Fail to Resolve Temporal Host

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

Issue with resolving temporal host in the new architecture of OSS Airbyte


Question

Heya, anyone encounter workload launcher fail to resolve the temporal host? trying out the new architecture of OSS Airbyte


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["workload-launcher", "temporal-host", "oss-airbyte", "architecture"]
2

Unable to resolve host stag-general2-airbyte-fpt-temporal

3

We hosted on K8s with helm and also work with our own temporal service

4

Found the problem, as we are using our own temporal, the actual temporal host value is stored in TEMPORAL_CLOUD_HOST instead of TEMPORAL_HOST,

Wondering is there any way to self specify the TEMPORAL_HOST instead pre set in configmap <airbyte-platform/charts/airbyte/templates/env-configmap.yaml at 1cf382778be76c348003483a842a1395f390f9ed · airbytehq/airbyte-platform · GitHub way>

TEMPORAL_HOST: {{ .Release.Name }}-temporal:{{ .Values.temporal.service.port }}

5

TemporalUtils(configureTemporalNamespace):111 - Skipping Temporal Namespace configuration because Temporal Cloud is in use.
Should expect something in worker launcher

6

This https://github.com/airbytehq/airbyte-platform/commit/8c7617de0b4acd4e895bee61fd31b876b68ca5df|commit has caused OSS Airbyte enforcing the use of Workload which doesn’t work well with Temporal Cloud