percona-postgres-operator creates resources which want ArgoCD to delete

[RogerSik]

The percona postgres operator creates many resources. I don't know how to hide them from ArgoCD.

An idea would be to filter by labels. Than it could take the managed-by: label.

  labels:
    app.kubernetes.io/instance: awx-db
    app.kubernetes.io/managed-by: percona-postgresql-operator
    app.kubernetes.io/name: percona-postgresql
    app.kubernetes.io/part-of: percona-postgresql

[ChristianCiach]

Please have a look at https://argo-cd.readthedocs.io/en/stable/faq/#why-is-my-app-out-of-sync-even-after-syncing

[RogerSik]

Yeah but i have this issue only with percona-operator and than i would do a global change only for an operator. And what i do when another operator has the same problem?

Or is it possible to change the instanceLabelKey only for one argocd app?

[ChristianCiach]

Or is it possible to change the instanceLabelKey only for one argocd app?

No, but I would highly recommend to change the key anyway. You will have this issue for many other apps, because many helm charts set the app.kubernetes.io/instance label on the pods.

The Argo CD helm chart even sets this key by default: https://github.com/argoproj/argo-helm/blob/d1f5d50dcdd436329f5baa2cea94a969b4b087d9/charts/argo-cd/values.yaml#L173

[RogerSik]

I see now what you mean. I thought that this is already set but this was an old setup which i inheritated. Moved now to helm to get this useful (and other default) values.

Now it is working fine. Thank you!