3 ms·
It does what it should for us. SSH + "make deploy" is a really bad comparison as you don't get overlay networking for free and also don't get any HA. What we
by ancieque 4y ago
It does what it should for us.
SSH + "make deploy" is a really bad comparison as you don't get overlay networking for free and also don't get any HA.
What we need:
1. HA for services
2. networking between nodes
3. ingress into the cluster
4. possibly volumes
All 4 are solved to our liking. Once we really need Kubernetes, we can do the switch.
- orf 4y ago> All 4 are solved to our liking. Once we really need Kubernetes, we can do the switch. Indeed, but this still doesn't mean it's a sound technical decision to build a bunch of custom tooling ontop of a dead and soon unsupported foundation that very few people use then realize too late that switching to a supported platform isn't as easy as you'd have hoped. I'm not comparing Swarm to Kubernetes, that's been done to death, I'm merely pointing out it's odd that you're spending time and energy building commodity features that already exist in k8s and are not core to your product. Good luck though!
- ancieque 4y agodocker-stack-deploy is not adding too much, and I don't see it doing much more in the future. But I get your point and believe it is in good faith, so thank you for your thoughts :).