https://linen.dev logo
#feedback-and-requests
Title
# feedback-and-requests
c

Christopher Wu

08/26/2021, 12:08 AM
On a Kubernetes deployment, is it possible to specify restrict the nodes that connector pods run on? e.g., connector pods for workspace X run only on nodes for workspace X?
u

user

08/26/2021, 1:29 AM
We just added an env variable that you can use to control connector pods globally. However, it doesn’t allow you to do it on a per-workspace basis.
u

user

08/26/2021, 1:30 AM
What’s the use case here? Is it performance related or security related?
u

user

08/26/2021, 5:27 PM
Security. It is a nice-to-have for us, but not a requirement
n

Nathan Atkins

08/26/2021, 6:44 PM
Can you make an issue for this on Github? No guarantees that we’ll get to it soon (we also have some other security related changes in the pipes like storing configs in a secrets store that we’ll likely work on first).
u

user

08/31/2021, 4:36 AM
For a start, there is
WORKER_POD_TOLERATIONS
https://github.com/airbytehq/airbyte/pull/5585, but that is not tied to a workspace. Not sure how easy/difficult it is to use it for for workspace isolation…
g

gunu

09/01/2021, 5:04 PM
tolerations can prevent pods from being scheduled on certain nodes, but I think I need to specify node affinity for workers so that they can be forced to launch on certain nodes Edit: I was able to get our desired configuration by applying a taint to the nodegroup used for the Airbyte backend containers
u

user

09/25/2021, 4:23 PM
I still think this should be affinity instead of toleration With toleration pods can still schedule on other nodes
2 Views