Operator not creating secrets in secretNamespace

[0xcd0e]

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

I am trying to create a cluster and have it write the LOGIN credentials to another namespace. I have enabled enable_cross_namespace_secret and the operator logs are claiming they are creating the secret in another namespace, but the secret is never created. after removing secretNamespace from preparedDatabases, the secret gets created in the operator NS.

pgdb.yaml: https://gist.github.com/0xcd0e/0b8385337bed320bedc2b8d6572c6244
values.yaml: https://gist.github.com/0xcd0e/fe994fc61fab70cb79f61f93467a19b9
logs.txt: https://gist.github.com/0xcd0e/dcdd4828065e360dd75ac23667ffaf19