And you are here why?

(For when you need to get beyond basic container orchestration) Seriously, Kubernetes is great for your baseline orchestration — stuff like scheduling, nodes, volumes, and so forth. It’s when you get into the complexity of workflows — like all the entertainment around continuous delivery — that you eventually realize that you need   something more , and that your increasingly complex python/scripting setup needs to be cleaned up. Enter Argo —  https://github.com/argoproj/argo  — which takes care of specifying, scheduling, and co-ordinating these workflows, the steps therein, and the interactions between these steps, all in a simple declarative style (YAML! You can munge this into your repo, and be well on your way towards immutable infrastructure!) In addition, Argo also integrates artifact management — which, in and as of itself, is ridiculously useful. My highly unscientific survey guesstimates that around 70% of the cruft in most existing home-built systems revolves ar...

(aka: “Scripting is to Operating Systems as   #Brigade   is to   #Kubernetes ”) If you think of Kubernetes as a “distributed OS” that runs containers on the individual hosts, then think of Brigade as providing the scripting around the containers — flow control, information gathering, event handling, etc. The key here is to maintain the separation of concerns, and not get opinionated about what the scheduling, functionality, and so forth — after all, that’s what Kubernetes is there for! Where things get somewhat different is that containers are really not “programs” in the OS sense — and towards managing that, Brigade looks at scripting in an Event-Oriented form, not unlike Applescript. Read on for more   at   http://technosophos.com/2018/01/04/why-brigade-doesn-t-do-yaml.html