Live data from Hacker News

Dear friend, you have built a Kubernetes (2024)

macchaffee.com

181–183 of 183 posts

Re: Dear friend, you have built a Kubernetes (2024)

#181

Why both posts mention docker compose and not mentioning docker swarm. Being using it for my projects for long time. And it's so nice. Similar syntax, easy networking, rollout strategy, easy to add nodes to cluster. You can have one template docker-compose.yaml file and separate deployment files for different envs, like: docker-compose.dev.yaml, docker-compose.prod.yaml I think swarm is really underrated

How do you solve persistence with swarm? Can I deploy postgres with network storage that will mount automatically on node where container is launched?

> Can I deploy postgres with network storage that will mount automatically on node where container is launched?

Yes (if I'm getting your question right). here is an example of nfs volume: https://docs.docker.com/reference/compose-file/volumes/#driv...

Re: Dear friend, you have built a Kubernetes (2024)

#183
post #15

Earlier quoted context omitted.

Another case: People who want to run workloads that are inherently incompatible with Kubernetes networking model. For example: * For some cursed reasons you want to make sure every single one instance of a large batch job see just one NIC in its container and they are all the same IP and you NAT to the outside world. Ingress? What ingress? This is a batch job! * Like the previous point, except that your "batch job" s…

That is indeed a weirdly cursed requirement. Why? Black box of legacy stuff? A system that was never designed to be run in multiple does so if all the nodes think they’re the same machine? Defeating a license restriction?

Easier checkpoint & restore.
Post reply on HN