“Why would I ever want the problem that this solves?” is the best way I’ve seen that mood captured. Brilliantly put and vital context for teaching.
I think this is also why I didn't see the point of the design patterns book.
If you don't already have all the problems that Kubernetes solves and the complexity that goes with those problems, adding Kubernetes prematurely gives you problems you didn't have by introducing complexity you weren't (yet) subscribed to.
A: "What the hell is a PersistentVolumeClaim? Why can't I just write to disk?"
B: "But what if you don't have a disk at the edge? How does this scale?"
A: "What edge?! What scale?! I have a disk!"/rant
The ones that have experience with devops tend to appreciate Kubernetes
I manage my personal infrastructure with Terraform.
I still prefer to keep services running with docker-compose when I can.
git pull && docker-compose restart docker pull ghcr.io/NAMESPACE/IMAGE_NAME:latest
docker-compose restart IMAGE_NAME ssh <server>
cd <directory>
git pull
tsc
pm2 restart allNo restart or compile because php don't care.