pod_environment_secret for cronjob

[mcatany]

• Which image of the operator are you using? ghcr.io/zalando/postgres-operator:v1.11.0
• Where do you run it - cloud or metal? Kubernetes
• Are you running Postgres Operator in production? yes
• Type of issue? Feature Request

We have set for our operator pod_environment_secret variable, so variables like AWS_ACCESS_KEY_ID are not hardcoded in the pod specification. The problem is that we have the logicalbackup enabled and the cronjob for that doesn't use it, but hardcodes the values of the envars. Is there any way to do that? Or does the possibility of implement that feature in the near future?

The code is here: https://github.com/zalando/postgres-operator/blob/68c4b496365f02afb57b9066492dfa319120622a/pkg/cluster/k8sres.go#L2512