Hi team, is there a way to inject pod priority specs in Metaflow-ArgoWF integration? I want to add a default priority class to all metaflow jobs flowing through Argo WF but I cannot seem to find a way to inject it. My analysis/tests so far: • Metaflow's Argo integration doesn't support

priorityClassName

• Tried adding a default priority class for argo WF, it is also not supported ◦ Argo Workflows supports the

podPriorityClassName

field, but unless the upstream tool (Metaflow) exposes this in its generated Argo manifests, there is no clean injection route • Tried adding

METAFLOW_KUBERNETES_POD_SPEC_OVERRIDE

, this works for direct k8s jobs, but we are running through argoWF, my test failed... • Also adding

priorityClassName

to a WorkflowTemplate (that we can create) using a direct field is not natively available in current Metaflow-Argo integrations... • Also, of course, users cannot add pod specs in their metaflow jobs. Not supported yet Let me know your recommendations, thanks a bunch!!!

if you happen to have new kubernetes and beta features enabled, one other option is to use

MutatingAdmissionPolicy