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

Flyte

Hey, I was thinking about adding `nodeSelector` to the Pod template propeller uses to create pods. Currently I am only using tolerations to allow my pods to schedule on certain nodes. However, let’s say I have multiple node pools for e.g., CPU/GPU tasks and I want to be verbose about which node I want to run my workloads on. Is tolerations sufficient or would I benefit from using `nodeSelectors`? It would be a fun contribution to work on, if you also think it would add value. This could e.g., be added in the `@task` decorator by the same means you are adjusting `requests/limits`. Let me know what you think! :slightly_smiling_face:

<@U038FT3LCRE> why not use pod tasks in this case

So Flyte has pods as a first class citizen for this reason

We want to keep @task default to be vanilla container as it open up great. Optimizations- more to come 

Didn't know about Pod tasks! Interesting :) can you point me to some nice example?

<https://docs.flyte.org/projects/cookbook/en/stable/auto/integrations/kubernetes/pod/index.html|https://docs.flyte.org/projects/cookbook/en/stable/auto/integrations/kubernetes/pod/index.html>