Need advice about which tool to choose?Ask the StackShare community!

Gardener

13
35
+ 1
2
Rancher

806
1.3K
+ 1
644
Add tool
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Gardener
Pros of Rancher
  • 2
    It works across clouds and on-prem
  • 103
    Easy to use
  • 79
    Open source and totally free
  • 63
    Multi-host docker-compose support
  • 58
    Load balancing and health check included
  • 58
    Simple
  • 44
    Rolling upgrades, green/blue upgrades feature
  • 42
    Dns and service discovery out-of-the-box
  • 37
    Only requires docker
  • 34
    Multitenant and permission management
  • 29
    Easy to use and feature rich
  • 11
    Cross cloud compatible
  • 11
    Does everything needed for a docker infrastructure
  • 8
    Simple and powerful
  • 8
    Next-gen platform
  • 7
    Very Docker-friendly
  • 6
    Support Kubernetes and Swarm
  • 6
    Application catalogs with stack templates (wizards)
  • 6
    Supports Apache Mesos, Docker Swarm, and Kubernetes
  • 6
    Rolling and blue/green upgrades deployments
  • 6
    High Availability service: keeps your app up 24/7
  • 5
    Easy to use service catalog
  • 4
    Very intuitive UI
  • 4
    IaaS-vendor independent, supports hybrid/multi-cloud
  • 4
    Awesome support
  • 3
    Scalable
  • 2
    Requires less infrastructure requirements

Sign up to add or upvote prosMake informed product decisions

Cons of Gardener
Cons of Rancher
    Be the first to leave a con
    • 8
      Hosting Rancher can be complicated

    Sign up to add or upvote consMake informed product decisions

    What is Gardener?

    Many Open Source tools exist which help in creating and updating single Kubernetes clusters. However, the more clusters you need the harder it becomes to operate, monitor, manage and keep all of them alive and up-to-date. And that is exactly what project Gardener focuses on.

    What is Rancher?

    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.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use Gardener?
    What companies use Rancher?
      No companies found
      See which teams inside your own company are using Gardener or Rancher.
      Sign up for Private StackShareLearn More

      Sign up to get full access to all the companiesMake informed product decisions

      What tools integrate with Gardener?
      What tools integrate with Rancher?

      Sign up to get full access to all the tool integrationsMake informed product decisions

      Blog Posts

      PythonDockerKubernetes+7
      3
      696
      May 21 2020 at 12:02AM

      Rancher Labs

      KubernetesAmazon EC2Grafana+12
      3
      1230
      Apr 16 2020 at 5:34AM

      Rancher Labs

      KubernetesRancher+2
      2
      782
      What are some alternatives to Gardener and Rancher?
      Architect
      Create, deploy, and maintain next-generation AWS cloud function-based serverless infrastructure with full local, offline workflows, and more.
      Apache Mesos
      Apache Mesos is a cluster manager that simplifies the complexity of running applications on a shared pool of servers.
      Nomad
      Nomad is a cluster manager, designed for both long lived services and short lived batch processing workloads. Developers use a declarative job specification to submit work, and Nomad ensures constraints are satisfied and resource utilization is optimized by efficient task packing. Nomad supports all major operating systems and virtualized, containerized, or standalone applications.
      DC/OS
      Unlike traditional operating systems, DC/OS spans multiple machines within a network, aggregating their resources to maximize utilization by distributed applications.
      YARN Hadoop
      Its fundamental idea is to split up the functionalities of resource management and job scheduling/monitoring into separate daemons. The idea is to have a global ResourceManager (RM) and per-application ApplicationMaster (AM).
      See all alternatives