Enable parallel OpenShift E2E test execution

[nammn]

Summary

OpenShift E2E tests were forced to run sequentially (max_hosts: 1) because multiple operator instances on the same cluster would conflict on the ValidatingWebhookConfiguration, a cluster-scoped resource with a hardcoded name mdbpolicy.mongodb.com.

---

Changes to Enable Parallel Execution

1. Configurable Webhook Name

Why: The ValidatingWebhookConfiguration is cluster-scoped. Multiple operators would overwrite each other.

What: Made webhook name configurable via MDB_WEBHOOK_NAME env var and operator.webhook.name helm value. OpenShift context files set namespace-unique names (e.g., mdbpolicy.${NAMESPACE}.mongodb.com).

2. Controlled Parallelism with Retries

Why: Unlimited parallelism caused pod scheduling failures due to cluster resource contention.

What: Set max_hosts: 2 per variant. Added retry mechanism via <<: *teardown_group and removed OpenShift from retry exclusion list.

---

Proof of Work

https://spruce.mongodb.com/version/6977bceda7da920007894d34/tasks?sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC -> were running in parallel

Checklist

• Have you linked a jira ticket and/or is the ticket in the title?
• Have you checked whether your jira ticket required DOCSP changes?
• Have you added changelog file?
  • use skip-changelog label if not needed

[github-actions]

⚠️ (this preview might not be accurate if the PR is not rebased on current master branch)

MCK 1.7.0 Release Notes

New Features

• Allows users to override any Ops Manager emptyDir mount with their own PVCs via overrides statefulSet.spec.volumeClaimTemplates.
• Added support for auto embeddings in MongoDB Community to automatically generate vector embeddings for the vector search data. This document can be followed for detailed documentation
• MongoDBSearch: Updated the default mongodb/mongodb-search image version to 0.60.1. This is the version MCK uses if .spec.version is not specified.
• Added support for configurable ValidatingWebhookConfiguration name via operator.webhook.name helm value.

Bug Fixes

• Fix an issue to ensure that hosts are consistently removed from Ops Manager monitoring during AppDB scale-down events.
• Fixed an issue where monitoring agents would fail after disabling TLS on a MongoDB deployment.
• Persistent Volume Claim resize fix: Fixed an issue where the Operator ignored namespaces when listing PVCs, causing conflicts with resizing PVCs of the same name. Now, PVCs are filtered by both name and namespace for accurate resizing.
• Fixed a panic that occurred when the domain names for a horizon was empty. Now, if the domain names are not valid (RFC 1123), the validation will fail before reconciling.
• MongoDBMultiCluster, MongoDB: Fix an issue where the operator skipped host removal when an external domain was used, leaving monitoring hosts in Ops Manager even after workloads were correctly removed from the cluster.
• Fixed an issue where the Operator could crash when TLS certificates are configured using the certificatesSecretsPrefix field without additional TLS settings.
• MongoDBOpsManager, AppDB: Block removing a member cluster while it still has non-zero members. This prevents scaling down without the preserved configuration and avoids unexpected issues.

[nammn]

this enables concurrent re-runs as well as independent retries

[nammn]

but, we can't set a higher number as we are still limited by openshift