Hi we have ~probably~ definitely used outerbound provided <h Outerbounds #ask-metaflow

Hi, we have probably definitely used outerbound pr...

fast-vr-44972

06/28/2023, 8:03 PM

Hi, we have ~~probably~~ definitely used outerbound provided terraform set-up for our internal metaflow on EKS with argo. What I see is all the scheduled flows are running inside

default

namespace even though there is an

argo

namespace? Is this expected?

fast-vr-44972

06/28/2023, 8:05 PM

I feel like this might be the reason behind these issues we are facing like • No trigger based on another flow • No slack notification

ancient-application-36103

06/28/2023, 9:07 PM

The latest release of Metaflow addresses the bug that prevented you from using a later version of metaflow. Have you been able to try out @User’s recommendation in that thread.

ancient-application-36103

06/28/2023, 9:09 PM

re: trigger based on other flows -

metaflow configure kubernetes

will ask you questions to configure your event related configuration. once you execute that, you will see some extra entries in

~/.metaflowconfig/config.json

Copy code

"METAFLOW_ARGO_EVENTS_EVENT": "xxx",
"METAFLOW_ARGO_EVENTS_EVENT_BUS": "xxx",
"METAFLOW_ARGO_EVENTS_EVENT_SOURCE": "xxx",
"METAFLOW_ARGO_EVENTS_SERVICE_ACCOUNT": "xxx",
"METAFLOW_ARGO_EVENTS_WEBHOOK_URL": "xxx",

ancient-application-36103

06/28/2023, 9:10 PM

re: scheduled flows running in

default

namespace - you can change the namespace your workflow gets deployed to by adding

METAFLOW_KUBERNETES_NAMESPACE=some-namespace

~/.metaflowconfig/config.json

9 Views

Open in Slack

Previous Next