Kostis (Codefresh)

This can work as well. But I think that if we have a large number of extensions, a marketplace thing might be a good idea in the long run....

The proper solution is as you found out to remove the replicas field from deployment. And actually this is an HPA best practice unrelated to Argo Rollouts Even if you...

Fixed by https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-gatewayapi/pull/122

For those affected by this issue could you elaborate a bit on **WHEN** it happens? Just when starting a rollout? Upgrading the controller? Scaling back? Doing something else?

Maybe related to https://github.com/argoproj/argo-rollouts/issues/4393 ?

Please see discussion at * https://github.com/argoproj/argo-rollouts/issues/2737 * https://github.com/argoproj/argo-rollouts/issues/2088 For your use case it is much easier to use Argo CD pre/post hooks since they include this functionality already. Alternatively if...

I would assume that "finish" is on-rollout-completed and "start" is on-rollout-step-completed using a step number. This is what you have right now?