The priority between autoPromotionEnabled and the steps defined in the strategy section of an Argo Rollouts

[zitrocy]

Hi, folks!

I have a question. I've set rollout.yaml as follows, and I want autoPromotion to be in action as I intended.
However, it's not working as I thought.
Maybe it's because of the pause option in the configuration.
So, I'd like to know which one takes priority: autoPromotionEnabled or pause in the steps?

 strategy:
   canary:
     maxSurge: 25%
     maxUnavailable: 0
     autoPromotionEnabled: true
     steps:
     - setWeight: 20
     - pause: {}

I thought autoPromotionEnabled takes priority over pause, as indicated in this link: Link Text,
but it wasn't the case.

Thanks for any help in advance,

[kostis-codefresh]

As explained in the documentation page that you linked autoPromotionEnabled is a property for Blue/Green deployments. Not canaries

The canary options are here https://argo-rollouts.readthedocs.io/en/stable/features/canary/

Can you explain a bit your use case? If you want auto-promotion you should put a timeout in the pause step (e.g. 5 minutes). Now the canary stops there for ever.

[cychoi34]

Thanks for the kind reply, Kostis, It was a lot helpful!

[cychoi34]

We just set it with the pause step instead of autoPromotionEnabled.