Release v0.6.0 · openkruise/rollouts

🎊 Support for blue-green style releases has been added (#214,#229,#238,#220,@myname4423)
⭐ Traffic loss during rollouts in certain scenarios is avoided (#226,#219,#222,@myname4423)

Enhanced flexibility by allowing free navigation between different steps within a rollout (#218,@myname4423)
Added support for HTTPQueryParamMatch and HTTPPathMatch of the Gateway API in traffic management (#204,@lujiajing1126)
Integrated RequestHeaderModifier into LuaData, facilitating its use with custom network references like Istio (#223,@lujiajing1126)
Introduced a composite provider to support multiple network providers (#224,@lujiajing1126)
Got the canary service selector patched from pod template metadata (#243,@lujiajing1126)
Patched label rollout-batch-id to pods even without rollout-id in the workload (#248,@PersistentJZH)
Upgraded Gateway API version from 0.5.1 to 0.7.1 and Kubernetes version from 1.24 to 1.26 (#237,@AiRanthem)
Enabled the option to skip canary service generation when using trafficRoutings.customNetworkRefs (#200,@myname4423)

Filtered out ReplicaSets not part of the current Deployment to prevent frequent scaling issues when multiple deployments share the same selectors (#191,@zhengjr9)
Synced the observed rollout-id to the BatchRelease CR status (#193,@veophi)
Checked deployment strategy during finalization to prevent random stuck states when used with KubeVela (#198,@phantomnat)
Resolved a Lua encoding structural error (#209,@ls-2018)
Corrected batch ID labeling in partition-style releases when pod recreation happens (#246,@myname4423)

Restricted the ability to set traffic percentage or match selectors in a partition-style release step when exceeding 30% replicas. Use the rollouts.kruise.io/partition-replicas-limit annotation to override this default threshold. Setting the threshold to 100% restores the previous behavior (#225,@myname4423)

Provide feedback