StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Container Registry
  4. Container Tools
  5. Kruise vs Weave

Kruise vs Weave

OverviewComparisonAlternatives

Overview

Weave
Weave
Stacks50
Followers72
Votes7
Kruise
Kruise
Stacks1
Followers7
Votes0
GitHub Stars5.1K
Forks832

Kruise vs Weave: What are the differences?

  1. Deployment Kruise allows for incremental and rolling updates of application deployments without downtime, while Weave focuses on providing automation and management for Kubernetes applications, focusing more on traffic management and observability.

  2. Traffic Management Weave provides advanced networking and traffic management capabilities, including load balancing, service discovery, and monitoring, whereas Kruise primarily focuses on deployment automation and management features.

  3. Observability With Weave, users can benefit from comprehensive monitoring and observability tools to track and analyze application performance, whereas Kruise offers minimal native support for observability features.

  4. Resource Management Kruise offers resource management features such as resource orchestration and allocation, helping optimize resource utilization, while Weave places more emphasis on networking and service communication within Kubernetes clusters.

  5. Community Support Weave has a larger and more active community with extensive documentation and community support, making it easier for users to troubleshoot issues and get help, compared to Kruise, which has a smaller user base and community presence.

  6. Customization Options Weave provides more flexibility and customization options for users to customize and fine-tune their Kubernetes deployments, while Kruise offers a more streamlined and opinionated approach to application deployment and management.

In Summary, Kruise and Weave differ in their focus on deployment automation, traffic management, observability, resource management, community support, and customization options within Kubernetes environments.

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)
or
Manual

Detailed Comparison

Weave
Weave
Kruise
Kruise

Weave can traverse firewalls and operate in partially connected networks. Traffic can be encrypted, allowing hosts to be connected across an untrusted network. With weave you can easily construct applications consisting of multiple containers, running anywhere.

Attempts to fill such gap by offering a set of controllers as the supplement to manage new workloads in Kubernetes.

Virtual Ethernet Switch;Application isolation;Security;Host network integration;Service export;Service import;Multi-cloud networking;Multi-hop routing;Dynamic topologies;Container mobility;Fault tolerance
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
50
Stacks
1
Followers
72
Followers
7
Votes
7
Votes
0
Pros & Cons
Pros
  • 3
    Easy setup
  • 3
    Seamlessly with mesos/marathon
  • 1
    Seamless integration with application layer
No community feedback yet
Integrations
Docker
Docker
boot2docker
boot2docker
Docker
Docker
Kubernetes
Kubernetes

What are some alternatives to Weave, Kruise?

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.

Docker Compose

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

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

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

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

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

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

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

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.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana