Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

Kruise Rollouts

openkruise.io

  • Free plan
  • API
  • Self-hosted
6.9 Club score Visit openkruise.io

What Kruise Rollouts is

Kruise Rollouts is free, open-source software for progressive delivery on Kubernetes. It provides canary, blue-green, multi-batch, and A/B testing modes with weighted traffic shifting and end-to-end canary deployment. Multi-batch updates support Deployment, CloneSet, StatefulSet, Advanced StatefulSet, Advanced DaemonSet, and DaemonSet. Canary updates apply to Deployment, while blue-green updates apply to Deployment and CloneSet. HTTP-header and cookie-based controls support A/B tests. Documented ingress integrations include NGINX, ALB, and Higress, while service-mesh integration uses Gateway API. Pluggable Lua scripts can extend traffic handling to other protocols and custom resources. Kruise Rollouts works as a bypass component for new or existing workloads without replacing controllers or migrating pods, and the documentation states compatibility with Horizontal Pod Autoscaler. Installation requires Kubernetes 1.19 or later; Helm installation requires version 3.1 or later. Blue-green releases use only v1beta1, require a Rollout newer than 0.5.0, and consume double resources while both versions run.

Who it suits

Kruise Rollouts suits Kubernetes operators managing staged releases across several workload types. It is self-hosted and requires a Kubernetes cluster plus Helm for the documented installation route.

Good to know, and what to watch

  • Supports canary, blue-green, multi-batch, and A/B modes
  • Works with existing workload objects
  • Provides weighted traffic shifting
  • Integrates with NGINX, ALB, Higress, and Gateway API
  • Compatible with Horizontal Pod Autoscaler
  • Requires Kubernetes 1.19 or later
  • Blue-green supports only Deployment and CloneSet
  • Blue-green releases consume double resources
  • No direct rollback is provided

The verdict

Kruise Rollouts adds multiple progressive-delivery strategies without replacing workload controllers. Review its blue-green limits and rollback workflow before adopting it for production releases.

What the maker publishes

Blue-green limit
Blue-green strategy applies only to Deployment and CloneSet, supports only the v1beta1 API, and requires a Rollout version newer than 0.5.0. source
cluster requirement
Installation requires a Kubernetes cluster running Kubernetes version 1.19 or later. source
Existing workloads
Kruise Rollouts is a bypass component that can be applied to newly created or existing workload objects without replacing workload controllers. source
extensibility
Pluggable Lua scripts can extend Kruise Rollouts to other Kubernetes traffic protocols, including custom resources. source
Extensibility
Pluggable Lua scripts can extend traffic routing to other Kubernetes traffic protocols and custom resources. source
Gateway integration
Service-mesh integration is provided through Gateway API. source
governance
OpenKruise is a Cloud Native Computing Foundation incubating project accepted on November 10, 2020 and moved to incubating maturity on March 2, 2023. source
HPA compatibility
The project documents compatibility with Horizontal Pod Autoscaler and other workload-referencing controllers. source
HPA support
The documentation states that Kruise Rollouts is compatible with Horizontal Pod Autoscaler. source
Ingress integrations
Documented ingress integrations include NGINX, ALB and Higress. source
installation
It can be installed with Helm version 3.1 or later, using the openkruise/kruise-rollout chart version 0.6.2 shown in the installation documentation. source
Installation
The documented Helm installation command installs chart version 0.6.2 from the OpenKruise chart repository. source
integrations
Its documented ingress integrations are NGINX, ALB and Higress, and it supports service-mesh integration through Gateway API. source
license
Kruise Rollouts is licensed under the Apache License, Version 2.0. source
License
Kruise Rollout is licensed under the Apache License, Version 2.0. source
maintainers
The repository states that the project is maintained by contributors from both OpenKruise and KubeVela communities. source
purpose
Kruise Rollouts provides progressive delivery for Kubernetes, including canary, blue-green, multi-batch and A/B testing modes. source
Purpose
Kruise Rollouts provides progressive delivery for Kubernetes, including canary, blue-green, multi-batch and A/B testing modes. source
release strategies
It supports multi-batch updates for Deployment, CloneSet, StatefulSet, Advanced StatefulSet, Advanced DaemonSet and DaemonSet, plus canary updates for Deployment and blue-green updates for Deployment and CloneSet. source
Requirements
Installation requires a Kubernetes cluster running version 1.19 or newer and Helm 3.1 or newer for Helm installation. source
Resource tradeoff
Blue-green releases consume double the resources because old and new version instances coexist. source
Rollback behavior
Kruise Rollout does not provide direct rollback and instead recommends rolling back the workload specification. source
rollback limit
Kruise Rollout does not provide direct rollback and instead expects users to roll back the workload specification, using native rolling upgrade behavior. source
rollout controls
Users can pause an in-progress rollout with spec.strategy.paused and disable a completed rollout with spec.disabled. source

Checked against the maker's pages on 1 Oct 2026.