Need advice about which tool to choose? Ask the StackShare community!
Kubernetes vs Puppet Labs: What are the differences?
Developers describe Kubernetes as " 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. On the other hand, Puppet Labs is detailed as " Server automation framework and application ". Puppet is an automated administrative engine for your Linux, Unix, and Windows systems and performs administrative tasks (such as adding users, installing packages, and updating server configurations) based on a centralized specification.
Kubernetes and Puppet Labs are primarily classified as "Container" and "Server Configuration and Automation" 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, Puppet Labs provides the following key features:
- Insight- Puppet Enterprise's event inspector gives immediate and actionable insight into your environment, showing you what changed, where and how by classes, nodes and resources.
- Discovery- Puppet Enterprise delivers a dynamic and fully-pluggable discovery service that allows you to take advantage of any data source or real-time query results to quickly locate, identify and group cloud nodes.
- Provisioning- Automatically provision and configure bare metal, virtual, and private or public cloud capacity, all from a single pane. Save time getting your cloud projects off the ground by reusing the same configuration modules you set up for your physical deployments.
"Leading docker container management solution" is the primary reason why developers consider Kubernetes over the competitors, whereas "Devops" was stated as the key factor in picking Puppet Labs.
Kubernetes and Puppet Labs are both open source tools. It seems that Kubernetes with 55K GitHub stars and 19.1K forks on GitHub has more adoption than Puppet Labs with 5.37K GitHub stars and 2.1K GitHub forks.
Google , Slack , and Shopify are some of the popular companies that use Kubernetes, whereas Puppet Labs is used by Uber Technologies , Twitch , and PayPal . Kubernetes has a broader approval, being mentioned in 1046 company stacks & 1096 developers stacks; compared to Puppet Labs, which is listed in 180 company stacks and 49 developer stacks.
I'm just getting started using Vagrant to help automate setting up local VMs to set up a Kubernetes cluster (development and experimentation only). (Yes, I do know about minikube)
I'm looking for a tool to help install software packages, setup users, etc..., on these VMs. I'm also fairly new to Ansible, Chef, and Puppet. What's a good one to start with to learn? I might decide to try all 3 at some point for my own curiosity.
The most important factors for me are simplicity, ease of use, shortest learning curve.
I have been working with Puppet and Ansible. The reason why I prefer ansible is the distribution of it. Ansible is more lightweight and therefore more popular. This leads to situations, where you can get fully packaged applications for ansible (e.g. confluent) supported by the vendor, but only incomplete packages for Puppet.
The only advantage I would see with Puppet if someone wants to use Foreman. This is still better supported with Puppet.
If you are just starting out, might as well learn Kubernetes There's a lot of tools that come with Kube that make it easier to use and most importantly: you become cloud-agnostic. We use Ansible because it's a lot simpler than Chef or Puppet and if you use Docker Compose for your deployments you can re-use them with Kubernetes later when you migrate
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 solution162
-
Simple and powerful127
-
Open source104
-
Backed by google75
-
The right abstractions57
-
Scale services24
-
Replication controller19
-
Permission managment10
-
Cheap7
-
Simple7
-
Supports autoscaling7
-
No cloud platform lock-in4
-
Self-healing4
-
Reliable4
-
Quick cloud setup3
-
Open, powerful, stable3
-
Scalable3
-
Promotes modern/good infrascture practice3
-
Custom and extensibility2
-
Cloud Agnostic2
-
Captain of Container Ship2
-
A self healing environment with rich metadata2
-
Runs on azure2
-
Backed by Red Hat2
-
Golang1
-
Expandable1
-
Sfg1
-
Everything of CaaS1
-
Easy setup1
-
Gke1
Pros of Puppet Labs
-
Devops51
-
Automate it44
-
Reusable components26
-
Dynamic and idempotent server configuration21
-
Great community18
-
Very scalable12
-
Cloud management12
-
Easy to maintain10
-
Free tier9
-
Works with Amazon EC26
-
Declarative4
-
Ruby4
-
Works with Azure3
-
Works with OpenStack3
-
Nginx2
-
Ease of use1
Sign up to add or upvote pros Make informed product decisions
Cons of Kubernetes
-
Steep learning curve15
-
Poor workflow for development15
-
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 Puppet Labs
-
Steep learning curve3
-
Customs types idempotence1
Sign up to add or upvote cons Make informed product decisions
What is Kubernetes?
What is Puppet Labs?
Need advice about which tool to choose? Ask the StackShare community!
+
5
+
10
+
9
+
18
+
14
+
8
+
9
+
27
What companies use Puppet Labs?
Sign up to get full access to all the companies Make informed product decisions
What tools integrate with Kubernetes?
What tools integrate with Puppet Labs?
Sign up to get full access to all the tool integrations Make informed product decisions
Blog Posts
+
1
+
2
+
9
+
11
+
11
+
7
+
12
+
2