@stefanoStefano Marinelli There are sane uses for something like kubernetes and there are stupid ones. If you develop a highly distributed system consisting of many services, you can profit e.g. from the possibility of independent tech stacks, scalability and failover, etc. And you have to weigh that against the drawbacks, like how to keep track of all the components, libraries etc in use, e.g. regarding security...

But *when* you decide to use it, you certainly need some "devops" capabilities. Could be a team containing "operations" guys, or when it's a single person, it's not enough that they "can write code". I mean, *should* be obvious, right?