Ignore service annotations

[sdressler]

• Which image of the operator are you using?

registry.opensource.zalan.do/acid/postgres-operator:v1.6.2

• Where do you run it - cloud or metal? Kubernetes or OpenShift?

AWS EC2 with Rancher 2.5.7

• Are you running Postgres Operator in production?

No but planned.

• Type of issue? [Bug report, question, feature request, etc.]

Question / Feature request

• Details

I am running a test setup with 1 main and 1 replica. The overall setup worked fine, and the cluster is up and running. Occasionally, however, the cluster will re-sync and cuts connections to do so. I first thought it was caused by #1447 but then realized that Rancher caused the resync by adding a service annotation field.cattle.io/publicEndpoints. That is, I see messages like:

time="2021-05-03T11:28:20Z" level=info msg="reason: new service's annotations does not match the current one: Removed 'field.cattle.io/publicEndpoints'." cluster-name=default/magic-minimal-swarm64da-tpch-zwn
65w pkg=cluster

Since this is dynamically added, I cannot simply add it to custom_service_annotations (resp. I don't know whether it is possible to make this dynamic). So, is there a way currently to ignore certain annotations? If not, I'd be happy to make a PR given I get a pointer to the correct location.

[KingJ]

FYI, this has been implemented via #1823. The operator configuration now has a ignored_annotations parameter which accepts a list of annotations which the operator should ignore.

(#1823 was mentioned in the linked PR #1482, but didn't make it back to this issue - so I thought it best to mention here for anyone looking at this issue in the future!)

[FxKu]

Thanks @KingJ for the pointers. I will close this issue then.