A workflow is a definition of execution of functions. It defines the order of execution of multiple dependent steps in a DAG. A workflow can reference the project’s params, secrets, artifacts, etc. It can also use a function execution output as a function execution input (which, of course, defines the order of execution).
MLRun supports running workflows on a
kubeflow pipeline engine. The
local engine runs the workflow as a
local process, which is simpler for debuggimg and running simple/sequential tasks. The
kubeflow (“kfp”) engine runs as a task over the
cluster and supports more advanced operations (conditions, branches, etc.). You can select the engine at runtime. Kubeflow-specific
directives like conditions and branches are not supported by the
See full details in Project Workflows and Automation.