Need advice about which tool to choose?Ask the StackShare community!
Kubernetes vs OpenStack: What are the differences?
What is 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.
What is OpenStack? Open source software for building private and public clouds. 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.
Kubernetes and OpenStack are primarily classified as "Container" and "Open Source Cloud" tools respectively.
Some of the features offered by Kubernetes are:
- 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
On the other hand, OpenStack provides the following key features:
- Compute
- Storage
- Networking
"Leading docker container management solution" is the primary reason why developers consider Kubernetes over the competitors, whereas "Private cloud" was stated as the key factor in picking OpenStack.
Kubernetes is an open source tool with 55K GitHub stars and 19.1K GitHub forks. Here's a link to Kubernetes's open source repository on GitHub.
Google, Slack, and Shopify are some of the popular companies that use Kubernetes, whereas OpenStack is used by PayPal, HubSpot, and Wikipedia. Kubernetes has a broader approval, being mentioned in 1046 company stacks & 1096 developers stacks; compared to OpenStack, which is listed in 67 company stacks and 50 developer stacks.
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?
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.
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%.
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.
Pros of Kubernetes
- Leading docker container management solution164
- Simple and powerful128
- Open source106
- Backed by google76
- The right abstractions58
- Scale services25
- Replication controller20
- Permission managment11
- Cheap8
- Supports autoscaling8
- Simple8
- No cloud platform lock-in5
- Reliable5
- Self-healing5
- Quick cloud setup4
- Promotes modern/good infrascture practice4
- Scalable4
- Open, powerful, stable4
- Runs on azure3
- Captain of Container Ship3
- Cloud Agnostic3
- Custom and extensibility3
- Backed by Red Hat3
- A self healing environment with rich metadata3
- Gke2
- Everything of CaaS2
- Sfg2
- Expandable2
- Golang2
- Easy setup2
Pros of OpenStack
- Private cloud56
- Avoid vendor lock-in37
- Flexible in use22
- Industry leader6
- Supported by many companies in top5004
- Robust architecture4
Sign up to add or upvote prosMake informed product decisions
Cons of Kubernetes
- Poor workflow for development15
- Steep learning curve15
- Orchestrates only infrastructure8
- High resource requirements for on-prem clusters4
- Too heavy for simple systems2
- Additional vendor lock-in (Docker)1
- More moving parts to secure1
- Additional Technology Overhead1
Cons of OpenStack
Sign up to add or upvote consMake informed product decisions
What is Kubernetes?
What is OpenStack?
Need advice about which tool to choose?Ask the StackShare community!
What companies use OpenStack?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Kubernetes?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+1
+2
+9
+11
+11+7
+12
+2