- Home
- Progressive Delivery Software
- Kruise Rollouts
On the recordRead 1 Oct 202625 facts
Kruise Rollouts
On the record
- 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.openkruise.io · read 1 Oct 2026
- cluster requirement
- Installation requires a Kubernetes cluster running Kubernetes version 1.19 or later.openkruise.io · read 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.github.com · read 1 Oct 2026
- Extensibility
- Pluggable Lua scripts can extend traffic routing to other Kubernetes traffic protocols and custom resources.openkruise.io · read 1 Oct 2026
- Gateway integration
- Service-mesh integration is provided through Gateway API.openkruise.io · read 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.cncf.io · read 30 Sep 2026
- HPA compatibility
- The project documents compatibility with Horizontal Pod Autoscaler and other workload-referencing controllers.openkruise.io · read 1 Oct 2026
- HPA support
- The documentation states that Kruise Rollouts is compatible with Horizontal Pod Autoscaler.openkruise.io · read 30 Sep 2026
- Ingress integrations
- Documented ingress integrations include NGINX, ALB and Higress.openkruise.io · read 1 Oct 2026
- Installation
- The documented Helm installation command installs chart version 0.6.2 from the OpenKruise chart repository.openkruise.io · read 1 Oct 2026
- integrations
- Its documented ingress integrations are NGINX, ALB and Higress, and it supports service-mesh integration through Gateway API.openkruise.io · read 30 Sep 2026
- License
- Kruise Rollout is licensed under the Apache License, Version 2.0.github.com · read 1 Oct 2026
- maintainers
- The repository states that the project is maintained by contributors from both OpenKruise and KubeVela communities.github.com · read 30 Sep 2026
- Purpose
- Kruise Rollouts provides progressive delivery for Kubernetes, including canary, blue-green, multi-batch and A/B testing modes.openkruise.io · read 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.openkruise.io · read 30 Sep 2026
- Requirements
- Installation requires a Kubernetes cluster running version 1.19 or newer and Helm 3.1 or newer for Helm installation.openkruise.io · read 1 Oct 2026
- Resource tradeoff
- Blue-green releases consume double the resources because old and new version instances coexist.openkruise.io · read 1 Oct 2026
- Rollback behavior
- Kruise Rollout does not provide direct rollback and instead recommends rolling back the workload specification.openkruise.io · read 1 Oct 2026
