![]() DevOps folks certainly do not need to learn yet another language just to get their jobs done. We quickly discarded the idea of writing a new scripting language from scratch, though. We wanted to build a scripting system for Kubernetes that mirrored UNIX. When we started Brigade five years ago, this was precisely the guiding light we were following. Just take a look in your system's /etc directory, and you'll see a litany of scripts that run every single time your Mac, Linux, etc. ![]() Shell scripts pipe data from one program to another, allowing a UNIX user to quickly accomplish a "big" task by orchestrating a series of "small" tasks.Īnd when you look at the history of UNIX, it is readily evident that shell scripts are key to the operating system's success. In UNIX, a scripting language functions as "workflow glue." One writes small bits of logic - for loops, if/then statements, error handling-that control the sequence of calling out to existing programs on a UNIX system. Our guiding intuition was "What if there was a scripting language for Kubernetes?" When we first set out to build Brigade, we wanted to create a new category of Kubernetes applications. While I am no longer active on that project, I am deeply impressed with the new architecture. ![]() If you're looking for next-gen Kubernetes workflows or a scripting language for your cluster, Brigade is it. I wanted to take a moment to reflect on why Brigade 2 is so exciting.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |