Workflow engine for Kubernetes
Best practice: As an alternative to specifying sequences of steps in Workflow, you can define the workflow as a directed-acyclic graph (DAG) by specifying the dependencies of each task. The DAG logic has a built-in fail fast feature to stop scheduling new steps, as soon as it detects that one of the DAG nodes has failed. Then it waits until all DAG nodes are completed before failing the DAG itself. The FailFast flag default is true. If set to false, it will allow a DAG to run all branches of the DAG to completion (either success or failure), regardless of the failed outcomes of branches in the DAG.
Argo SSO with PingOne
1 project | dev.to | 14 Jun 2022
How you can run your first Argo Workflow on K3s ?
1 project | dev.to | 18 May 2022
Advisory for Argo Workflows high severity CVE
1 project | reddit.com/r/devopsish | 4 May 2022
Using docker and Kubernetes to process long-running background jobs at scale.
1 project | reddit.com/r/devops | 23 Feb 2022
1 project | dev.to | 28 Jan 2022