We have noticed three instances of an orphan resource in your Kubernetes configuration files. Deploying Kubernetes resources that are not being actively used or referenced by any other resources in the cluster can lead to orphan resources. These orphan resources consume unnecessary resources and can potentially cause confusion or clutter within the cluster. Additionally, we provide anecdotal evidence from topolvm-topolvm#484 regarding the orphan resource defect.
cluster role postgres-pod does not have any relevant cluster role binding which can be considered orphan resource.
Orphan resource should not be deployed or cluster role should have necessary cluster role binding.
Please, answer some short questions which should help us to understand your problem / question better?
**Which image of the operator are you using? ghcr.io/zalando/postgres-operator:v1.12.2
Where do you run it - cloud or metal? Kubernetes or OpenShift? [AWS K8s | GCP ... | Bare Metal K8s] Bare Metal K8s
Are you running Postgres Operator in production? [yes | no] no
Type of issue? [Bug report, question, feature request, etc.]
bug report
Some general remarks when posting a bug report:
Please, check the operator, pod (Patroni) and postgresql logs first. When copy-pasting many log lines please do it in a separate GitHub gist together with your Postgres CRD and configuration manifest.
If you feel this issue might be more related to the Spilo docker image or Patroni, consider opening issues in the respective repos.
We have noticed three instances of an orphan resource in your Kubernetes configuration files. Deploying Kubernetes resources that are not being actively used or referenced by any other resources in the cluster can lead to orphan resources. These orphan resources consume unnecessary resources and can potentially cause confusion or clutter within the cluster. Additionally, we provide anecdotal evidence from topolvm-topolvm#484 regarding the orphan resource defect.
cluster role postgres-pod does not have any relevant cluster role binding which can be considered orphan resource.
Orphan resource should not be deployed or cluster role should have necessary cluster role binding.
Please, answer some short questions which should help us to understand your problem / question better?
bug report
Some general remarks when posting a bug report: