Yuan Tang
You'll have to enable health assessment for Application CRD. See instructions in https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/1.7-1.8/#health-assessment-of-argoprojioapplication-crd-has-been-removed
@alexec Would you like to take a look?
Please fill out the issue template.
@JPZ13 This seems related to pod name change. Would you like to take a look?
I'll see if I can reproduce locally.
I ran it 20 times and it failed only once locally.
@juliev0 That test case should be fixed in https://github.com/argoproj/argo-workflows/pull/9156.
It's not in the core installation intentionally but in the quickstart manifests, e.g. https://github.com/argoproj/argo-workflows/blob/master/manifests/quick-start-mysql.yaml See https://github.com/argoproj/argo-workflows/blob/master/manifests/quick-start/base/agent-role.yaml
cc @alexec who added this in https://github.com/argoproj/argo-workflows/pull/7999 The idea is to have clear permissions for the additional features and avoid excessive permissions on workflows.
Would you like to send a PR and test it out? I'd also make sure your cluster has stable connection to that OSS address.