Hello. Is there a way to add a taint to a KubernetesRun without creating a custom job_template.yaml?

Looks like no. It’s not exposed in KubernetesRun. Your other option is passing the job template as Python, but I think that would be harder than writing the job template

ok, thank you. I see that the default job_template is simple so the risk of mine deviating from future changes is small. all I want is the opportunity to add a taint, so I can control which pool is running the job. all the remaining default args in KubernetesRun are perfect, just the taint missing in my case.

This is something we are talking about internally for 2.0, but generally our stance has been we don’t want to expose every argument in the KubernetesRun because the codebase becomes more complex to maintain also. So we really only expose the most commonly used ones