3 ms·
I mainly became familiar with Argo Workflows when looking at/lightly evaluating Argo Events to run my home-(k8s)-cluster's Event Driven Architecture (as an esb/
by rektide 6y ago
I mainly became familiar with Argo Workflows when looking at/lightly evaluating Argo Events to run my home-(k8s)-cluster's Event Driven Architecture (as an esb/lambda-architecture/event-fabric/&c system). Also poked at Brigade and Tekton (who sadly are now CI/CD focused, not general EDA) and local Github Actions runners.
Workflow was mentioned in the Argo Events docs a couple times. Events is a pretty general system, but if you need to assemble more complex inter-dependent tasks, they had Workflow integration. I didn't get super far in, look very deep at how the integration worked, or how pleased I was going to be using Workflows, as I was mainly interested in the EDA end to start.
Anyhow, picking through Workflow 3.0, my main interest is:
> Argo Workflows v3.0 comes with a new UI that now also supports Argo Events! The UI is also more robust and reliable.
Really seems like Argo Workflow has been made the over-arching UI for both of these systems in this 3.0 release. There's now some event-flow pages in Workflow 3.0, that will be interesting to check out. I'm very interested in how the APIs have all been updated, how the systems work together. Especially given Argo Event's fall 1.0 release & the new architecture[1].
One other cool feature from the Workflow 3.0 is Widgets. Embed some code in other pages so you can see build status, job status, &c.
[1] https://blog.argoproj.io/argo-events-v1-0-released-b69668de0583 https://blog.argoproj.io/argo-events-v1-0-released-b69668de0...
- halfmatthalfcat 6y agoSpeaking as someone whose spent the last 18 months building out Tekton pipelines, I can confidently disagree that it’s architecture (or general ethos) is built around CI/CD. The docs might allude to a lot of CI/CD use cases but the framework is very general in that you have the building blocks for any event driven workflow: Tasks, Pipelines and Events.
- rektide 6y agoTekton was very high in my runnings, very attractive. I liked the models they built around, they seemed like a good structure. Everything built very "cloud-native" (system state stored as Kubernetes objects). But the project did explicitly pivot, sometime in the last 12 months, to explicitly declare themselves/think of themselves as a CI/CD system. They're also under the Continuous Delivery Foundation now. I spent 5 minutes looking for the specific event, where this was determined/declared, & will try to follow up; hope I find it. I don't think it precludes Tekton from still being used more generally, thought of more generally. But now, doing so puts one out of alignment with the stated goals, with the project itself. I'm quite sad about this development: I think it radically undershoots the relevance of Tekton & what role it ought to fill. We have all this wonderful new cloud based pieces of state, but in terms of how one piece actuates another, how we can make systems that behave autonomically: we direly need some core Event Driven Architecture logic, and Tekton definitely has some really good tools for doing that. I want very much for Tekton to meet it's potential head on.