Summary
Issue with orchestrator pod running on the same worker node in Airbyte deployment via Helm. Question about including pod anti-affinity to distribute load across nodes.
Question
I have some issue about deployed airbyte via helm. I’m facing issue when run sync then the sync job (orchestrator pod) try to run in same worker node or same each other. Could I include pod anti affinity to avoid this or distribute load to every nodes ? (additional infor: I disable workload-api-server and workload-launcher)
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.