Hi team! I am experiencing an unexpected behavior ...
# ask-metaflow
e
Hi team! I am experiencing an unexpected behavior with Metaflow and ArgoWorkflows, where the flows will belong to a production namespace by default, and no matter what I do. As a result, it is not possible to leverage the user namespaces with remote flows. And this is causing troubles with authorization tokens on occasion, that create friction with my devs. Am I missing something? Should I use
--with kubernetes run
instead of
argo-workflows trigger
?