Rancher vs Spinnaker: What are the differences?
Developers describe Rancher as "Open Source Platform for Running a Private Container Service". Rancher is an open source container management platform that includes full distributions of Kubernetes, Apache Mesos and Docker Swarm, and makes it simple to operate container clusters on any cloud or infrastructure platform. On the other hand, Spinnaker is detailed as "Multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence". Created at Netflix, it has been battle-tested in production by hundreds of teams over millions of deployments. It combines a powerful and flexible pipeline management system with integrations to the major cloud providers.
Rancher and Spinnaker are primarily classified as "Container" and "Continuous Deployment" tools respectively.
Rancher and Spinnaker are both open source tools. Rancher with 11.9K GitHub stars and 1.34K forks on GitHub appears to be more popular than Spinnaker with 6.27K GitHub stars and 902 GitHub forks.
What is Rancher?
What is Spinnaker?
Want advice about which of these to choose?Ask the StackShare community!
Why do developers choose Spinnaker?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Spinnaker?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
- Consume too much unnecessary resource by just running rancher agent alone;
- Hard to recover from system failure
- Bad performance of load balancing (compare to dokcer swarm built-in LB or others).
The whole infrastructure is managed through Rancher. It provides a simple interface to all the underlying tools - Docker, HAProxy (automatically configures load balancer from the containers).
Currently looking to move to Swarm or Kubernetes due to a few issues I have with Rancher.
Orchestration of containers for our environments. Remote deployment from Jenkins.
We use Rancher for container orchestration and automated deployment pipelines.