Fleet聽vs聽Kubernetes

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

Fleet

7
27
+ 1
0
Kubernetes

37.8K
32K
+ 1
623
Add tool

Fleet vs Kubernetes: What are the differences?

Fleet: Container management and deployment for your cluster. Fleet is a low-level cluster engine that feels like a distributed init system. With fleet, you can treat your CoreOS cluster as if it shared a single init system; Kubernetes: Manage a cluster of Linux containers as a single system to accelerate Dev and simplify Ops. Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.

Fleet and Kubernetes belong to "Container Tools" category of the tech stack.

Some of the features offered by Fleet are:

  • Deploy docker containers on arbitrary hosts in a cluster
  • Distribute services across a cluster using machine-level anti-affinity
  • Maintain N instances of a service, re-scheduling on machine failure

On the other hand, Kubernetes provides the following key features:

  • Lightweight, simple and accessible
  • Built for a multi-cloud world, public, private or hybrid
  • Highly modular, designed so that all of its components are easily swappable

Fleet and Kubernetes are both open source tools. Kubernetes with 55K GitHub stars and 19.1K forks on GitHub appears to be more popular than Fleet with 2.45K GitHub stars and 309 GitHub forks.

Advice on Fleet and Kubernetes

Hello, we have a bunch of local hosts (Linux and Windows) where Docker containers are running with bamboo agents on them. Currently, each container is installed as a system service. Each host is set up manually. I want to improve the system by adding some sort of orchestration software that should install, update and check for consistency in my docker containers. I don't need any clouds, all hosts are local. I'd prefer simple solutions. What orchestration system should I choose?

See more
Replies (1)
Mortie Torabi
Recommends
Docker Swarm

If you just want the basic orchestration between a set of defined hosts, go with Docker Swarm. If you want more advanced orchestration + flexibility in terms of resource management and load balancing go with Kubernetes. In both cases, you can make it even more complex while making the whole architecture more understandable and replicable by using Terraform.

See more
Decisions about Fleet and Kubernetes
Michael Roberts

We develop rapidly with docker-compose orchestrated services, however, for production - we utilise the very best ideas that Kubernetes has to offer: SCALE! We can scale when needed, setting a maximum and minimum level of nodes for each application layer - scaling only when the load balancer needs it. This allowed us to reduce our devops costs by 40% whilst also maintaining an SLA of 99.87%.

See more
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH | 28 upvotes 路 3.1M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Fleet
Pros of Kubernetes
    Be the first to leave a pro
    • 155
      Leading docker container management solution
    • 124
      Simple and powerful
    • 100
      Open source
    • 75
      Backed by google
    • 56
      The right abstractions
    • 24
      Scale services
    • 18
      Replication controller
    • 9
      Permission managment
    • 7
      Simple
    • 7
      Supports autoscaling
    • 6
      Cheap
    • 4
      Self-healing
    • 4
      Reliable
    • 4
      No cloud platform lock-in
    • 3
      Open, powerful, stable
    • 3
      Scalable
    • 3
      Quick cloud setup
    • 3
      Promotes modern/good infrascture practice
    • 2
      Backed by Red Hat
    • 2
      Runs on azure
    • 2
      Cloud Agnostic
    • 2
      Custom and extensibility
    • 2
      Captain of Container Ship
    • 2
      A self healing environment with rich metadata
    • 1
      Golang
    • 1
      Easy setup
    • 1
      Everything of CaaS
    • 1
      Sfg
    • 1
      Expandable
    • 1
      Gke

    Sign up to add or upvote prosMake informed product decisions

    Cons of Fleet
    Cons of Kubernetes
      Be the first to leave a con
      • 13
        Poor workflow for development
      • 11
        Steep learning curve
      • 5
        Orchestrates only infrastructure
      • 2
        High resource requirements for on-prem clusters

      Sign up to add or upvote consMake informed product decisions

      What is Fleet?

      Fleet is a low-level cluster engine that feels like a distributed init system. With fleet, you can treat your CoreOS cluster as if it shared a single init system.

      What is Kubernetes?

      Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.

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

      What companies use Fleet?
      What companies use Kubernetes?
      See which teams inside your own company are using Fleet or Kubernetes.
      Sign up for Private StackShareLearn More

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

      What tools integrate with Fleet?
      What tools integrate with Kubernetes?

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

      Blog Posts

      +2
      2
      1007
      Dec 8 2020 at 5:50PM

      DigitalOcean

      +11
      2
      1812
      +7
      3
      681
      May 21 2020 at 12:02AM

      Rancher Labs

      +12
      3
      1215
      Apr 16 2020 at 5:34AM

      Rancher Labs

      +2
      2
      769
      +14
      11
      2090
      What are some alternatives to Fleet and Kubernetes?
      Docker Compose
      With Compose, you define a multi-container application in a single file, then spin your application up in a single command which does everything that needs to be done to get it running.
      Helm
      Helm is the best way to find, share, and use software built for Kubernetes.
      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.
      Docker Swarm
      Swarm serves the standard Docker API, so any tool which already communicates with a Docker daemon can use Swarm to transparently scale to multiple hosts: Dokku, Compose, Krane, Deis, DockerUI, Shipyard, Drone, Jenkins... and, of course, the Docker client itself.
      Spring Cloud
      It provides tools for developers to quickly build some of the common patterns in distributed systems.
      See all alternatives