In an effort to ensure all HA components are not degraded by design during normal e2e test or upgrades, we are collecting all operators that are blipping Degraded=True during any payload job run. 


This card captures kube-apiserver operator that blips Degraded=True during upgrade runs. 

Example Jobs: 

https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-azure-ovn-upgrade/1843275894844559360

https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-rt-upgrade/1843561647470284800

    
Reasons associated with the blip: NodeController_MasterNodesReady or NodeController_MasterNodesReady::StaticPods_Error

For now, we put an exception in the test. But it is expected that teams take action to fix those and remove the exceptions after the fix go in. 

Exceptions are defined here: https://github.com/openshift/origin/blob/e5e76d7ca739b5699639dd4c500f6c076c697da6/pkg/monitortests/clusterversionoperator/legacycvomonitortests/operators.go#L375

See linked issue for more explanation on the effort.

    1.
    2.
    3.