Wait for replacing canary

[paichinger]

Hey Argo People!

We're currently evaluating and testing argo rollouts as a tool for doing progressive delivery at our company. While testing it I encountered the following behavior (using nginx+canary+header-based routing):

1. I have an app on version 1
2. I trigger a new release of the app (version 2)
3. a new canary with version 2 is deployed and the correct traffic is routed to it
4. I pause the canary
5. I deploy another version of the same app (version 3)
6. The stable version of the app (version 1) gets all the traffic until version 3 is ready

We are looking for an option for some of our apps to prevent that a customer (identified by header) will ever end up at an older version again. So in this case (step 6) all the requests should end up at version 2 until version 3 is ready.

Is there a way to make argo rollouts work like that?