still thinking about this one
@nixCraft I can’t wait to maintain someone’s implementation of Kubernetes written in Bash.

@anderseknert we wrote k8s in bash in 2015. We made mistakes. It caused problems. It was rocket surgery.

Moving to k8s very much helped make things manageable because there are docs and examples and help available. It is still really hard but there is now a realistic chance others can pitch in and build things in our environment.

@myforest yeah, I have worked in a team where we implemented container orchestration before k8s too, although mostly in Python, and obviously not covering all of what k8s does. We were quite relieved to leave that behind. Standardizing on *something*, even if something complex, is almost always a big win.
@anderseknert @myforest I always struggle to decide on which standard to adhere to because some of them end up as a vendor lock in.
@cmdrSprocket @anderseknert @myforest happier in a self-built prison?