[throw1234651234]

Terraform feels like a useless wrapper on top of AZ CLI and resource definition yaml files. In general, Terraform provides nothing but a useless wrapper that people need to understand.

Furthermore, most companies don't need K8S either if they are using a cloud provider. It only starts being cheaper if you forget what you pay the DevOps team (or senior devs who do DevOps on top of code) AND have a huge number of resources. Otherwise you literally have to be in maybe the top 30 companies for K8S to actually save you money.

[throw1234651234]

I see the negs, but I don't see any coherent arguments, much like "irl", past "We just need it, ok". Nevermind the fact that even the OS-agnostic garbage argument falls apart the moment you do anything complex since it relies on the host kernel. Doing some graphics stuff (no, not games or AI, just say, PDF report generation)? Guess what, your library might be relying on OS-specific libraries and will break the moment you put your "agnostic" container on Linux. And now Docker desktop needs a license and everyone needs to learn Rancher.

Again, you don't need Docker. You aren't CoreWeave or a cloud provider. You DON'T need to virtualize your hardware and parse it out in pieces on a moment's notice. You don't need K8S to do a rolling update for you when on the cloud, you don't need Ingress to load balance, you don't need ECS/EKS to break every day.

I am persisting in hopes someone convinces me I am wrong by the way. This isn't a rant, I have a decade of experience of someone building a fancy container/orchestrator infrastructure only for all of it to fall apart the moment the DevOps team leaves. Perpetual cost center that adds nothing.

And yes, I know, I am not doing it right and we need Flux to fix all our problems now.

[pjmlp]

In general we don't need Docker, but that isn't what CV driven development looks like, thus here we are.