search

bookingcom / shipper

Kubernetes native multi-cluster canary or blue-green rollouts using Helm
Apache License 2.0
733 stars 39 forks source link

Fixed historical release awakening due to targetStep resolve inconsistency #286

Closed osdrv closed 4 years ago

osdrv commented 4 years ago

Due to a change introduced in #285, shipper strarted re-activating historical releases due to the way targetStep is resolved. The aforementioned step changed the composition of the pipeline and caused historical releases to be re-scheduled. This caused some historical items to re-activate their capacity and target targets. This change mainly reverts the re-composition of the pipeline and ensures the historical releases never re-activate their predecessors.

Signed-off-by: Oleg Sidorov oleg.sidorov@booking.com