TestCatalogImageUpdate e2e test does not work locally on kind clusters

[exdx]

Bug Report

What did you do?
A clear and concise description of the steps you took (or insert a code snippet).
The TestCatalogImageUpdate test does not work on KIND clusters locally (it does work on minikube however). This seems due to the port-forwarding that is required to talk to the local docker registry that is deployed during the course of this test.

Test Here

Fixing this quickly would require a check to see if we are in a kind cluster and then a t.Skip() if so. Fixing this properly would require some thought and more diagnosis.

What did you expect to see?
A clear and concise description of what you expected to happen (or insert a code snippet).
Test passes on KIND clusters

What did you see instead? Under which circumstances?
A clear and concise description of what you expected to happen (or insert a code snippet).
Test fails on KIND clusters

Environment

• operator-lifecycle-manager version:

• Kubernetes version information:

• Kubernetes cluster kind:

Possible Solution

Additional context
Add any other context about the problem here.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ecordell]

The test is still skipped - not sure we should close this until it can be enabled

[timflannagan]

I did a quick github/local search and wasn't immediately able to find the test name in question - it looks like it was renamed to It("delete gRPC registry pod triggers recreation") in 06e84d9 if I'm following everything correctly. Am I missing anything, or is this a problem on another already released, yet still supported branch?

[exdx]

Closing as a duplicate of #2420