Kubernetes Maximalism

But like most posts, it doesn't talk up Kubernetes on it's own terms. Right now we regard it as a platform, a place for building apps, which will continue talking to redis and postgres and memcache as usual.

I've yet to seeuch advocacy of real kubernetes maximalism, of preaching development of cloud native apps. Rather than passing configmaps of configuration, and storing entities in databases, rather than processing commands & returning results, I want to imagine more state externalized into our cloud, I want to imagine more declarative systems where we first declare state and then controllers/operators enact it, as a way of developing our apps. There's a lot of thoughtleadering that limits cloud native development practices to something suitable for platform, but imo we should be embracing & looking at which strengths of architecture we can adopt more broadly, & taking those lessons to our everyday app building. The way of kubernetes has much to each us.

I also think there's a lot of argumentation related to this about having single pane of glass interfaces, about having total systems integration & visibility that the old diy build your own ops stacks & local environments could not offer without enormous effort.