Is there an existing issue already for this bug?

• I have searched for an existing issue, and could not find anything. I believe this is a new bug.

I have read the troubleshooting guide

• I have read the troubleshooting guide and I think this is a new bug.

I am running a supported version of CloudNativePG

• I have read the troubleshooting guide and I think this is a new bug.

Contact Details

No response

Version

1.26 (latest patch)

What version of Kubernetes are you using?

1.31

What is your Kubernetes environment?

Cloud: Amazon EKS

How did you install the operator?

YAML manifest

What happened?

We deploy pooler pods with lower requests.cpu: 500m / request.memory: 50Mi to aid with consolidation.

But the bootstrap-controller init container is using requests.cpu: 1 / requests.memory: 1Gi and k8s scheduler is using this to place the pod.

The deployment should set the initContainer resources to match the pgbouncer resources.

Cluster resource

Relevant log output

Code of Conduct

• I agree to follow this project's Code of Conduct