Kubernetes vs Test Kitchen

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

Kubernetes

49.8K
43.4K
+ 1
639
Test Kitchen

37
45
+ 1
15
Add tool

Kubernetes vs Test Kitchen: What are the differences?

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; Test Kitchen: Integration tool for developing and testing infrastructure code and software on isolated target platforms. Test Kitchen has a static, declarative configuration in a .kitchen.yml file at the root of your project. It is designed to execute isolated code run in pristine environments ensuring that no prior state exists. A plugin architecture gives you the freedom to run your code on any cloud, virtualization, or bare metal resources and allows you to write acceptance criteria in whatever framework you desire.

Kubernetes belongs to "Container Tools" category of the tech stack, while Test Kitchen can be primarily classified under "Continuous Integration".

"Leading docker container management solution" is the primary reason why developers consider Kubernetes over the competitors, whereas "Automated testing" was stated as the key factor in picking Test Kitchen.

Kubernetes and Test Kitchen are both open source tools. It seems that Kubernetes with 55.1K GitHub stars and 19.1K forks on GitHub has more adoption than Test Kitchen with 1.62K GitHub stars and 543 GitHub forks.

Decisions about Kubernetes and Test Kitchen
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 29 upvotes · 5M 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 StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Kubernetes
Pros of Test Kitchen
  • 162
    Leading docker container management solution
  • 126
    Simple and powerful
  • 104
    Open source
  • 75
    Backed by google
  • 56
    The right abstractions
  • 24
    Scale services
  • 19
    Replication controller
  • 10
    Permission managment
  • 7
    Simple
  • 7
    Cheap
  • 7
    Supports autoscaling
  • 4
    Reliable
  • 4
    Self-healing
  • 4
    No cloud platform lock-in
  • 3
    Quick cloud setup
  • 3
    Open, powerful, stable
  • 3
    Scalable
  • 3
    Promotes modern/good infrascture practice
  • 2
    Captain of Container Ship
  • 2
    A self healing environment with rich metadata
  • 2
    Cloud Agnostic
  • 2
    Runs on azure
  • 2
    Backed by Red Hat
  • 2
    Custom and extensibility
  • 1
    Golang
  • 1
    Expandable
  • 1
    Gke
  • 1
    Easy setup
  • 1
    Sfg
  • 1
    Everything of CaaS
  • 6
    Automated testing
  • 4
    Detect bugs in cook books
  • 2
    Integrates well with vagrant
  • 2
    Can containerise tests in Docker
  • 1
    Integrates well with puppet

Sign up to add or upvote prosMake informed product decisions

Cons of Kubernetes
Cons of Test Kitchen
  • 15
    Poor workflow for development
  • 15
    Steep learning curve
  • 8
    Orchestrates only infrastructure
  • 4
    High resource requirements for on-prem clusters
  • 2
    Too heavy for simple systems
  • 1
    Additional vendor lock-in (Docker)
  • 1
    More moving parts to secure
  • 1
    Additional Technology Overhead
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

    - No public GitHub repository available -

    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.

    What is Test Kitchen?

    Test Kitchen has a static, declarative configuration in a .kitchen.yml file at the root of your project. It is designed to execute isolated code run in pristine environments ensuring that no prior state exists. A plugin architecture gives you the freedom to run your code on any cloud, virtualization, or bare metal resources and allows you to write acceptance criteria in whatever framework you desire.

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

    Jobs that mention Kubernetes and Test Kitchen as a desired skillset
    CBRE
    United States of America Texas Richardson
    CBRE
    United States of America Texas Richardson
    Pinterest
    San Francisco, CA, US; Atlanta, GA, US; New York, NY, US
    CBRE
    United States of America Texas Dallas
    CBRE
    United States of America Texas Dallas
    What companies use Kubernetes?
    What companies use Test Kitchen?
    See which teams inside your own company are using Kubernetes or Test Kitchen.
    Sign up for StackShare EnterpriseLearn More

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

    What tools integrate with Kubernetes?
    What tools integrate with Test Kitchen?
      No integrations found

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

      Blog Posts

      Kubernetesetcd+2
      2
      1073
      Dec 8 2020 at 5:50PM

      DigitalOcean

      GitHubMySQLPostgreSQL+11
      2
      2158
      PythonDockerKubernetes+7
      3
      765
      May 21 2020 at 12:02AM

      Rancher Labs

      KubernetesAmazon EC2Grafana+12
      4
      1363
      Apr 16 2020 at 5:34AM

      Rancher Labs

      KubernetesRancher+2
      2
      839
      What are some alternatives to Kubernetes and Test Kitchen?
      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.
      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.
      OpenStack
      OpenStack is a cloud operating system that controls large pools of compute, storage, and networking resources throughout a datacenter, all managed through a dashboard that gives administrators control while empowering their users to provision resources through a web interface.
      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 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.
      See all alternatives