You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IgnoreDifferences for CustomResource objects is not working. What have I done:
tested if I understood IgnoreDifferences syntax. I tested with standard builtin objects like replicas and this was working as expected
tested with multiple helmcharts which use custom resource object, and always encountered same issue. I will provide an example based on a small project external-dns, which will make it easy to reproduce
ArgoCD reports outofsync condition despite the fact that the changed objects are defined under IgnoreDifferences
To Reproduce
It is assumed that ArGoCD server v2.13.2 is installed
Create App in ArgoCD, with following settings (also provided in file: argocd-app.yaml). This will create namespace external-dns with external-dns application and the CRD dnsendpoints.externaldns.k8s.io
Logs
Attached are the logs which appeared after changing the dnsendpoint
The following command was used to gather the logs:
kubectl -n argocd logs -f argocd-application-controller-0 -c argocd-application-controller
Checklist:
argocd version
.IgnoreDifferences for CustomResource objects is not working. What have I done:
ArgoCD reports outofsync condition despite the fact that the changed objects are defined under IgnoreDifferences
To Reproduce
It is assumed that ArGoCD server v2.13.2 is installed
recordTTL to another value
kubectl -n external-dns edit DNSEndpoint ns-record
Expected behavior
I expect that ArgoCD does not report outofsync for objects which are defined under IgnoreDifferences
I expected Sync Status to be "Synced" because ArgoCD should have ignored any changes on the DNSendpoint
Screenshots
A screenshot has been added which shows the detected diff:
Version
Logs
Attached are the logs which appeared after changing the dnsendpoint
The following command was used to gather the logs:
kubectl -n argocd logs -f argocd-application-controller-0 -c argocd-application-controller
The text was updated successfully, but these errors were encountered: