dhellman@redhat.com  shared one idea[1] to create some "smoke" tests to avoid a lot of troubleshooting like we needed to find the NFS error (SPLAT-798). Those tests could be added to this "pre-flight" plugin, keeping the message more obvious like "Unable to create an image on the internal image registry". "Unable to pull the custom image from internal registry".

Can you create an image? Can you create a pod from that image? Can you create a volume? Can you mount that volume to a pod? Etc 

Initially we wouldn't want to re-create existing jobs, if we can reuse it would be nice, if not we can create it with the focus on the usability (use the registry), not in the feature (NFS storage for the image-registry). The main idea is to avoid a lot of overhead troubleshooting on Partner execution and support teams. Also we will share a more clear error before running all the conformance tests.

On this spike we can talk with TRT Team to understand their approach when troubleshooting the tests running on CI.

[1] https://coreos.slack.com/archives/C02DSMAP4LA/p1664982317171009