Ignore RepeatedResourceWarning

[caseyscarborough]

Is it possible to ignore/whitelist specific warnings as a non-issue, such as the RepeatedResourceWarning? We have a case where sometimes a RepeatedResourceWarning occurs but it's really not an issue and we would like the warning to be removed from the UI.

I've tried searching around but can't seem to find much on it except maybe this issue (#2115).

[KalenWessel]

I know this isn't an answer but I am also interested in the ability to ignore the RepeatedResourceWarning message, ideally on a case-by-case basis. This way files I know will show up can be ignored while new unexpected duplicates would trigger the warning.

[rsavage-nozominetworks]

I am also interested in discovering how to silence this message. According to the ArgoCD documentation, ArgoCD allows for an application to be sourced from multiple repos. If there is a duplicate resource, the last definition overrides. This is exactly what I want and need. However, I don't need the warning message because it's intended.

[noah-hein]

Interestingly enough the ArgoCD rbac page promotes creating multiple argocd-rbac-cm ConfigMaps to make it easier to manage the policy csv, which ends up throwing this warning.

[dannysauer]

Looking at the code which detects dups:

argo-cd/controller/state.go

Lines 422 to 432 in e5417e1

	for key, targets := range targetByKey {
	if len(targets) > 1 {
	now := metav1.Now()
	conditions = append(conditions, v1alpha1.ApplicationCondition{
	Type: v1alpha1.ApplicationConditionRepeatedResourceWarning,
	Message: fmt.Sprintf("Resource %s appeared %d times among application resources.", key.String(), len(targets)),
	LastTransitionTime: &now,
	})
	}
	result = append(result, targets[len(targets)-1])
	}

...it appears there is no test for a configuration option to silence the specific warning.

Though it should be entirely possible to add a configuration in the app which does suppress the warning. Maybe a list of resource_type/name strings?

[Bak3y]

Casting another vote for the ability to ignore warnings here.

My specific use case is I'm using a using a wrapper chart with multiple instances of the external-dns subchart (a common pattern for split DNS), the CRDs are identical and deduplicated correctly, ServerSideApply=true handles them fine, and the warning is pure noise with no way to suppress it.

EDIT - #28026