Mubarak Jama

many folks reported this issue in slack as well https://cloud-native.slack.com/archives/C01UKS2NKK3/p1657184741979379 @pasha-codefresh @RaviHari @alexmt is something you can help with?

would this trigger condition prevent sending the false alert? i.e wait 2 mins before sending degraded notifications ```yaml trigger.on-health-degraded: | - description: Application has degraded oncePer: app.status.sync.revision send: - app-health-degraded...

if this issue hasn’t been resolved in latest argo-cd v2.4.0, then i think this issue should be resubmitted upstream because [notification code](https://github.com/argoproj/argo-cd/tree/master/notification_controller/controller) was merged with [argo-cd repo](https://github.com/argoproj/argo-cd/issues). I doubt issues...

Does this limitation still apply in current version?

The new format as shown in [argocd docs examples](https://argo-cd.readthedocs.io/en/stable/operator-manual/health/) was introduced in ArgoCD v1.2.0 and explained in the [blog release here](https://blog.argoproj.io/argo-cd-v2-1-first-release-candidate-is-ready-c1aab7795638) So unless you're running an older version of argocd,...

You can find argocd built-in resource customizations here: https://github.com/argoproj/argo-cd/tree/master/resource_customizations

I think it's worth adding an explanation for `requeueAfterSeconds` and when can it be used in the [template spec page](https://argocd-applicationset.readthedocs.io/en/stable/Template/).

Yes, argo-rollouts is running in HA mode with 2 replicas using the [community chart](https://github.com/argoproj/argo-helm/tree/main/charts/argo-rollouts). it was release/rollout number 43 for this service (which you can tell by the replicaset version)...

@darken99 @iakov-aws the issue is that providing csv file is supported during the initial deployment `cid-cmd deploy`. But if I want to update the dashboards with new accounts, using `cid-cmd...

One of our apps with over 170 pods suffered an outage due to this bug https://github.com/argoproj/argo-rollouts/issues/2235. Reading this issue, it seems this bug always had the potential to hit since...