Both in the conversations as well as these comments I see two sets of people talking past each other. Immediately that phrase becomes very evident, "It is diffi

Both in the conversations as well as these comments I see two sets of people talking past each other. Immediately that phrase becomes very evident, "It is difficult to get a man to understand something when his salary depends on his not understanding it." Embracing k8s is a monumental decision for a company and from that point forward it becomes the galactic center of everything you do. Any new solution you introduce needs to fit into the k8s ecosystem you will have created. It insists upon itself, and it insists upon people's time. It is also a lock in of its own kind, and an insidious one too. You are not going to escape a lock in, the only thing you can do is accept it or perform an appropriate set of mental gymnastics to convince yourself that it isn't one. Many of us are technologists, and part our role is to understand that cost and impact. After 10 years, hopefully it is evident by now and we have learned in the industry that k8s not something that should be taken on lightly (spoiler: we haven't learned squat). It absolutely is possible to go managed well - forget serverless itself - managed services where you work with what is given by a cloud provider. The point of managed services isn't just cost, it is reducing the amount of time and effort your humans are spending. Part of managed services is to actually understand what they do and not go in blindly, then acting surprised when they do something else. Small functions, Lambda. Containers, ECS Fargate. Databases, RDS. The service costs and boogeymans often trotted out are irrelevant in the face of human time, if your humans are having to maintain and manage something, that is wasted time, and they are not delivering actual things of value.