... | @@ -4,6 +4,15 @@ Argo DAG workflows documentation entry: [LINK](https://argoproj.github.io/argo-w |
... | @@ -4,6 +4,15 @@ Argo DAG workflows documentation entry: [LINK](https://argoproj.github.io/argo-w |
|
# Getting started
|
|
# Getting started
|
|
Quick start guide: [LINK](https://argoproj.github.io/argo-workflows/quick-start/)
|
|
Quick start guide: [LINK](https://argoproj.github.io/argo-workflows/quick-start/)
|
|
|
|
|
|
|
|
# Using previous steps' outputs as inputs
|
|
|
|
For Argo workflows to be able to patch inputs and output paths as volumes on each pod, the `ServiceAccountName` used must have enough privileges:
|
|
|
|
|
|
|
|
- Input/Output examples:
|
|
|
|
- [Inputs as artifacts (it requires an artifact registry)](https://argoproj.github.io/argo-workflows/workflow-inputs/#using-previous-step-outputs-as-inputs)
|
|
|
|
- [Inputs as parameters (content of file, not the file itself)](https://stackoverflow.com/questions/71599185/how-to-run-multiple-files-in-one-container-image-and-use-the-output-as-input-in)
|
|
|
|
|
|
|
|
- Patching k8s Roles and RoleBindings to allow this: [LINK](https://github.com/argoproj/argo-workflows/issues/2228)
|
|
|
|
|
|
# Takeaways
|
|
# Takeaways
|
|
- Pros:
|
|
- Pros:
|
|
- DAG natively accepted in the Argo workflows
|
|
- DAG natively accepted in the Argo workflows
|
... | | ... | |