Our infrastructure? One server. One docker-compose.yml file. Zero Kubernetes complexity.

If your business/use case can tolerate manually rebuilding a server and redeploying your stack in case of hardware failure, I don't see why we're even discussing kubernetes.

That's a cool docker compose setup and is definitely competitive with a single node k8s deployment I run for hobby projects (k3s). The simplicity of this docker compose setup is an advantage, but it is missing some useful features compared to k8s:

• No Let's Encrypt support for Nginx using Cert Manager.
• No git ops support, the deployment shell script is manually run.
• No management ui's like Lens or k9s.
• Will not scale to multiple machines without changing the technology to k8s or Nomad.

That said, I would be happy to run their setup if I hadn't gone through the pain of learning k8s.

Ok? But it's also more fun. Do whatever you want, I'll stick with k8s