Description of problem:

During Upgrade: The operator MUST report Progressing=True (since a version change is a configuration change). It is defined in the o/api docs.

However, CO/kube-scheduler did not in these upgrade jobs: example1.

: [Monitor:legacy-cvo-invariants][bz-kube-scheduler] clusteroperator/kube-scheduler must go Progressing=True during an upgrade test expand_less31m40s{  clusteroperator/kube-scheduler was never Progressing=True during the upgrade window from 2025-11-24T14:34:38Z to 2025-11-24T15:06:18Z and CVO waited for it over 2 minutes from 2025-11-24T14:35:31Z to 2025-11-24T14:39:01Z} 

Version-Release number of selected component (if applicable):

The job upgrades a cluster to 4.21.0-0.nightly-2025-11-24-132032 (from 4.21.0-0.nightly-2025-11-22-193140).{code}
How reproducible:

failed 3/10 in the aggregate job: aggregated-aws-ovn-single-node-upgrade-4.21-micro-release-openshift-release-analysis-aggregator.