Summary

The feature is behind a flag. We should enable resource.ignoreResourceUpdatesEnabled: true by default the argocd-cm ConfigMap.

Motivation

No undesired effect has been reported since it has been implemented. Argo operators will likely experience problems until they find that flag and turn it on. If it is on by default, argo performance will be sustainable with default configurations for longer. CPU will be less and new/existing users are less likely to deploy Argo on instances with a lot of CPU request/limits, saving cost.

Proposal

• Set it to true by default
• For widely used Kubernetes resources that are known to have high churn, we should configure the ignore by default.