https://grafana-loki.ci.openshift.org/d/ISnBj4LVk/disruption?orgId=1&var-platform=vsphere&var-percentile=P75&var-backend=image-registry-new-connections&var-backend=image-registry-reused-connections&var-releases=4.15&var-upgrade_type=none&var-networks=ovn&var-networks=sdn&var-topologies=ha&var-architectures=amd64&var-min_job_runs=10&var-lookback=1&var-min_disruption_regression=5&var-min_disruption_job_list=5&var-master_nodes_updated=N&var-master_nodes_updated=&var-master_nodes_updated=Y&from=now-30d&to=now

For some reason the registry reports a disproportionate amount of disruption problems on vsphere ovn, NON upgrade, just normal e2e runs, which is rather strange. Have seen some things in these job runs indicating lack of replicas for the registry.

Problem doesn't really appear until you view P75 and above.

Dig into what's going on in these job runs and see if we can get someone a bug, but bear in mind registry does not have a lot of development power to investigate.

Also consider removing this from our alerts, this has tripped the P95 a few times.