K8SPG-683 support Authenticating Against a TLS-enabled LDAP Server

[gkech]

Jira: https://perconadev.atlassian.net/browse/K8SPG-683

CHANGE DESCRIPTION

Problem:

Adds support for configuring PostgreSQL LDAP authentication over TLS (ldaps) in PerconaPG clusters.

• Two new fields added to the PerconaPGCluster CR:
  • spec.config.files — mount arbitrary files (e.g. an LDAP CA certificate) into /etc/postgres
  • spec.authentication.rules — define custom pg_hba.conf rules, either structured or as raw HBA lines; rules are evaluated after mandatory operator rules and before the default scram-sha-256 fallback
• CRDs regenerated to reflect the new fields
• Two e2e tests added: one for plain LDAP and one for LDAP over TLS (ldap-tls suite)

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

[JNKPercona]

Test Name	Result	Time
backup-enable-disable	passed	00:00:00
builtin-extensions	passed	00:00:00
cert-manager-tls	passed	00:00:00
custom-envs	passed	00:00:00
custom-extensions	passed	00:00:00
custom-tls	passed	00:00:00
database-init-sql	passed	00:00:00
demand-backup	passed	00:00:00
demand-backup-offline-snapshot	passed	00:00:00
dynamic-configuration	passed	00:00:00
finalizers	passed	00:00:00
init-deploy	passed	00:00:00
huge-pages	passed	00:00:00
ldap	passed	00:00:00
ldap-tls	passed	00:00:00
monitoring	passed	00:00:00
monitoring-pmm3	passed	00:00:00
one-pod	passed	00:00:00
operator-self-healing	passed	00:00:00
pg-tde	passed	00:00:00
pitr	passed	00:00:00
scaling	passed	00:00:00
scheduled-backup	passed	00:00:00
self-healing	passed	00:09:59
sidecars	passed	00:00:00
standby-pgbackrest	passed	00:00:00
standby-streaming	passed	00:10:33
start-from-backup	passed	00:00:00
tablespaces	passed	00:00:00
telemetry-transfer	passed	00:00:00
upgrade-consistency	passed	00:00:00
upgrade-minor	passed	00:00:00
users	passed	00:00:00

Summary	Value
Tests Run	33/33
Job Duration	00:35:25
Total Test Time	00:20:32

commit: a74d00e
image: perconalab/percona-postgresql-operator:PR-1456-a74d00eb4

[egegunes]

this will lead to unnecessary retries but also exit 0 will make the test continue. i wonder how can we improve this kind of situations where need to skip tests on jenkins? @jvpasinatto any ideas?

[hors]

I think we do not have many choices. We need to use exit 0