Jesse Suen

Did you happen to go back to the previously deployed version or all these pod specs different from each other?

I think this might be fixed in v1.8. We were unexpectedly re-using job names in some circumstances. Would you be able to test/verify with the v1.8.0-rc2 candidate?

> Rollout controller in a infinity loop trying to reconcile a still referenced replicaset. > All reconciles in this rollout execute the isEscaleEvent, **_and will never make the service switch._**...

Can we try the tests in the other PR? To see what differences there are? https://github.com/argoproj/argo-cd/pull/16602/files#diff-4dec00983e470c56b48582b67b8ef5c1baf5216e202ec29fdff3233fa4aec501R1937-R2045 I understand this PR does a replace vs. the other does json merge, and...

> I expect that Kustomize probably respects that. > if the Kustomize user doesn't set openapi - maybe it defaults to a plain old JSON patch? Yes, I think you...

> we do generate the schema Ah, I forgot it lived in a different repo. Thanks. I didn't see it auto-generated in this PR so I incorrectly assumed it was...

Thinking about this some more, I think valuesObject behaving like SMP vs. json merge patch is completely moot. SMP matters most when there are merge keys in lists. But since...

We found this issue since we faced the same error. This appears to be a breaking behavior in the auth0 backend. In our case, we use auth0 API to configure...

> is it possible to implement a custom git webhook configuration that can be called arbitrarily If you are open to that route, then you may be able to work...

Note that even if we allowed configuring Argo CD to append the `--validate` arg when running the `helm template` command, the repo-server would still need to be given API server...