The TestPerfEncryption is very flaky in openshift-kube-apiserver-operator because some time, the test fail to observe the migration time.

An example of that scenario happening can be found in https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-kube-apiserver-operator/1449/pull-ci-openshift-cluster-kube-apiserver-operator-master-e2e-gcp-operator-encryption-perf-single-node/1633492098231570432.

This is most likely due to the fact that when the test tries to get the operator status, it sometimes get connection refused errors that are interrupting the migration time checks:

    e_log.go:52: Mar  8 16:52:01.983: failed waiting for the condition "EncryptionMigrationControllerProgressing" with the reason "Migrating" to be set to true, err was Get "https://api.ci-op-k3t1sbb5-05f61.XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:6443/apis/operator.openshift.io/v1/kubeapiservers/cluster": dial tcp 34.68.154.63:6443: connect: connection refused

Note that this might be broken only in SNO jobs.