Jesse Suen

Ah yes, you are right about that unfortunately.

When trying to reproduce this, it seems to be working as expected: ```yaml apiVersion: argoproj.io/v1alpha1 kind: Rollout metadata: name: cat-fact labels: cat-fact-id: 5887e1d85c873e0011036889 # this must be modified at same...

If it turns out that the label update happens after the pod spec update, and it is difficult to change them at the same time, then the following workaround may...

Spoke with the user and clarified that they are using the workloadRef feature. So there is a timing issue similar to what I described above. What happens is: 1. Deployment...

One consideration is that because runs can be synthesized from multiple templates, we would need to determine what to do if ttl disagreed. I guess we would need to take...

> we could maybe do some heuristic but I am also ok with it just being on the AnalysisRun itself, especially as a first pass. Given the two options, I...

I suspect the problem to be here: https://github.com/argoproj/argo-rollouts/blob/master/rollout/trafficrouting.go#L216-L226 In the case of canary, we properly check that canary replicas are available: ```golang atDesiredReplicaCount := replicasetutil.AtDesiredReplicaCountsForCanary(c.rollout, c.newRS, c.stableRS, c.otherRSs, nil) if...

This turned out to be an issue with a specific fork of rollouts modified to work Contour, and how Contour would encounter 503s when modifying the HTTPProxy. Rollouts does properly...

I thought the informer writeback solved a lot of our issues. Has this caused problems?

Which traffic provider integration are you using / asking to use this with? Or are you asking about stableService (and not ingress)