We deploy all our containerized applications to Rancher (using Cattle for orchestration) via Jenkins jobs with a standardized Makefile for build, test, and deploy, making things consistent.
We look at running straight k8s, but it was like using a chainsaw to sharpen a pencil for our use case.
In addition their devs are extremely helpful and also have a hobby of getting things to run on ARM.
We're migrating to Rancher from a mix of Jenkins tasks and manual deploys on AWS machines (ie: a mess) and the product is great. I've evaluated both DCOS and k8s about 7-8 months ago and found a k8s a bit complex and moving really fast (we're a small ops team so we can't spend too much time browsing documentation and keeping up with the latest way of doing things). I didn't like DCOS for various reasons (it seemed less mature and the community was too small.)
Rancher is also a breeze to deploy, I could manually deploy it with one hand tied behind my back in 10mn on AWS.
I read something about using Rancher to deploy an Elixir cluster with Docker the other day. That jumped out at me because prior to reading that, the general feeling was that Docker + Erlang/Elixir cluster was a no go.
Rancher was the first thing I'd seen that claimed to be able to pull it off. I'll definitely give this more of a look.
We deploy all our containerized applications to Rancher (using Cattle for orchestration) via Jenkins jobs with a standardized Makefile for build, test, and deploy, making things consistent.
We look at running straight k8s, but it was like using a chainsaw to sharpen a pencil for our use case.
In addition their devs are extremely helpful and also have a hobby of getting things to run on ARM.