Kruise vs Kubernetes

Overview

Kubernetes

Stacks61.2K

Followers52.8K

Votes685

Kruise

Stacks1

Followers7

Votes0

GitHub Stars5.1K

Forks832

Kruise vs Kubernetes: What are the differences?

Key Differences Between Kruise and Kubernetes

1. Inherent Operations: Kruise, an open-source project, is built upon Kubernetes and provides additional capabilities for managing application-level workloads. It extends Kubernetes by allowing users to perform rolling updates, canary deployments, and canary rollbacks without the need for external tools or technologies. Kubernetes, on the other hand, focuses primarily on container orchestration and provides a foundation for deploying, scaling, and managing containerized applications.

2. Application Management: Kruise introduces a higher-level API for managing applications, whereas Kubernetes operates at a lower level with its deployment, replication controllers, and stateful sets. Kruise allows users to define application-level objects, such as apps and components, which can be managed collectively. This abstraction simplifies the management of complex applications and reduces the need for manual interventions.

3. Update Strategies: Kruise offers more advanced update strategies compared to Kubernetes. It supports multiple strategies like "InPlaceUpdate" where pods are upgraded in-place, "RollingUpdate" where pods are replaced gradually, and "BlueGreenUpdate" where two sets of pods are used to perform a blue-green deployment. Kubernetes, on the other hand, focuses on rolling updates as the primary strategy for updating deployments.

4. Canary Deployment: Kruise provides native support for canary deployments, allowing users to perform gradual rollouts of new versions with minimal impact on the overall system. It allows for automated monitoring of metrics to evaluate the success of the new version before fully rolling it out. Kubernetes does not have built-in support for canary deployments, although it can be achieved using third-party tools or custom configurations.

5. Rollback Capabilities: Kruise simplifies the process of rolling back deployments by providing a rollback API. With a single command or API call, users can easily revert to a previous stable version of an application. Kubernetes also supports rollback functionality through its deployment resources, but the process might require several steps and manual interventions.

6. Custom Resources: Kruise introduces the concept of custom resources, allowing users to define their own application-specific resources and controllers. This feature enables easy extensibility and customization of Kruise to specific application requirements. Kubernetes has a more rigid structure with predefined resources and controllers, restricting the ability to define custom resources.

In summary, Kruise extends Kubernetes by providing higher-level capabilities for application management, advanced update strategies like canary deployments, simplified rollback functionalities, and the ability to define custom resources. These features make Kruise a valuable tool for managing complex application workloads on top of the powerful container orchestration capabilities offered by Kubernetes.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Kubernetes, Kruise

Simon

Senior Fullstack Developer at QUANTUSflow Software GmbH

Apr 27, 2020

Decidedon

GitHub

GitHub Pages

Markdown

Our whole DevOps stack consists of the following tools:

@{GitHub}|tool:27| (incl. @{GitHub Pages}|tool:683|/@{Markdown}|tool:1147| for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
Respectively @{Git}|tool:1046| as revision control system
@{SourceTree}|tool:1599| as @{Git}|tool:1046| GUI
@{Visual Studio Code}|tool:4202| as IDE
@{CircleCI}|tool:190| for continuous integration (automatize development process)
@{Prettier}|tool:7035| / @{TSLint}|tool:5561| / @{ESLint}|tool:3337| as code linter
@{SonarQube}|tool:2638| as quality gate
@{Docker}|tool:586| as container management (incl. @{Docker Compose}|tool:3136| for multi-container application management)
@{VirtualBox}|tool:774| for operating system simulation tests
@{Kubernetes}|tool:1885| as cluster management for docker containers
@{Heroku}|tool:133| for deploying in test environments
@{nginx}|tool:1052| as web server (preferably used as facade server in production environment)
@{SSLMate}|tool:2752| (using @{OpenSSL}|tool:3091|) for certificate management
@{Amazon EC2}|tool:18| (incl. @{Amazon S3}|tool:25|) for deploying in stage (production-like) and production environments
@{PostgreSQL}|tool:1028| as preferred database system
@{Redis}|tool:1031| 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.

12.8M views12.8M

Comments

Detailed Comparison

Kubernetes	Kruise
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.	Attempts to fill such gap by offering a set of controllers as the supplement to manage new workloads in Kubernetes.
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	Advanced StatefulSet: An enhanced version of default StatefulSet with extra functionalities such as inplace-update, sharding by namespace; BroadcastJob: A job that runs pods to completion across all the nodes in the cluster; SidecarSet: A controller that injects sidecar container into the pod spec based on selectors.
Statistics
GitHub Stars -	GitHub Stars 5.1K
GitHub Forks -	GitHub Forks 832
Stacks 61.2K	Stacks 1
Followers 52.8K	Followers 7
Votes 685	Votes 0
Pros & Cons
Pros 166 Leading docker container management solution 130 Simple and powerful 108 Open source 76 Backed by google 58 The right abstractions Cons 16 Steep learning curve 15 Poor workflow for development 8 Orchestrates only infrastructure 4 High resource requirements for on-prem clusters 2 Too heavy for simple systems	No community feedback yet
Integrations
Vagrant Docker Rackspace Cloud Servers Microsoft Azure Google Compute Engine Ansible Google Kubernetes Engine	Docker

What are some alternatives to Kubernetes, Kruise?

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.

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.

Tutum

Tutum lets developers easily manage and run lightweight, portable, self-sufficient containers from any application. AWS-like control, Heroku-like ease. The same container that a developer builds and tests on a laptop can run at scale in Tutum.

Portainer

It is a universal container management tool. It works with Kubernetes, Docker, Docker Swarm and Azure ACI. It allows you to manage containers without needing to know platform-specific code.

Codefresh

Automate and parallelize testing. Codefresh allows teams to spin up on-demand compositions to run unit and integration tests as part of the continuous integration process. Jenkins integration allows more complex pipelines.

CAST.AI

It is an AI-driven cloud optimization platform for Kubernetes. Instantly cut your cloud bill, prevent downtime, and 10X the power of DevOps.

k3s

Certified Kubernetes distribution designed for production workloads in unattended, resource-constrained, remote locations or inside IoT appliances. Supports something as small as a Raspberry Pi or as large as an AWS a1.4xlarge 32GiB server.

Flocker

Flocker is a data volume manager and multi-host Docker cluster management tool. With it you can control your data using the same tools you use for your stateless applications. This means that you can run your databases, queues and key-value stores in Docker and move them around as easily as the rest of your app.

Kitematic

Simple Docker App management for Mac OS X

Related Comparisons

Kruise vs Kubernetes: What are the differences?

Key Differences Between Kruise and Kubernetes

Kruise vs Kubernetes

Overview

Kruise vs Kubernetes: What are the differences?