Aliaksei Venski

I hit into this problem as well. I tried to set selectorLabels in values files, but my custom selector label isn't being copied to primary from canary deployment spec. @aryan9600...

I noticed one more thing - after unsuccessful promotion deployment rolled back, then after 5-10 seconds I see 'New revision detected' again and flagger tries to promote failed deployment second...

@aryan9600 could you help please? I looked at https://github.com/fluxcd/flagger/issues/1227 and still do not know how to resolve this.

I left just 'app.kubernetes.io/instance' as single selector label, now all services have this label as a selector, so I do everything correctly. But if I specify more than one label...

Regarding deployment selector labels - they are changing only if you delete and then install helm release, so flagger operator doesn't modify primary deployment selector labels on the fly (works...

Hey @aryan9600, any comments on this? You see that users face this issue having an impact from small to high? Almost 1 year after issue is created and no feedback...

P.S.: recently we updated flagger to latest, issue still persists.