Introduce base-rhel9 image and replace ubi-minimal references [mce-2.11]

[girish1430]

Summary

Add a managed base-rhel9 image (layered on ubi-minimal) so MCE images receive timely RPM updates without waiting for RHEL releases. Replace all runtime stream: rhel9 references with member: base-rhel9 across 31 component configs.

Same pattern as Brian's ACM 2.16 PR #11642 and the MTA 8.1 PR #11595.

Changes

• New: images/base-rhel9.yml — managed base image layered on ubi-minimal
• Modified: 31 image configs — runtime stream: rhel9 → member: base-rhel9
• Modified: group.yml — added ocp-build-data public_upstreams entry (required for base-rhel9 source)
• Unchanged: console-mce.yml (uses rhel-9-nodejs-24 as runtime base, not rhel9)

Ref: HYPBLD-854

Made with Cursor

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign locriandev for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[openshift-ci]

Hi @girish1430. Thanks for your PR.

I'm waiting for a openshift-eng member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.