Feature Request: Specific pod annotations

• Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.10.0
• Where do you run it - cloud or metal? Kubernetes or OpenShift? Tanzu on vSphere
• Are you running Postgres Operator in production? yes
• Type of issue? Feature request

We'd like to use the telegraf operator to fetch database logs. This operator is using pod annotations to install its sidecar to. The manifest parameter podAnnotations allows to set these annotations, but they are propagated to every pod the operator manages. This e.g. includes logical backup and connection pooler pods, where the server logs obviously don't exist.

It would be nice to have a parameter to only set the pod annotations for the spilo pods.

A workaround for this could be to use the sidecars parameter to manually set the telegraf sidecar, but this would break how we do it with our other deployments.

Start by tracing where the manifest parameter podAnnotations is applied to managed pods, then compare the handling of Spilo, logical backup, and connection pooler pods. The change is complete when a parameter can target annotations to Spilo pods without propagating them to backup or pooler pods; check the relevant operator tests if available.