I'll spend some time to go through this more carefully once the 0.12.1 release is out. Like you've mentioned, I think the tests in the operator module need some adjustments.

I looked into the test failures and there are a few things that need to be adjusted to correct. The suggestions about adding readyPostcondition to the ingress and route is one part, and the other part is in the tests themselves.

Since the presence of the Route API will trigger the new logic, we need to make sure it is only present in the Kube server for the (single) test that needs it. In the ConsoleReconcilerTestBase class setUp method, add a JUnit TestInfo testInfo argument that you can use to conditionally create the Route CRD based on a tag. Something like:

if (testInfo.getTags().contains("requires:routes.route.openshift.io")) {
    // create the route CRD
} else {
    // delete any route instances and the CRD
    try {
        delete(client.resources(Route.class).inAnyNamespace());
        client.resources(CustomResourceDefinition.class).withName("routes.route.openshift.io").delete();
    } catch (KubernetesClientException e) {
        // Ignore
    }
}

Then you can tag the one test that needs a Route like this:

@Test
@Tag("requires:routes.route.openshift.io")
void testConsoleReconciliationWithOpenShiftMonitoring() {
    // the test
}

Future tests you add to check the new Route logic can use the same tag.