Using everest deploying pg error

Percona Everest
1

/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.21.0/pkg/internal/controller/controller.go:202 │
…
│ [spec.resources.requests[cpu]: Invalid value: “50m”: must be greater than or equal to aggregate container requests of 1, spec.resources.requests[memory]: Inva │
│ lid value: “32Mi”: must be greater than or equal to aggregate container requests of 2G, spec.resources.containers[0][memory].limits: Invalid value: “2G”: mu │
│ st be less than or equal to pod limits of 64Mi, spec.resources.containers[0][cpu].limits: Invalid value: “1”: must be less than or equal to pod limits of 100m │
│ ]”, “errorVerbose”: “Pod “postgresql-r7i-patroni-version-check” is invalid: [spec.resources.requests[cpu]: Invalid value: “50m”: must be greater than or equ │
│ al to aggregate container requests of 1, spec.resources.requests[memory]: Invalid value: “32Mi”: must be greater than or equal to aggregate container requests │
│ of 2G, spec.resources.containers[0][memory].limits: Invalid value: “2G”: must be less than or equal to pod limits of 64Mi, spec.resources.containers[0][cpu]. │
│ limits: Invalid value: “1”: must be less than or equal to pod limits of 100m]\

….

with simple default option make these error.
i gave a 2g of memory.
where 64MiB or other resource limit comes from?

2

Hi @jjpark ,

If you’re on k8s 1.34, this is a known issue with the PG operator that is fixed in 2.8.0. It will be available in the next Everest release. See - Jira

Meanwhile, please try to use k8s v1.33 or below

3

oh. thanks. i’ll happy to wait for next release.