Today, bits in stage are never tested.

Rather, automated tests exist for:

• CI (from quay resistry, using crwctl only) - on QE OCP 3.11 every time
• pre-pre-GA aka pre-stage (from brew/osbs registry) - on QE OCP 4.x every time
• post-GA (from prod reg.rh.io) - from time to time

But we don't test the staged bits that are actually in the Erratas, and while they're verbatim copies of the images in brew / osbs / quay, it would probably be wise to have at least a smoke test or two to validate the images before they're pushed from stage to production.

Ya know, just in case.

To faciliate this, since an existing ICSP is being used to point refs to reg.rh.io at quay.io to resolve images, we'd likely need a way to first stand up per-use clusters for this testing, then enable an ICSP to point refs to reg.rh.io at reg.stage.rh.io.

Once the smoke test is done, the per-use cluster could then be torn down. This would prevent it from colliding with the ICSP used for ongoing 2.y and 2.y+1 tests, which will rely on the quay ICSP.

The first step here is to add credentials to casc.yaml such that a bot user on main-jenkins can log into reg.stage to pull metadata. See also CRW-1557, where this will likely be done first.