https://perconadev.atlassian.net/browse/K8SPS-430

CHANGE DESCRIPTION

Problem:
cert-manager certificates are not refreshed when .spec.tls.SANs is updated.

Cause:
The operator currently verifies whether the TLS secret's ownerReferences points to the PerconaServerMySQL. If it does not, the operator skips updating the certificate. This logic is intended to prevent updating TLS secrets created by the user.

Solution:
Improve the logic for detecting user certificates. First, operator should check if the TLS secret was created by cert-manager. If so, verify that the ownerReferences of the issuer point to the PerconaServerMySQL. If both conditions are met, proceed with updating the certificates.

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?