Hi! I was looking into running my metaflow generated argo-workflows within gVisor pods. I don't see an easy way to set

podSpecPatch

in the generated manifest from inside metaflow. Is there a recommended way to do this? I see that the template is already using podSpecPatch but not exposing it.

I had a similar question a while back about setting some fields that weren't exposed too. savin suggested using a mutating admission webhook to inject the changes I was looking for. I ended up doing something like that via kyverno and it's worked out well. Maybe you can use the same pattern to make the changes you need?

Oh that sounds good. I was considering this as a workaround so I am glad to hear it worked for you. I do wish that more of the argo workflow templating layers were exposed through the api since it would be trivial to just reuse the same .podSpecPath function that they already have. Also this would give me access to node affinity and other kubernetes native paradigms.