Hi folks! Are there any Airbyte (and Temporal) modules that cannot be running in parallel on different Kubernetes nodes? My scenario is an on-premise cloud that has two Kubernetes (in different data centers) aiming for fault tolerance.

Based on the information provided in the extracts, Airbyte allows scaling sync workloads horizontally using Kubernetes. The core components (api server, scheduler, etc) run as deployments while the scheduler launches connector-related pods on different nodes [source](https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm). However, there is no specific information about running Airbyte and Temporal modules in parallel on different Kubernetes nodes for fault tolerance. It's important to note that when scaling Airbyte on Kubernetes, you need to ensure that the Kubernetes cluster can accommodate the number of pods Airbyte creates. As a rule of thumb, the Kubernetes cluster should be able to schedule up to

2 x <number-of-possible-concurrent-connections>

pods at once [source](https://docs.airbyte.com/operator-guides/scaling-airbyte). For more specific details about your scenario, you might want to refer to the official Airbyte documentation or reach out to the Airbyte community for further assistance.