Member-only story
ArgoWorkflow: First Deployment
Argo workflows is a workflow engine for executing DAGs of tasks on Kubernetes. It is implemented as Kubernetes CRDs (Custom Resource Definitions) and container-native workflows.
Target Deployment
We will deploy argo workflows 0.41.4 with s3 access for artifacts. As of August 12th, 2024, the most recent version is 0.41.14. However, we will use 0.41.4. For the object storage, we will use Ceph RGW for this deployment. However, any s3-compatible object storage should be fine.
Namespace argo-workflows is where the argo workflows package (mainly argo workflows server and controller) will be installed. Namespace argo-events is where application developers will create actual workflows.
Preparation
First, we need to set up an object storage. We used an Ceph RGW. Detailed instructions on how to set one up, please see Ceph RGW section in this Ceph article. This step should provide an s3 storage access information: an endpoint, an access key and a secret key. They will be used for a Kubernetes configmap and secret in the next step.
Before helm installation, we need to prepare a config map and a secret. So, we will create namespaces and set up them first.
---
apiVersion: v1
kind: Namespace
metadata:
name: argo-workflows
labels…
