Skip to content

Conversation

@gkech
Copy link
Contributor

@gkech gkech commented Oct 23, 2025

K8SPG-882 Powered by Pull Request Badge

CHANGE DESCRIPTION

Problem:

The current patroni version check implementation can be completely skipped. We can assume by default patroni version 4.x. The operator should be able to determine the patroni version by running a patronictl version command to an instance pod, database container and assign this value to the pg status, as well to an annotation pgv2.percona.com/patroni-version. The custom patroni version annotation option will not continue to be support with this version.

For cr 2.7 and older, the pgv2.percona.com/custom-patroni-version should continue to work. The patroni version check pod also should continue working for these cr versions.

Cause:
Short explanation of the root cause of the issue if applicable.

Solution:
Short explanation of the solution we are providing with this PR.

CHECKLIST

Jira

  • Is the Jira ticket created and referenced properly?
  • Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
  • Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

  • Is an E2E test/test case added for the new feature/change?
  • Are unit tests added where appropriate?

Config/Logging/Testability

  • Are all needed new/changed options added to default YAML files?
  • Are all needed new/changed options added to the Helm Chart?
  • Did we add proper logging messages for operator actions?
  • Did we ensure compatibility with the previous version or cluster upgrade process?
  • Does the change support oldest and newest supported PG version?
  • Does the change support oldest and newest supported Kubernetes version?

@gkech gkech marked this pull request as ready for review October 27, 2025 12:21
egegunes
egegunes previously approved these changes Oct 28, 2025
hors
hors previously approved these changes Oct 28, 2025
nmarukovich
nmarukovich previously approved these changes Oct 28, 2025
pooknull
pooknull previously approved these changes Oct 29, 2025
@gkech gkech dismissed stale reviews from pooknull, hors, egegunes, and nmarukovich via cdb5c8d October 30, 2025 10:36
@egegunes
Copy link
Contributor

@gkech please check unit tests

egegunes
egegunes previously approved these changes Oct 31, 2025
@gkech gkech requested a review from egegunes November 3, 2025 10:52
@JNKPercona
Copy link
Collaborator

Test Name Result Time
backup-enable-disable passed 00:10:34
custom-envs passed 00:17:23
custom-extensions passed 00:14:09
custom-tls passed 00:05:10
database-init-sql passed 00:02:20
demand-backup passed 00:23:19
finalizers passed 00:03:52
init-deploy passed 00:03:17
monitoring passed 00:08:26
monitoring-pmm3 passed 00:10:34
one-pod passed 00:06:21
operator-self-healing passed 00:08:35
pgvector-extension passed 00:03:17
pitr passed 00:12:31
scaling passed 00:05:11
scheduled-backup passed 00:27:14
self-healing passed 00:09:12
sidecars passed 00:02:41
start-from-backup passed 00:12:45
tablespaces passed 00:07:21
telemetry-transfer passed 00:03:32
upgrade-consistency passed 00:12:01
upgrade-minor passed 00:06:13
users passed 00:04:46
Summary Value
Tests Run 24/24
Job Duration 01:24:08
Total Test Time 03:40:53

commit: 898926b
image: perconalab/percona-postgresql-operator:PR-1334-898926bc1

@hors hors merged commit bd567da into main Nov 3, 2025
18 checks passed
@hors hors deleted the K8SPG-882 branch November 3, 2025 14:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants