Argo Workflow Platform
(Redirected from Argo Workflows)
Jump to navigation
Jump to search
An Argo Workflow Platform is a workflow platform.
- …
- Example(s):
- Argo v2.4.2 (~2019-10-20) [1].
- Argo v2.2.1 (~2018-10-18).
- …
- Counter-Example(s):
- See: Argo Project Tool, Kubernetes.
References
2018
- https://github.com/argoproj/argo
- QUOTE: Argo is an open source container-native workflow engine for getting work done on Kubernetes. Argo is implemented as a Kubernetes CRD (Custom Resource Definition).
- Define workflows where each step in the workflow is a container.
- Model multi-step workflows as a sequence of tasks or capture the dependencies between tasks using a graph (DAG).
- Easily run compute intensive jobs for machine learning or data processing in a fraction of the time using Argo workflows on Kubernetes.
- Run CI/CD pipelines natively on Kubernetes without configuring complex software development products.
- Why Argo?
- Argo is designed from the ground up for containers without the overhead and limitations of legacy VM and server-based environments.
- Argo is cloud agnostic and can run on any kubernetes cluster.
- Argo with Kubernetes puts a cloud-scale supercomputer at your fingertips.
- QUOTE: Argo is an open source container-native workflow engine for getting work done on Kubernetes. Argo is implemented as a Kubernetes CRD (Custom Resource Definition).
2017
- Pratik Wadher. (2017). “Introducing Argo — A Container-Native Workflow Engine for Kubernetes.”
- QUOTE: ... Our first contribution to the Kubernetes ecosystem is Argo, a container-native workflow engine for Kubernetes. You can think of Argo as an engine for feeding and tending a Kubernetes cluster. Argo makes it easy to specify, schedule and coordinate the running of complex workflows and applications on Kubernetes. Argo accomplishes this by combining a workflow engine with native artifact management, admission control, “fixtures”, built-in support for DinD (Docker-in-Docker), and policies. There are several uses for Argo workflows including:
- Traditional CI/CD pipelines
- Complex jobs with both sequential and parallel steps and dependencies
- Orchestrating deployments of complex, distributed applications
- Policies to enable time/event-based execution of workflows
- QUOTE: ... Our first contribution to the Kubernetes ecosystem is Argo, a container-native workflow engine for Kubernetes. You can think of Argo as an engine for feeding and tending a Kubernetes cluster. Argo makes it easy to specify, schedule and coordinate the running of complex workflows and applications on Kubernetes. Argo accomplishes this by combining a workflow engine with native artifact management, admission control, “fixtures”, built-in support for DinD (Docker-in-Docker), and policies. There are several uses for Argo workflows including: