Plug-and-Play Progressive Delivery for Kubernetes Built-in Workloads With OpenKrui...
summary
OpenKruise Rollout claims to add enterprise-grade progressive delivery to existing Kubernetes Deployments and StatefulSets without CRD migration by pausing controllers via a webhook and managing replicas in batches (examples: 5%, 20%, then 100%). It implements multibatch without duplicating workloads, canary, blue‑green and AB strategies, preserves HPA/PDB, validates new pods (minReadySeconds=infinite for blue‑green), wires into Ingress/Gateway APIs without a service mesh, emits labels (rolloutID, batchID) for Prometheus metrics, and demoed manual approval plus timed automation working end‑to‑end.
AI-written summary · about
chapters (16)
- 0:00OpenKruise Rollout intro
- 1:07What is OpenKruise
- 2:55Progressive delivery in OpenKruise
- 6:03Kubernetes workload limits
- 7:50OpenKruise enhancing workloads
- 9:42Argo Rollouts vs Flagger
- 11:47OpenKruise advanced features
- 13:10Basic Rollout API
- 14:35Multibatch strategy
- 16:42Multibatch rollout demo
- 17:45Blue-green with OpenKruise
- 18:52Gateway APIs traffic routing
- 21:12Live OpenKruise Rollout demo
- 24:43Q&A 1
- 26:10Q&A 2
- 27:57Q&A 3
related talks
49mCustomize Progressive Delivery for Your Own Workload and Traffic
51mProgressive Delivery in the Kubernetes era
36mProgressive Delivery in the Kubernetes era
48mProgressive Delivery in the Kubernetes Era
40mProgressive Delivery with Kubernetes and Argo Rollouts
46mProgressive Delivery in the Kubernetes era
43mCloud-Native Progressive Delivery
35mProgressive Delivery with Argo Rollouts