Following a suggested gap covered:
What is the goal * To test cluster resilience and OLMv1’s cleanup behavior when a webhook registered by an extension affects global resources.

• Ensure uninstalling or breaking the extension’s webhook doesn’t prevent normal Kubernetes operations for other workloads.

How to do the test ( Idea / Suggestion offered in the review api )

Set up an extension (operator) that installs a validating or mutating webhook.
The webhook should act on core Kubernetes resources (e.g., block or validate Deployments).
Then simulate a failure — uninstall the extension or make the webhook unavailable.
Verify that OLMv1 handles cleanup correctly, so that:

The goal would be: 

• No stale or broken webhook configurations remain.
• The cluster recovers gracefully — meaning users can still create resources like Deployments.
• The uninstall process never leaves the cluster blocked by a stale webhook.

where the test should be added : https://github.com/openshift/operator-framework-operator-controller/tree/main/openshift/tests-extension