Alternatives to Amazon EKS logo

Alternatives to Amazon EKS

kops, Kubernetes, Rancher, Amazon EC2 Container Service, and Google Kubernetes Engine are the most popular alternatives and competitors to Amazon EKS.
764
401
+ 1
3

What is Amazon EKS and what are its top alternatives?

Amazon Elastic Container Service for Kubernetes (Amazon EKS) is a managed service that makes it easy for you to run Kubernetes on AWS without needing to install and operate your own Kubernetes clusters.
Amazon EKS is a tool in the Containers as a Service category of a tech stack.

Top Alternatives to Amazon EKS

  • kops
    kops

    It helps you create, destroy, upgrade and maintain production-grade, highly available, Kubernetes clusters from the command line. AWS (Amazon Web Services) is currently officially supported, with GCE in beta support , and VMware vSphere in alpha, and other platforms planned. ...

  • Kubernetes
    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. ...

  • Rancher
    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. ...

  • Amazon EC2 Container Service
    Amazon EC2 Container Service

    Amazon EC2 Container Service lets you launch and stop container-enabled applications with simple API calls, allows you to query the state of your cluster from a centralized service, and gives you access to many familiar Amazon EC2 features like security groups, EBS volumes and IAM roles. ...

  • Google Kubernetes Engine
    Google Kubernetes Engine

    Container Engine takes care of provisioning and maintaining the underlying virtual machine cluster, scaling your application, and operational logistics like logging, monitoring, and health management. ...

  • AWS Fargate
    AWS Fargate

    AWS Fargate is a technology for Amazon ECS and EKS* that allows you to run containers without having to manage servers or clusters. With AWS Fargate, you no longer have to provision, configure, and scale clusters of virtual machines to run containers. ...

  • Azure Kubernetes Service
    Azure Kubernetes Service

    Deploy and manage containerized applications more easily with a fully managed Kubernetes service. It offers serverless Kubernetes, an integrated continuous integration and continuous delivery (CI/CD) experience, and enterprise-grade security and governance. Unite your development and operations teams on a single platform to rapidly build, deliver, and scale applications with confidence. ...

  • Hyper
    Hyper

    Hyper.sh is a secure container hosting service. What makes it different from AWS (Amazon Web Services) is that you don't start servers, but start docker images directly from Docker Hub or other registries. ...

Amazon EKS alternatives & related posts

kops logo

kops

89
70
0
Production Grade K8s Installation, Upgrades, and Management
89
70
+ 1
0
PROS OF KOPS
    Be the first to leave a pro
    CONS OF KOPS
      Be the first to leave a con

      related kops posts

      Kubernetes logo

      Kubernetes

      47K
      40.6K
      635
      Manage a cluster of Linux containers as a single system to accelerate Dev and simplify Ops
      47K
      40.6K
      + 1
      635
      PROS OF KUBERNETES
      • 161
        Leading docker container management solution
      • 126
        Simple and powerful
      • 103
        Open source
      • 75
        Backed by google
      • 56
        The right abstractions
      • 24
        Scale services
      • 19
        Replication controller
      • 9
        Permission managment
      • 7
        Simple
      • 7
        Supports autoscaling
      • 6
        Cheap
      • 4
        Self-healing
      • 4
        No cloud platform lock-in
      • 4
        Reliable
      • 3
        Open, powerful, stable
      • 3
        Scalable
      • 3
        Quick cloud setup
      • 3
        Promotes modern/good infrascture practice
      • 2
        Backed by Red Hat
      • 2
        Cloud Agnostic
      • 2
        Runs on azure
      • 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
      CONS OF KUBERNETES
      • 15
        Poor workflow for development
      • 14
        Steep learning curve
      • 7
        Orchestrates only infrastructure
      • 4
        High resource requirements for on-prem clusters
      • 2
        Too heavy for simple systems
      • 1
        Additional Technology Overhead
      • 1
        More moving parts to secure
      • 1
        Additional vendor lock-in (Docker)

      related Kubernetes posts

      Conor Myhrvold
      Tech Brand Mgr, Office of CTO at Uber · | 41 upvotes · 5.2M views

      How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

      Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

      Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

      https://eng.uber.com/distributed-tracing/

      (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

      Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

      See more
      Yshay Yaacobi

      Our first experience with .NET core was when we developed our OSS feature management platform - Tweek (https://github.com/soluto/tweek). We wanted to create a solution that is able to run anywhere (super important for OSS), has excellent performance characteristics and can fit in a multi-container architecture. We decided to implement our rule engine processor in F# , our main service was implemented in C# and other components were built using JavaScript / TypeScript and Go.

      Visual Studio Code worked really well for us as well, it worked well with all our polyglot services and the .Net core integration had great cross-platform developer experience (to be fair, F# was a bit trickier) - actually, each of our team members used a different OS (Ubuntu, macos, windows). Our production deployment ran for a time on Docker Swarm until we've decided to adopt Kubernetes with almost seamless migration process.

      After our positive experience of running .Net core workloads in containers and developing Tweek's .Net services on non-windows machines, C# had gained back some of its popularity (originally lost to Node.js), and other teams have been using it for developing microservices, k8s sidecars (like https://github.com/Soluto/airbag), cli tools, serverless functions and other projects...

      See more
      Rancher logo

      Rancher

      858
      1.4K
      644
      Open Source Platform for Running a Private Container Service
      858
      1.4K
      + 1
      644
      PROS OF RANCHER
      • 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
      CONS OF RANCHER
      • 10
        Hosting Rancher can be complicated

      related Rancher posts

      Amazon EC2 Container Service logo

      Amazon EC2 Container Service

      12.4K
      8.1K
      325
      Container management service that supports Docker containers
      12.4K
      8.1K
      + 1
      325
      PROS OF AMAZON EC2 CONTAINER SERVICE
      • 100
        Backed by amazon
      • 72
        Familiar to ec2
      • 53
        Cluster based
      • 42
        Simple API
      • 26
        Iam roles
      • 7
        Scheduler
      • 7
        Cluster management
      • 7
        Programmatic Control
      • 4
        Socker support
      • 4
        Container-enabled applications
      • 2
        No additional cost
      • 1
        Easy to use and cheap
      CONS OF AMAZON EC2 CONTAINER SERVICE
        Be the first to leave a con

        related Amazon EC2 Container Service posts

        Cyril Duchon-Doris

        We build a Slack app using the Bolt framework from slack https://api.slack.com/tools/bolt, a Node.js express app. It allows us to easily implement some administration features so we can easily communicate with our backend services, and we don't have to develop any frontend app since Slack block kit will do this for us. It can act as a Chatbot or handle message actions and custom slack flows for our employees.

        This app is deployed as a microservice on Amazon EC2 Container Service with AWS Fargate. It uses very little memory (and money) and can communicate easily with our backend services. Slack is connected to this app through a ALB ( AWS Elastic Load Balancing (ELB) )

        See more
        Russel Werner
        Lead Engineer at StackShare · | 7 upvotes · 208.1K views

        We began our hosting journey, as many do, on Heroku because they make it easy to deploy your application and automate some of the routine tasks associated with deployments, etc. However, as our team grew and our product matured, our needs have outgrown Heroku. I will dive into the history and reasons for this in a future blog post.

        We decided to migrate our infrastructure to Kubernetes running on Amazon EKS. Although Google Kubernetes Engine has a slightly more mature Kubernetes offering and is more user-friendly; we decided to go with EKS because we already using other AWS services (including a previous migration from Heroku Postgres to AWS RDS). We are still in the process of moving our main website workloads to EKS, however we have successfully migrate all our staging and testing PR apps to run in a staging cluster. We developed a Slack chatops application (also running in the cluster) which automates all the common tasks of spinning up and managing a production-like cluster for a pull request. This allows our engineering team to iterate quickly and safely test code in a full production environment. Helm plays a central role when deploying our staging apps into the cluster. We use CircleCI to build docker containers for each PR push, which are then published to Amazon EC2 Container Service (ECR). An upgrade-operator process watches the ECR repository for new containers and then uses Helm to rollout updates to the staging environments. All this happens automatically and makes it really easy for developers to get code onto servers quickly. The immutable and isolated nature of our staging environments means that we can do anything we want in that environment and quickly re-create or restore the environment to start over.

        The next step in our journey is to migrate our production workloads to an EKS cluster and build out the CD workflows to get our containers promoted to that cluster after our QA testing is complete in our staging environments.

        See more
        Google Kubernetes Engine logo

        Google Kubernetes Engine

        1.1K
        769
        69
        Deploy, manage, and scale containerized applications on Kubernetes, powered by Google Cloud
        1.1K
        769
        + 1
        69
        PROS OF GOOGLE KUBERNETES ENGINE
        • 17
          Backed by Google
        • 17
          Powered by kubernetes
        • 12
          Docker
        • 11
          Scalable
        • 6
          Open source
        • 2
          Command line interface is intuitive
        • 2
          Decoupled app
        • 1
          Provisioning
        • 1
          Declarative management
        CONS OF GOOGLE KUBERNETES ENGINE
          Be the first to leave a con

          related Google Kubernetes Engine posts

          Omar Mehilba
          Co-Founder and COO at Magalix · | 19 upvotes · 274.1K views

          We are hardcore Kubernetes users and contributors. We loved the automation it provides. However, as our team grew and added more clusters and microservices, capacity and resources management becomes a massive pain to us. We started suffering from a lot of outages and unexpected behavior as we promote our code from dev to production environments. Luckily we were working on our AI-powered tools to understand different dependencies, predict usage, and calculate the right resources and configurations that should be applied to our infrastructure and microservices. We dogfooded our agent (http://github.com/magalixcorp/magalix-agent) and were able to stabilize as the #autopilot continuously recovered any miscalculations we made or because of unexpected changes in workloads. We are open sourcing our agent in a few days. Check it out and let us know what you think! We run workloads on Microsoft Azure Google Kubernetes Engine and Amazon EC2 and we're all about Go and Python!

          See more
          Emanuel Evans
          Senior Architect at Rainforest QA · | 18 upvotes · 996.1K views

          We recently moved our main applications from Heroku to Kubernetes . The 3 main driving factors behind the switch were scalability (database size limits), security (the inability to set up PostgreSQL instances in private networks), and costs (GCP is cheaper for raw computing resources).

          We prefer using managed services, so we are using Google Kubernetes Engine with Google Cloud SQL for PostgreSQL for our PostgreSQL databases and Google Cloud Memorystore for Redis . For our CI/CD pipeline, we are using CircleCI and Google Cloud Build to deploy applications managed with Helm . The new infrastructure is managed with Terraform .

          Read the blog post to go more in depth.

          See more
          AWS Fargate logo

          AWS Fargate

          618
          346
          0
          Run Containers Without Managing Infrastructure
          618
          346
          + 1
          0
          PROS OF AWS FARGATE
            Be the first to leave a pro
            CONS OF AWS FARGATE
              Be the first to leave a con

              related AWS Fargate posts

              Cyril Duchon-Doris

              We build a Slack app using the Bolt framework from slack https://api.slack.com/tools/bolt, a Node.js express app. It allows us to easily implement some administration features so we can easily communicate with our backend services, and we don't have to develop any frontend app since Slack block kit will do this for us. It can act as a Chatbot or handle message actions and custom slack flows for our employees.

              This app is deployed as a microservice on Amazon EC2 Container Service with AWS Fargate. It uses very little memory (and money) and can communicate easily with our backend services. Slack is connected to this app through a ALB ( AWS Elastic Load Balancing (ELB) )

              See more
              Azure Kubernetes Service logo

              Azure Kubernetes Service

              340
              306
              0
              Simplify Kubernetes management, deployment, and operations.
              340
              306
              + 1
              0
              PROS OF AZURE KUBERNETES SERVICE
                Be the first to leave a pro
                CONS OF AZURE KUBERNETES SERVICE
                  Be the first to leave a con

                  related Azure Kubernetes Service posts

                  Farzad Jalali
                  Senior Software Architect at BerryWorld · | 8 upvotes · 209.7K views

                  Visual Studio Azure DevOps Azure Functions Azure Websites #Azure #AzureKeyVault #AzureAD #AzureApps

                  #Azure Cloud Since Amazon is potentially our competitor then we need a different cloud vendor, also our programmers are microsoft oriented so the choose were obviously #Azure for us.

                  Azure DevOps Because we need to be able to develop a neww pipeline into Azure environment ina few minutes.

                  Azure Kubernetes Service We already in #Azure , also need to use K8s , so let's use AKS as it's a manged Kubernetes in the #Azure

                  See more
                  Hyper logo

                  Hyper

                  103
                  63
                  0
                  On-Demand Container, Per-Second Billing
                  103
                  63
                  + 1
                  0
                  PROS OF HYPER
                    Be the first to leave a pro
                    CONS OF HYPER
                      Be the first to leave a con

                      related Hyper posts