The core problem, I think, is that K8s is overly complicated for 95% of deployments out there, but it's become the default standard. People then start creating

The core problem, I think, is that K8s is overly complicated for 95% of deployments out there, but it's become the default standard. People then start creating tooling to mask some of the complexity, but then said tooling grows to support the full K8s feature set and then we're back to square one. Because the rush to K8s was so fast (and arguably before it was ready) the tooling often became necessary. > Helm charts are meant to be written by someone with the relevant skills sitting next to the developers. That makes sense for large organizations, but it still gets complicated depending on how your service plugs into a greater mesh of services. I currently treat helm the same way I treat Cloudformation on AWS (another horrid thing to deal with). If some third party has it so that I can easily take the template and launch it, then great. I don't want to go any further under the hood than that.