# Failed to create Pod: patroni-version-check

**URL:** <https://forums.percona.com/t/failed-to-create-pod-patroni-version-check/39671>\
**Category:** Percona Operator for PostgreSQL\
**Created:** [October 31, 2025, 5:16pm UTC](https://forums.percona.com/t/failed-to-create-pod-patroni-version-check/39671 "2025-10-31T17:16:05Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Luke](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/luke/32/22520_2.png) [@Luke](https://forums.percona.com/u/Luke)\
**Post date:** [October 31, 2025, 5:16pm UTC](https://forums.percona.com/t/failed-to-create-pod-patroni-version-check/39671/1 "2025-10-31T17:16:05Z")

</div>

## Description:

An error is logged during reconciliation when attempting to create the `patroni-version-check` pod if resources requests are set on the PerconaPGCluster resource.

This seems to be caused by the `PodLevelResources` feature gate that was introduced in kubernetes 1.32 and enabled by default in 1.34. In v2.7.0 of the controller, the version-check pod defaults to the `ResourceRequirements` of the first `instance` which now exceeds the pod-level requirements.

**TL;DR** : The main branch already has a fix (see additional information below) so my ultimate question is what is the timeline for the next release that will contain the fix? Thanks in advance 🙂

## Steps to Reproduce:

Create a `PerconaPGCluster` with resource requirements defined on the first instance: `spec.instances.0.resources.requests`

## Version:

Percona Postgresql Operator: 2.7.0  
Kubernetes: 1.34.1

## Logs:

```auto
check patroni version: failed to create pod to check patroni version: Pod \"postgres-infra-patroni-version-check\" is invalid: spec.resources.requests[memory]: Invalid value: \"32Mi\": must be greater than or equal to aggregate container requests of 6Gi"

```

## Expected Result:

A postgres cluster is successfully deployed.

## Actual Result:

The controller fails to create the cluster and logs the above error.

## Additional Information:

- Fixed by: [K8SPG-879 patroni version check pod and container should align the re… · percona/percona-postgresql-operator@541cb1f · GitHub](https://github.com/percona/percona-postgresql-operator/commit/541cb1f7df5928b1c29aa1389888068b5417d9b6)

---

<div class="post-metadata">

**Author:** ![eleonora.zinchenko](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/eleonora.zinchenko/32/19132_2.png) [@eleonora.zinchenko](https://forums.percona.com/u/eleonora.zinchenko)\
**Post date:** [November 3, 2025, 9:21am UTC](https://forums.percona.com/t/failed-to-create-pod-patroni-version-check/39671/2 "2025-11-03T09:21:01Z")

</div>

Hi,

Thanks for reaching out! PG operator v2.7.0 is not supported on k8s 1.34. This issue will be resolved in 2.8.0 that is planned for release in upcoming weeks.

---

<div class="post-metadata">

**Author:** ![Luke](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/luke/32/22520_2.png) [@Luke](https://forums.percona.com/u/Luke)\
**Post date:** [November 3, 2025, 2:18pm UTC](https://forums.percona.com/t/failed-to-create-pod-patroni-version-check/39671/3 "2025-11-03T14:18:03Z")

</div>

Thanks for the information 🙂 I’ll keep an eye out for the 2.8.0 release.

---

<div class="post-metadata">

**Author:** ![Slava\_Sarzhan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/slava_sarzhan/32/3196_2.png) [@Slava\_Sarzhan](https://forums.percona.com/u/Slava_Sarzhan)\
**Post date:** [November 29, 2025, 5:23pm UTC](https://forums.percona.com/t/failed-to-create-pod-patroni-version-check/39671/4 "2025-11-29T17:23:37Z")

</div>

@Luke The v2.8.0 was released two weeks ago. Did you have a chance to check it?