Jesse Suen

Looks like we support this for diffing customization so it makes sense to do for health checks.

Thank you everyone for your comments. There are at least 3 other issues around this topic (which I'll be duplicating shortly): https://github.com/argoproj/argo-cd/issues/5826, https://github.com/argoproj/argo-cd/issues/3988, https://github.com/argoproj/argo-cd/issues/4129. I brought up this feature in...

For those eagerly awaiting this Argo CD feature, I want to offer/suggest an alternative approach which is possible to do **_today_**. And I would not even consider it a "workaround"...

> 2. Support for chart repository authentication or OCI registries > It's unclear to me if the kustomize helm chart feature supports authentication or OCI registries properly, but this could...

Maybe this is a dumb question but will it have any impact of not showing the in-cluster cluster correctly (e.g. showing them as Unknown)?

> I'm glad to see this gaining traction again. From previous discussions, we thought that the sync retry feature would solve this problem in a more declarative way (e.g. reconcile...

I think argoproj/notification-engine library should be considered for powering this. This has support for configuring attachments and threaded messages

Note that I'm not necessarily suggesting we implement annotation-based support in events. I'm suggesting in code-reuse and standardizing on the configuration that the notification engine suppoert.

> To fix this performance issue, it seems we need to propagate the rollout's label to the analysisrun and it's pods. Please correct me if I miss anything. Thanks. You're...

> I realized that experiment and analysisrun have already have the rollout-pod-template-hash label. I think the issue is that: 1) Pods which AnalysisRuns create (i.e. from the Job) are not...