K8SPG-597 - Update monitoring test

[tplavcic]

CHANGE DESCRIPTION

Problem: In one position in the test we were checking for Pod status conditions (array) and Kubernetes 1.29 adds a new status PodReadyToStartContainers. Unfortunately kuttl cannot compare arrays of different sizes so the test fails on 1.29. On the other hand I don't think checking for these status conditions in this place tests anything since any pod running will have all these conditions True.

Solution: I have removed checking for status conditions and just left checking for Running phase and also added checking for sts statuses.

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?
• [ ] 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	passed
demand-backup	passed
init-deploy	passed
major-upgrade	passed
monitoring	passed
one-pod	passed
operator-self-healing	passed
pitr	passed
scaling	passed
scheduled-backup	passed
self-healing	passed
start-from-backup	passed
tablespaces	passed
telemetry-transfer	passed
upgrade-consistency	passed
upgrade-minor	passed
users	passed
We run 17 out of 17

commit: https://github.com/percona/percona-postgresql-operator/pull/824/commits/3d236e374c6102fdcc2b9bbdaf2df294cfed839e image: perconalab/percona-postgresql-operator:PR-824-3d236e374