@kapa.ai Can you run airbyte community edition off of a shared temporal deployment?

Based on the knowledge sources, this is technically possible but not well-supported or documented. A forum post directly addresses this question: an Airbyte team member confirmed that using an external/shared Temporal instance is believed to be possible, but acknowledged there is no official documentation for it and it is not a prioritized use case. [external Temporal] There are also a few relevant caveats from the knowledge sources: • Temporal Cloud (managed): There is an open GitHub issue describing significant problems when trying to use Airbyte CE 2.x with Temporal Cloud. The issue reports a

ConnectorRolloutApiController

bean initialization failure that prevents the server from starting, even with all Temporal Cloud environment variables correctly configured. The root cause appears to be that certain beans initialize before runtime configuration can be evaluated. [Temporal Cloud issue] • Self-hosted shared Temporal: The Helm chart does support disabling the bundled Temporal deployment (

temporal.enabled: false

) and pointing to an external instance, but there is no official documentation on the exact steps required. • High availability / clustering: The bundled Temporal deployment in the Helm chart does not support Temporal's clustering capabilities, meaning a true HA Temporal setup is not supported out of the box. [HA Temporal issue] In summary, while it may be technically feasible to point Airbyte CE at a shared Temporal deployment, there is no official documentation or guaranteed support for this configuration, and known issues exist particularly with Temporal Cloud integration. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.