Non-early readiness waiting broken for old versions (at least in mixed-version scenarios)

[porridge]

I didn't dig to the bottom of this, but it seems that when deploying a "4.12" central and and old securedcluster (which does not have the Available status condition in the CR), then with --early-readiness=false roxie will always timeout waiting for the nonexistent condition to appear on secured cluster.

Example:

05:59 Waiting for resource securedcluster/stackrox-secured-cluster-services to exist in namespace stackrox...
06:00   → Deployment 'central' created (1/1 replicas ready)
06:00   → Deployment 'central-db' created (1/1 replicas ready)
06:00   → Deployment 'config-controller' created (1/1 replicas ready)
06:00   → Deployment 'scanner' created (1/1 replicas ready)
06:00   → Deployment 'scanner-db' created (1/1 replicas ready)
06:00   → Deployment 'scanner-v4-db' created (1/1 replicas ready)
06:00   → Deployment 'scanner-v4-indexer' created (1/1 replicas ready)
06:00   → Deployment 'scanner-v4-matcher' created (1/1 replicas ready)
06:00     • Pod 'central-5b7bd98bbb-hjps8' running
06:00     • Pod 'central-db-5fbb54b79c-prttc' running
06:00     • Pod 'config-controller-6fdd78c7fb-68kr2' running
06:00     • Pod 'scanner-6745765776-rdztx' running
06:00     • Pod 'scanner-db-56459f7669-7tkmz' running
06:00     • Pod 'scanner-v4-db-7779d5964b-9x6jm' running
06:00     • Pod 'scanner-v4-indexer-6845676665-d44p4' running
06:00     • Pod 'scanner-v4-matcher-78cbd7cd56-877mw' running
06:06   → Deployment 'admission-control' created (/ replicas ready)
06:06   → Deployment 'sensor' created (/ replicas ready)
06:06     • Pod 'admission-control-d47cb4cc4-5lm79' starting...
06:06     • Pod 'admission-control-d47cb4cc4-fkdz7' starting...
06:06     • Pod 'admission-control-d47cb4cc4-m47fw' starting...
06:06     • Pod 'collector-kdg2s' starting...
06:06     • Pod 'collector-r898s' starting...
06:06     • Pod 'sensor-7cdd7cb69f-ts84m' starting...
06:07   ⋯ Deployment 'admission-control' progressing (/3 replicas ready)
06:07   ⋯ Deployment 'sensor' progressing (/1 replicas ready)
06:40     • Pod 'sensor-7cdd7cb69f-ts84m' running (not ready yet)
06:51   ⋯ Deployment 'sensor' progressing (1/1 replicas ready)
06:51     • Pod 'sensor-7cdd7cb69f-ts84m' is ready
06:53     • Pod 'admission-control-d47cb4cc4-fkdz7' running (not ready yet)
07:04     • Pod 'admission-control-d47cb4cc4-fkdz7' is ready
07:05   ⋯ Deployment 'admission-control' progressing (1/3 replicas ready)
07:06   ✓ Deployment 'sensor' is available (1/1 replicas)
07:06     • Pod 'collector-kdg2s' is ready
07:42     • Pod 'admission-control-d47cb4cc4-m47fw' running (not ready yet)
07:48   ⋯ Deployment 'admission-control' progressing (2/3 replicas ready)
07:48     • Pod 'admission-control-d47cb4cc4-m47fw' is ready
07:56     • Pod 'admission-control-d47cb4cc4-5lm79' running (not ready yet)
08:00     • Pod 'collector-r898s' is ready
08:02   ✓ Deployment 'admission-control' is available (3/3 replicas)
08:02     • Pod 'admission-control-d47cb4cc4-5lm79' is ready
09:03 Still waiting for component Secured Cluster in namespace stackrox
10:03 Still waiting for component Secured Cluster in namespace stackrox
11:03 Still waiting for component Secured Cluster in namespace stackrox
12:04 Still waiting for component Secured Cluster in namespace stackrox
13:05 Still waiting for component Secured Cluster in namespace stackrox
14:06 Still waiting for component Secured Cluster in namespace stackrox
15:07 Still waiting for component Secured Cluster in namespace stackrox
16:08 Still waiting for component Secured Cluster in namespace stackrox
17:09 Still waiting for component Secured Cluster in namespace stackrox
18:10 Still waiting for component Secured Cluster in namespace stackrox
19:10 Still waiting for component Secured Cluster in namespace stackrox
20:11 Still waiting for component Secured Cluster in namespace stackrox
INFO: Fri Aug 14 02:05:52 UTC 2026: Refreshing the GKE auth token
Fetching cluster endpoint and auth data.
kubeconfig entry generated for rox-ci-nongroovy-compat-test-20880586884.
21:11 Still waiting for component Secured Cluster in namespace stackrox
22:12 Still waiting for component Secured Cluster in namespace stackrox
23:12 Still waiting for component Secured Cluster in namespace stackrox
24:13 Still waiting for component Secured Cluster in namespace stackrox
25:13 Still waiting for component Secured Cluster in namespace stackrox
25:59 Transient error in kubectl command: error: timed out waiting for the condition on securedclusters/stackrox-secured-cluster-services
25:59 Retrying kubectl command (attempt 2/3) after 4s...
26:04 failed to check for deployment progress in namespace stackrox: retrieving deployment information: kubectl command failed: context deadline exceeded
26:04 failed to check for pod progress in namespace stackrox: retrieving pod information: kubectl command failed: context deadline exceeded
Error: deployment failed: failed to deploy secured cluster: failed waiting for SecuredCluster: timeout reached
****
**** 02:11:02: ERROR: test failed [Test failed: exit 1] [version compatibility tests: 4.12.x-729-g5102191426--4.9.10]

The same happens for central the other way in version compatibility tests: 4.9.10--4.12.x-729-g5102191426