K8SPG-836: Release 2.8.0

[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	Result	Time
backup-enable-disable	passed	00:09:56
custom-envs	passed	00:19:25
custom-extensions	passed	00:14:18
custom-tls	passed	00:05:02
database-init-sql	passed	00:02:56
demand-backup	passed	00:26:11
finalizers	passed	00:03:38
init-deploy	passed	00:02:42
monitoring	passed	00:07:27
monitoring-pmm3	passed	00:09:06
one-pod	passed	00:05:58
operator-self-healing	passed	00:08:29
pgvector-extension	passed	00:02:40
pitr	passed	00:11:56
scaling	passed	00:04:49
scheduled-backup	passed	00:29:54
self-healing	passed	00:09:20
sidecars	passed	00:02:29
start-from-backup	passed	00:11:50
tablespaces	passed	00:06:48
telemetry-transfer	passed	00:03:28
upgrade-consistency	passed	00:07:53
upgrade-minor	passed	00:05:27
users	passed	00:04:49

Summary	Value
Tests Run	24/24
Job Duration	01:31:42
Total Test Time	03:36:42

commit: f36b46f
image: perconalab/percona-postgresql-operator:PR-1354-f36b46f15