Value Statement

Whenever a new CAPI image is released to registry.redhat.io, testing images break due to needing the `mch-imageRepository` annotation, which causes all repository references to look at quay.io for the images. However, there is no automated mirroring in place for this image, so this breaks all QE builds until the image is manually mirrored. To avoid this, we should pin the image to prevent breakages.

Slack thread with example issue: https://redhat-internal.slack.com/archives/CUBFVGV9A/p1752160770659279?thread_ts=1752146787.235129&cid=CUBFVGV9A

Definition of Done for Engineering Story Owner (Checklist)

in https://github.com/stolostron/mce-operator-bundle/blob/backplane-2.9/config/mce-manifest-gen-config.json,

"image-ref": "registry.redhat.io/openshift4/ose-cluster-api-rhel9:v4.19"

should change to

"image-ref": "registry.redhat.io/openshift4/ose-cluster-api-rhel9@sha256:9a72b8081a57846d942981ced07da86ad8e197309a1bc3c9d53876528b58f8ec
"

for all three, we need

registry.redhat.io/openshift4/ose-cluster-api-rhel9@sha256:9a72b8081a57846d942981ced07da86ad8e197309a1bc3c9d53876528b58f8ec

registry.redhat.io/openshift4/ose-aws-cluster-api-controllers-rhel9@sha256:cf13b0658271cd0dbd1ce6dcc350e64c5459ef02ba4dc88a0031de9d6f26ffd1

registry.redhat.io/openshift4/ose-baremetal-cluster-api-controllers-rhel9@sha256:f855d5ce17d3ac4560afc73c35d03f045f84551fdccc00312c890288a889b9ce

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.

-------------------------------------------------------------------------------------------------------
QE Hand Off Template (fill out when moving to Review) 7/14/25:

Summary of the Work:
What was implemented or fixed? Include a brief description of the problem (if applicable) and how it was addressed.
e.g., "Updated the UI to show validation errors for the form. The previous implementation did not surface backend validation issues."

Key Areas to Verify:

1. What functionality should QE focus on? List what was tested or what is most important to validate.
2. Ensure the new validation messages appear for required fields
3. Confirm the workflow still completes as expected after validation fixes
4. Any edge cases or high-risk areas touched by the change

Fix or Feature Availability:
When will this be available in a build?
Code merged on: YYYY-MM-DD
Expected downstream build tag (if known): example-build-tag
(Optional) Related PR(s): Link