In a blue/green strategy, is it possible to not terminate the previous version after rollout promote?

[gomgomshrimp]

Hi, all.

Just like the title.
Is there any way not to terminate previous version of replicaset?

For example, below is the state right after promote.

Name:            rollout-bluegreen
Namespace:       default
Status:          ✔ Healthy
Strategy:        BlueGreen
Images:          argoproj/rollouts-demo:blue
                 argoproj/rollouts-demo:green (stable, active)
Replicas:
  Desired:       1
  Current:       2
  Updated:       1
  Ready:         1
  Available:     1

NAME                                           KIND        STATUS     AGE  INFO
⟳ rollout-bluegreen                            Rollout     ✔ Healthy  31m
├──# revision:2
│  └──⧉ rollout-bluegreen-75695867f            ReplicaSet  ✔ Healthy  27m  stable,active
│     └──□ rollout-bluegreen-75695867f-8wcg5   Pod         ✔ Running  27m  ready:1/1
└──# revision:1
   └──⧉ rollout-bluegreen-5ffd47b8d4           ReplicaSet  ✔ Healthy  31m  delay:25s
      └──□ rollout-bluegreen-5ffd47b8d4-cbz2x  Pod         ✔ Running  31m  ready:1/1

After delay time, revision 1 replicaset terminating.

Name:            rollout-bluegreen
Namespace:       default
Status:          ✔ Healthy
Strategy:        BlueGreen
Images:          argoproj/rollouts-demo:green (stable, active)
Replicas:
  Desired:       1
  Current:       1
  Updated:       1
  Ready:         1
  Available:     1

NAME                                           KIND        STATUS         AGE  INFO
⟳ rollout-bluegreen                            Rollout     ✔ Healthy      32m
├──# revision:2
│  └──⧉ rollout-bluegreen-75695867f            ReplicaSet  ✔ Healthy      28m  stable,active
│     └──□ rollout-bluegreen-75695867f-8wcg5   Pod         ✔ Running      28m  ready:1/1
└──# revision:1
   └──⧉ rollout-bluegreen-5ffd47b8d4           ReplicaSet  • ScaledDown   32m
      └──□ rollout-bluegreen-5ffd47b8d4-cbz2x  Pod         ◌ Terminating  32m  ready:1/1
Name:            rollout-bluegreen
Namespace:       default
Status:          ✔ Healthy
Strategy:        BlueGreen
Images:          argoproj/rollouts-demo:green (stable, active)
Replicas:
  Desired:       1
  Current:       1
  Updated:       1
  Ready:         1
  Available:     1

NAME                                           KIND        STATUS         AGE  INFO
⟳ rollout-bluegreen                            Rollout     ✔ Healthy      32m
├──# revision:2
│  └──⧉ rollout-bluegreen-75695867f            ReplicaSet  ✔ Healthy      28m  stable,active
│     └──□ rollout-bluegreen-75695867f-8wcg5   Pod         ✔ Running      28m  ready:1/1
└──# revision:1
   └──⧉ rollout-bluegreen-5ffd47b8d4           ReplicaSet  • ScaledDown   32m
      └──□ rollout-bluegreen-5ffd47b8d4-cbz2x  Pod         ◌ Terminating  32m  ready:1/1

I don't want the previous version of replicaset terminating

[kostis-codefresh]

The whole point of blue/green is to have a single color after promotion has finished.

If you want to have 2 versions in parallel for a long time have you seen experiments? https://argoproj.github.io/argo-rollouts/features/experiment/#use-cases-of-experiments

Maybe you could describe a bit your use case?