Add stackrox stable/latest tag mirrors

[davdhacs]

Summary

• Add mirror entries for scanner-test-stable, stackrox-test-stable, and stackrox-ui-test-stable images (and "-latest" for each for staged testing)
  The latest tagged images will be pushed by rox-ci-image on every release.
  The stable tagged images will be pushed on-demand by a stackrox engineer after verifying the latest images

This change removes the need to request testplatform review for each version bump

Related to stackrox/rox-ci-image#248 which adds the stable and latest image pushes

🤖 Generated with Claude Code

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@davdhacs: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[davdhacs]

/cc @porridge @tommartensen @mclasmeier @janisz

[davdhacs]

/unhold

[tommartensen]

/lgtm

QQ though: Do you know how long it takes until a newer image is mirrored into the build infrastructure? Can we infer the actual rox-ci-image version from the Prow output?

[davdhacs]

/assign @bear-redhat

[davdhacs]

/lgtm

QQ though: Do you know how long it takes until a newer image is mirrored into the build infrastructure? Can we infer the actual rox-ci-image version from the Prow output?

In my experience with the automation-flavors, the mirroring takes 1-3 hours. I think that it must be running on a periodic job and so the time-to-mirrored depends on when that sync happens (and if we have pushed right before it, we get the fastest mirroring).

Can we infer the actual rox-ci-image version from the Prow output?

prow does not log the image sha.

I've PR'd adding a printing of the image sha into the begin step: #77727

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: davdhacs, deepsm007, porridge, tommartensen

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• core-services/image-mirroring/OWNERS [deepsm007]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@davdhacs: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.