K8SPG-512 update switchover section

[nmarukovich]

CHANGE DESCRIPTION

Problem: Short explanation of the problem. We updated postgrescluster object and it does not make any changes. It looks like correct way is to update pg object. In addition, commands do not make any changes: kubectl patch postgrescluster/cluster1 --type merge --patch '{"spec":{"paused": true}}' kubectl patch postgrescluster/cluster1 --type merge --patch '{"spec":{"shutdown": true}}' Should we fix it too? Or move the changes in another documentation? 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 the manifests (crd/bundle) regenerated if needed?
• [ ] 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
monitoring	passed
operator-self-healing	passed
scaling	passed
scheduled-backup	passed
self-healing	passed
start-from-backup	passed
tablespaces	passed
telemetry-transfer	passed
upgrade-minor	passed
users	passed
We run 13 out of 13

commit: https://github.com/percona/percona-postgresql-operator/pull/671/commits/d677868b4531d15bc008b02d0f0ea88efe23ab73 image: perconalab/percona-postgresql-operator:PR-671-d677868b4