K8SPSMDB-1635 configure through cr the auth mechanism for PMM

[gkech]

CHANGE DESCRIPTION

Problem:

The Percona operator v1.22.0 hardcodes --authentication-mechanism=SCRAM-SHA-1 when it launches the PMM exporter sidecar. The operator should allow configuring this option through a new cr configuration. For example:

  pmm:
    enabled: false
    image: perconalab/pmm-client:3-dev-latest
    serverHost: monitoring-service
    authenticationMechanism: SCRAM-SHA-256

Helm Chart PR: percona/percona-helm-charts#856

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?
• Are OpenShift compare files changed for E2E tests (compare/*-oc.yml)?

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

[gkech]

discuss if we want to continue using SCRAM-SHA-1 auth mechanism as the default one.

[egegunes]

should we consider making 256 the default?

[gkech]

have the same question: #2342 (comment)

[egegunes]

maybe we can ask PMM team to see if there are any possible side effects

[JNKPercona]

Test Name	Result	Time
arbiter	passed	00:11:12
balancer	passed	00:18:16
cross-site-sharded	passed	00:19:09
custom-replset-name	passed	00:10:24
custom-tls	passed	00:14:03
custom-users-roles	passed	00:10:14
custom-users-roles-sharded	passed	00:11:30
data-at-rest-encryption	passed	00:13:11
data-sharded	failure	00:58:26
demand-backup	passed	00:16:50
demand-backup-eks-credentials-irsa	passed	00:00:07
demand-backup-fs	passed	00:23:10
demand-backup-if-unhealthy	passed	00:08:40
demand-backup-incremental-aws	passed	00:11:45
demand-backup-incremental-azure	passed	00:12:10
demand-backup-incremental-gcp-native	passed	00:11:45
demand-backup-incremental-gcp-s3	passed	00:10:44
demand-backup-incremental-minio	passed	00:28:29
demand-backup-incremental-sharded-aws	passed	00:19:29
demand-backup-incremental-sharded-azure	passed	00:18:25
demand-backup-incremental-sharded-gcp-native	passed	00:18:37
demand-backup-incremental-sharded-gcp-s3	passed	00:17:59
demand-backup-incremental-sharded-minio	passed	00:28:29
demand-backup-logical-minio-native-tls	passed	00:09:05
demand-backup-physical-parallel	passed	00:08:14
demand-backup-physical-aws	passed	00:12:33
demand-backup-physical-azure	passed	00:12:45
demand-backup-physical-gcp-s3	passed	00:13:04
demand-backup-physical-gcp-native	passed	00:13:07
demand-backup-physical-minio	passed	00:24:36
demand-backup-physical-minio-native	passed	00:28:14
demand-backup-physical-minio-native-tls	passed	00:20:31
demand-backup-physical-sharded-parallel	passed	00:12:43
demand-backup-physical-sharded-aws	passed	00:20:31
demand-backup-physical-sharded-azure	passed	00:20:54
demand-backup-physical-sharded-gcp-native	passed	00:19:12
demand-backup-physical-sharded-minio	passed	00:20:44
demand-backup-physical-sharded-minio-native	passed	00:18:26
demand-backup-sharded	passed	00:26:41
demand-backup-snapshot	passed	00:39:05
demand-backup-snapshot-vault	passed	00:18:26
disabled-auth	passed	00:17:20
expose-sharded	passed	00:34:26
finalizer	passed	00:10:21
ignore-labels-annotations	passed	00:07:57
init-deploy	passed	00:13:22
ldap	passed	00:08:36
ldap-tls	passed	00:12:39
limits	passed	00:06:22
liveness	passed	00:08:50
mongod-major-upgrade	passed	00:13:26
mongod-major-upgrade-sharded	passed	00:21:17
monitoring-2-0	passed	00:25:14
monitoring-pmm3	passed	00:25:47
multi-cluster-service	passed	00:12:49
multi-storage	passed	00:18:39
non-voting-and-hidden	passed	00:16:54
one-pod	passed	00:07:37
operator-self-healing-chaos	passed	00:13:58
pitr	passed	00:32:43
pitr-physical	passed	01:02:50
pitr-sharded	passed	00:21:10
pitr-to-new-cluster	passed	00:24:58
pitr-physical-backup-source	passed	00:54:26
preinit-updates	passed	00:05:03
pvc-auto-resize	passed	00:14:51
pvc-resize	passed	00:16:24
recover-no-primary	passed	00:27:21
replset-overrides	passed	00:17:26
replset-remapping	passed	00:17:27
replset-remapping-sharded	passed	00:17:53
rs-shard-migration	passed	00:14:46
scaling	passed	00:11:10
scheduled-backup	passed	00:18:17
security-context	passed	00:07:07
self-healing-chaos	passed	00:14:54
service-per-pod	passed	00:19:06
serviceless-external-nodes	passed	00:07:08
smart-update	passed	00:08:18
split-horizon	passed	00:14:14
stable-resource-version	passed	00:04:32
storage	passed	00:07:16
tls-issue-cert-manager	passed	00:31:38
unsafe-psa	passed	00:07:50
upgrade	passed	00:09:34
upgrade-consistency	passed	00:06:32
upgrade-consistency-sharded-tls	passed	00:53:11
upgrade-sharded	passed	00:19:50
upgrade-partial-backup	passed	00:16:24
users	passed	00:17:46
users-vault	passed	00:13:20
version-service	passed	00:25:19

Summary	Value
Tests Run	92/92
Job Duration	03:06:17
Total Test Time	27:28:59

commit: 8887205
image: perconalab/percona-server-mongodb-operator:PR-2342-888720581