4 ms·
I'd be really interested to know more about your setup and processes if you're running Swarm in production? For example, how do you handle rolling updates?
by GordonS 8y ago
I'd be really interested to know more about your setup and processes if you're running Swarm in production? For example, how do you handle rolling updates?
- nisa 8y agowe are not a SaaS company, we just run some simple nodejs based services on swarm and my goal is to use swarm as a testing hub for docker - mostly the ci should push something there for the devs. So uptime does not matter, however swarm crashed badly a few times on me and at the moment everything important is well configured outside using your typical LTS linux distribution and I'm hesitant to move our basic services to it...basically 9-5 it has to work, I can just run apt-get update && reboot earlier or later - really not sure if I should move all the stuff into swarm / k8s - also because bus factor would be one and there is some experience with the old linux way. For everything that resembles a microservice/service -> Docker, everything else (ldap, mail) -> oldschool. So far so good. I'm looking at k3s or minikube with rancher as ui - maybe that's better, or we just ignore the hype and run docker-compose.yml files by hand but that's also pretty shitty.