4 ms·
one thing i need to point out is: swarm intentionally ship many features conflict with kubernetes in order to compete with it, then it failed, and leaves migrat
by resouer 9y ago
one thing i need to point out is: swarm intentionally ship many features conflict with kubernetes in order to compete with it, then it failed, and leaves migrations somehow impossible. so if u only have small cluster and love swarm thing and does not need more mature orchestrations level, just keep it. but recommendng others jump in this hole is definitely Irresponsible.
- ossm1db 9y agoI learned first-hand that migrations are difficult. Do not go to production with Swarm if you are thinking of migrating to k8s. Use it for experimentation and learning.
- raarts 9y agoI respectfully disagree. If you move your existing stack to Docker Swarm, by far most of the work is in containerization. Creating Dockerfiles, decoding how containers interact, deciding on environment variables, deployment mechanisms etcetera. When moving to Kubernetes the same thing happens: most of the work goes to those same activities. That work is not lost if you defer moving to k8s to later. And that move itself will be so easy compared to the containerization.