I agree, I learned Kubernetes, we use it in our company and to be honest, we could live without it, but it was just ugly, due to lack of good standardization. N

I agree, I learned Kubernetes, we use it in our company and to be honest, we could live without it, but it was just ugly, due to lack of good standardization. Now we have GitOps and can easily use tools like Argo Workflows, Argo CD and Argo Events to execute practically any kind of reasonable activity, make it reusable and everyone can see how everything works, at least on dynamically created k3d cluster provisioned with Terraform for development/testing/learning purposes. It's also easy to show everything you create on high level and communicate it to others, because it's easily presentable with e.g. draw.io It doesn't of course solve all kind of issue, because software development is very complex area, but it's making it easier to reason about some solution with others, so we can make what actually client wants without many dirty hacks and rediscovering the wheel. Do we need all these tools and concepts to just build cooperatively, some secure APIs, some front-end, automatically test them and ensure that solution will be highly available under light or moderate load? Probably no, but it would be much harder, even if our solution will be used only internally to handle up to few hundred requests per second and not millions of them. With Kubernetes I can setup almost everything on my own, with just virtual machines or servers and some networking change requests and assuming that infrastructure is stable, solution deployed with Kubernetes will probably be also stable. There are also managed Kubernetes clusters provided in cloud, where cost might seem high for smaller companies or there might be worries about security of using cloud, but once you get it how to create proper cloud-native solutions with Kubernetes, everything becomes much simpler. However learning curve is steep, so beginner might still have issues with efficient use of Kubernetes or other advanced setups, if there won't be good guidance on solution from documentation and/or meetings.