Metaflow's event triggering makes it possible to start flows deployed on Argo Workflows when an event is published to an event backend.
To make publishing work, two preconditions must be met:
Metaflow configuration needs to be available in the environment that uses
ArgoEventtries to call the webhook deployed in the Kubernetes cluster based on the address set in a config variable
ARGO_EVENTS_WEBHOOK_URL(you can override it with the
ArgoEvent). Hence this URL must be accessible from the calling environment.
One approach is to use our port forwarding script which piggybacks on the
kubectlauthentication to create a secure connection to the cluster. If you don't want to use port forwarding, you must ensure that the URL is accessible to the caller otherwise.