K8SPG-511 fix variables

[nmarukovich]

CHANGE DESCRIPTION

Problem:
In openshift we can't run pg cluster properly because of default fields.
Cause:
There is a bug in OpenShift where it ignores our alm-examples and automatically adds all fields with default values to the CR example.

As a result, extra sections like dataSource appear in the CR. If a user tries to create a cluster with this unintended dataSource section, the cluster gets stuck in the init state, attempting to restore from a backup that likely doesn't exist (since it's usually the first time the cluster is being deployed).
Solution:
Delete default values or turn some values from true to false.

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	passed
custom-tls	passed
demand-backup	passed
finalizers	passed
init-deploy	passed
monitoring	passed
one-pod	passed
operator-self-healing	passed
pitr	passed
scaling	passed
scheduled-backup	passed
self-healing	passed
sidecars	passed
start-from-backup	passed
tablespaces	passed
telemetry-transfer	passed
upgrade-consistency	passed
upgrade-minor	passed
users	passed
We run 19 out of 19

commit: 6d1234a
image: perconalab/percona-postgresql-operator:PR-1054-6d1234ac3