Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

Cross-posting here: Can anyone tell me what the impact of configuring a `node-selector` on the <https://docs.flyte.org/en/latest/deployment/configuration/generated/flytepropeller_config.html#k8s-array-k8s-config|k8s-array plugin> is? Does this affect the pods that are spun up to fulfill a `map_task` or something else?

it’s a k8s <https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#nodeselector|node selector>. you set it if you want to run map task on certain nodes

So does this mean that the pods spun up by the map_task will use that node? Or is this for the pod that manages the map_task itself?

Our use case is that we have a `@dynamic` that launches a `map_task`. We have a default `node-selector` configured on our k8 plugin that assigns tasks to nodes spun up by karpenter with the corresponding label attached, but it's not clear how the k8s-array node selector would be used here

&gt; So does this mean that the pods spun up by the map_task will use that node?
Correct