Kruise Rollouts

What it does

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.checked 1 Oct 2026

cluster requirement

Installation requires a Kubernetes cluster running Kubernetes version 1.19 or later.checked 30 Sep 2026

Existing workloads

Kruise Rollouts is a bypass component that can be applied to newly created or existing workload objects without replacing workload controllers.checked 1 Oct 2026

extensibility

Pluggable Lua scripts can extend Kruise Rollouts to other Kubernetes traffic protocols, including custom resources.checked 30 Sep 2026

Extensibility

Pluggable Lua scripts can extend traffic routing to other Kubernetes traffic protocols and custom resources.checked 1 Oct 2026

Gateway integration

Service-mesh integration is provided through Gateway API.checked 1 Oct 2026

governance

OpenKruise is a Cloud Native Computing Foundation incubating project accepted on November 10, 2020 and moved to incubating maturity on March 2, 2023.checked 30 Sep 2026

HPA compatibility

The project documents compatibility with Horizontal Pod Autoscaler and other workload-referencing controllers.checked 1 Oct 2026

HPA support

The documentation states that Kruise Rollouts is compatible with Horizontal Pod Autoscaler.checked 30 Sep 2026

Ingress integrations

Documented ingress integrations include NGINX, ALB and Higress.checked 1 Oct 2026

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.checked 30 Sep 2026

Installation

The documented Helm installation command installs chart version 0.6.2 from the OpenKruise chart repository.checked 1 Oct 2026

integrations

Its documented ingress integrations are NGINX, ALB and Higress, and it supports service-mesh integration through Gateway API.checked 30 Sep 2026

license

Kruise Rollouts is licensed under the Apache License, Version 2.0.checked 30 Sep 2026

License

Kruise Rollout is licensed under the Apache License, Version 2.0.checked 1 Oct 2026

maintainers

The repository states that the project is maintained by contributors from both OpenKruise and KubeVela communities.checked 30 Sep 2026

purpose

Kruise Rollouts provides progressive delivery for Kubernetes, including canary, blue-green, multi-batch and A/B testing modes.checked 30 Sep 2026

Purpose

Kruise Rollouts provides progressive delivery for Kubernetes, including canary, blue-green, multi-batch and A/B testing modes.checked 1 Oct 2026

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.checked 30 Sep 2026

Requirements

Installation requires a Kubernetes cluster running version 1.19 or newer and Helm 3.1 or newer for Helm installation.checked 1 Oct 2026

Resource tradeoff

Blue-green releases consume double the resources because old and new version instances coexist.checked 1 Oct 2026

Rollback behavior

Kruise Rollout does not provide direct rollback and instead recommends rolling back the workload specification.checked 1 Oct 2026

rollback limit

Kruise Rollout does not provide direct rollback and instead expects users to roll back the workload specification, using native rolling upgrade behavior.checked 30 Sep 2026

rollout controls

Users can pause an in-progress rollout with spec.strategy.paused and disable a completed rollout with spec.disabled.checked 30 Sep 2026