Release 2.5.1

[eleo007]

CHANGE DESCRIPTION

Problem:
Short explanation of the problem.

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?

[JNKPercona]

Test name	Status
custom-extensions	skipped
custom-tls	skipped
demand-backup	skipped
finalizers	skipped
init-deploy	skipped
major-upgrade	skipped
monitoring	skipped
one-pod	skipped
operator-self-healing	skipped
pitr	skipped
scaling	skipped
scheduled-backup	skipped
self-healing	skipped
start-from-backup	skipped
tablespaces	skipped
telemetry-transfer	skipped
upgrade-consistency	skipped
upgrade-minor	skipped
users	skipped
We run 0 out of 19

commit: ebd8950
image: perconalab/percona-postgresql-operator:PR-1063-ebd8950e6