[sig-instrumentation] Prometheus [apigroup:image.openshift.io] when installed on the cluster should provide ingress metrics [Skipped:Disconnected] [Suite:openshift/conformance/parallel]

Happened in one payload https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/aggregated-aws-sdn-upgrade-4.13-micro-release-openshift-release-analysis-aggregator/1594450635296608256

I don't think it's a regression given the changelog, however the test does seem to have an issue that pops up about 2% of the time.

https://sippy.dptools.openshift.org/sippy-ng/tests/4.13/analysis?test=%5Bsig-instrumentation%5D%20Prometheus%20%5Bapigroup:image.openshift.io%5D%20when%20installed%20on%20the%20cluster%20should%20provide%20ingress%20metrics%20%5BSkipped:Disconnected%5D%20%5BSuite:openshift/conformance/parallel%5D

The common error message is:

{ fail [github.com/openshift/origin/test/extended/prometheus/prometheus.go:718]: Unexpected error:
<*json.SyntaxError | 0xc0015a4000>:

unexpected end of JSON input
occurred
Ginkgo exit error 1: exit with code 1}

Test seems to spit out a LOT of output.

See if we can determine why this is happening and if it can be addressed.