Hi @kapa.ai is temporal required for airbyte helm kubernetes installation ?

Yes, Temporal is required for Airbyte's Helm Kubernetes installation. Temporal is a system that Airbyte uses for orchestrating jobs. It is a part of the Airbyte's architecture and is included in the Helm chart for Kubernetes deployment. The Airbyte Worker pod uses local ports to connect to the various Job pods, which are managed by Temporal. In the Helm chart, the

TEMPORAL_WORKER_PORTS

environment variable defines the local ports the Airbyte Worker pod uses to connect to the various Job pods. By default, ports 9001 - 9040 are exposed in the Helm Chart [^1^]. Also, it's important to note that there have been discussions and issues related to configuring Temporal in the Helm chart, such as adding an

externalTemporal

section in values.yaml and conditionally template the Temporal deployment [^2^]. There are also issues related to the version of Temporal used in Airbyte's Helm chart [^5^][^7^]. [^1^]: (https://docs.airbyte.com/operator-guides/configuring-airbyte#worker-1) [^2^]: (https://github.com/airbytehq/airbyte/issues/13212) [^5^]: (https://github.com/airbytehq/airbyte/issues/30973) [^7^]: (https://discuss.airbyte.io/t/4432)

@kapa.ai i am getting this error

sql schema version compatibility check failed: pq: database "temporal" does not exist

A message from kapa.ai

The error message

sql schema version compatibility check failed: pq: database "temporal" does not exist

indicates that the Temporal service is unable to find the "temporal" database. This could be due to a few reasons: 1. The database "temporal" does not exist in your PostgreSQL instance. You might need to create it manually or ensure that the setup scripts have run correctly. 2. The database connection details provided to the Temporal service are incorrect. You should verify that the hostname, port, username, and password are correct and that the user has the necessary permissions to access the "temporal" database. 3. There might be network issues preventing the Temporal service from reaching your PostgreSQL instance. In the knowledge sources, there are several instances of similar issues. For example, in one case, the user was unable to start the server due to a SQL schema version compatibility check failure[^1^]. In another case, the user was unable to connect to an external database[^4^]. You might want to check the logs of your Temporal service for more detailed error messages. If you're using Docker, you can use the command

docker logs <container_id>

to view the logs. [^1^]: (https://github.com/airbytehq/airbyte/issues/26647) [^4^]: (https://discuss.airbyte.io/t/1544)

@kapa.ai i am not able to connect to my webapp from outside world with Kubernetes helm airbyte

A message from kapa.ai

Connecting to the Airbyte webapp from outside your Kubernetes cluster requires proper configuration of your services and potentially setting up Ingress rules, depending on your Kubernetes environment. Here are some steps you can follow: 1. Check your service configuration: Ensure that your

airbyte-webapp-svc

is correctly configured and that it's accessible within your Kubernetes cluster[^1^]. You can check this by running

kubectl describe svc airbyte-webapp-svc

in your Kubernetes cluster. 2. Port Forwarding: If you're trying to access the webapp for testing or development purposes, you can use

kubectl port-forward

to access the service[^2^]. However, this is not a suitable solution for production environments as it requires the command to be running continuously. 3. Ingress Controller: For production environments, you might need to set up an Ingress controller to manage external access to services in your cluster[^3^]. This will allow you to access the webapp using a domain name or IP address. 4. Network Policies: Ensure that there are no network policies preventing access to the `airbyte-webapp-svc`[^4^]. 5. Firewall Rules: If you're running your Kubernetes cluster in a cloud environment, you might need to check your cloud provider's firewall rules to ensure that incoming connections are allowed. If you're still having trouble, please provide more details about your Kubernetes environment and the exact steps you've taken so far. [^1^]: (https://discuss.airbyte.io/t/704) [^2^]: (https://discuss.airbyte.io/t/704) [^3^]: (https://discuss.airbyte.io/t/704) [^4^]: (https://discuss.airbyte.io/t/2661)