I've been looking at Argo Workflows for small CI projects. Reusable pipelines outside the repository and a snappy UI are appealing, but Git platform integration and the number of Kubernetes resources involved feel cumbersome.
What makes it worth using for CI? Do you use it with Argo Events or without, and does it make more sense for other kinds of workflows?
The separation from repositories is a good reason if you want to reuse pipeline definitions or restrict who can change them. Whether that's worth the extra Kubernetes setup is a different question, especially for small projects.
Argo Events does have an event source for GitHub. That gives you an option beyond starting and waiting for a workflow from another CI system, though you still have the event setup to manage.
CI isn't the only reason to use it. Argo Workflows can run asynchronous processing, with Argo Events triggering some jobs and CronWorkflows scheduling others. WorkflowTemplates with defined inputs can also be used to start business processes.
That kind of workload may make the Kubernetes-native setup more useful than it feels for a handful of small CI pipelines.
Answers are reviewed before publication.
pencilcase_undertaker:
That general-purpose side sounds interesting. Is it comparable to a business process tool such as Camunda?