K8SPS-393 PMM3 support

[gkech]

CHANGE DESCRIPTION

Problem:
With this PR we introduce the PMM3 support for the ps operator. We completely stop supporting PMM2, so the included changes remove completely PMM2 related configurations and references.

An example of using PMM server v3 and PMM client v3.

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 PS version?
• Does the change support oldest and newest supported Kubernetes version?

[gkech]

@gkech check why this env var is not references in the PMM documentation

[gkech]

ticket created

[JNKPercona]

Test name	Status
version-service	failure
async-ignore-annotations	passed
auto-config	passed
config	passed
config-router	passed
demand-backup	passed
gr-demand-backup	passed
gr-demand-backup-haproxy	passed
gr-finalizer	passed
gr-haproxy	passed
gr-ignore-annotations	passed
gr-init-deploy	passed
gr-one-pod	passed
gr-recreate	passed
gr-scaling	passed
gr-scheduled-backup	passed
gr-security-context	passed
gr-self-healing	passed
gr-tls-cert-manager	passed
gr-users	passed
haproxy	passed
init-deploy	passed
limits	passed
monitoring	passed
one-pod	passed
operator-self-healing	passed
recreate	passed
scaling	passed
scheduled-backup	passed
service-per-pod	passed
sidecars	passed
smart-update	passed
tls-cert-manager	passed
users	passed
We run 34 out of 34

commit: 6978c3b
image: perconalab/percona-server-mysql-operator:PR-849-6978c3b9

[BupycHuk]

Hi, since it's default value even without env variable, what's the reason to override it?

[BupycHuk]

this change will drop pmm2 support by the operator

[gkech]

correct, we are not going to support PMM2 on the PS operator. We will keep support both for PMM2 and PMM3 for all the other operators i.e. pxc, psmdb and pgo

[gkech]

cc @hors

[hors]

@BupycHuk PS operator will be GA only in the end of Q3, so we decided to release GA only with PMM3 support