K8SPSMDB-1014: add upgrade-consistency-sharded-tls test

[pooknull]

DESCRIPTION

Problem:
We don't have an upgrade-consistency test with installed cert-manager.

Solution:
Create an upgrade-consistency-sharded-tls test. In this test, we should renew certificates after every cr update.

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 the manifests (crd/bundle) regenerated if needed?
• 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?

[tplavcic]

The only thing which I'm thinking is do we need two tests or should we just keep upgrade-consistency-sharded-tls and remove upgrade-consistency-sharded?
@hors @egegunes

[hors]

The only thing which I'm thinking is do we need two tests or should we just keep upgrade-consistency-sharded-tls and remove upgrade-consistency-sharded? @hors @egegunes

I think we need to have only one

[nmarukovich]

@pooknull did you check why the test failed?