Hello 👋 Having scoured the channel and gone through the issues open on the github repo I see that

nodeSelector

is exposed via the kubernetes CLI. I was wondering if: 1. It would be possible to expose

nodeAffinity

(and anti affinity?) as well? 2. If we could allow specifying an init container too? I am happy to open Github issues for these as feature requests and can contribute to making the updates needed for this as well. Just wanted to check here if there is anything that I have missed and if these have been considered already and deemed to be not worth doing. The use case particularly for

nodeAffinity

is that we'd like an order of precedence for our nodes, eg: schedule on an

L40s

accelerator with priority

X

, schedule on

L4

with priority

Y

, schedule on

T4

with priority

Z

, etc. Reason for ☝️ is that we've found that the

L40s

instance types are often not available (even on demand 🫠 ) so would love to have fallbacks. If there already is a way to do this, then happy to be directed towards that! thankyou