Skip to content

HYPBLD-844: Add MCE 2.11 images for 24 stolostron components#10730

Open
girish1430 wants to merge 7 commits into
openshift-eng:mce-2.11from
girish1430:HYPBLD-844-mce-images
Open

HYPBLD-844: Add MCE 2.11 images for 24 stolostron components#10730
girish1430 wants to merge 7 commits into
openshift-eng:mce-2.11from
girish1430:HYPBLD-844-mce-images

Conversation

@girish1430
Copy link
Copy Markdown

@girish1430 girish1430 commented May 20, 2026

Summary

Adds images/*.yml for the 24 in-scope stolostron components on HYPBLD-844, building on the merged mce-2.11 skeleton (#10627).

  • 24 image configs aligned to the Jira stolostron checklist (backplane-2.11, existing Konflux/RHTAP Dockerfiles — not Dockerfile.art)
  • OCM monorepo components (addon-manager, placement, registration, registration-operator, work) use stolostron/ocm with build/Dockerfile.*.rhtap
  • group.yml aligned with ACM onboarding pattern (hermetic konflux, simplified cachi2)
  • streams.yml: rhel-9-nodejs-20 for console-mce
  • DECISIONS.md: component → repo → Dockerfile reference

Test plan

girish1430 and others added 6 commits May 20, 2026 12:48
Add 17 component image configs following ACM PR openshift-eng#10635 pattern:
- openshift-priv/stolostron-* git URLs, backplane-2.11 branch target
- multicluster-engine/*-rhel9 delivery names, mce-*-container distgit
- Per-repo Dockerfile paths from Konflux/RHTAP files (not Dockerfile.art)

Update group.yml to match ACM branch style (branch key, simplified konflux).
Add DECISIONS.md documenting naming and deferred components.

Jira: HYPBLD-844
Signed-off-by: ggn <ggn@redhat.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
- Add images/*.yml for console-mce, discovery-operator, multicloud-manager,
  cluster-api-provider-agent, cluster-api-provider-kubevirt, hypershift-operator
- Fix addon-manager to use stolostron/ocm (build/Dockerfile.addon.rhtap)
- Add rhel-9-nodejs-20 stream for console-mce
- Update DECISIONS.md with correct repo/branch mapping per Jira and sheet

Jira: HYPBLD-844
Signed-off-by: ggn <ggn@redhat.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
placement, work, registration, and registration-operator now use
stolostron/ocm on backplane-2.11 with the matching build/Dockerfile.*.rhtap
paths from ocm/build. cluster-proxy-addon uses backplane-2.10 until 2.11 exists.

Co-authored-by: Cursor <cursoragent@cursor.com>
Do not pin to backplane-2.10; MCE 2.11 target branch is backplane-2.11.

Co-authored-by: Cursor <cursoragent@cursor.com>
Jira stolostron checklist has cluster-proxy only, not cluster-proxy-addon.

Co-authored-by: Cursor <cursoragent@cursor.com>
Scope matches HYPBLD-844: add aws/azure/webhook-config/aso images,
remove openshift hypershift/capi-agent/capi-kubevirt, fix kube-rbac-proxy
to Containerfile.operator, document full component→repo→dockerfile map.

Co-authored-by: Cursor <cursoragent@cursor.com>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 20, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 20, 2026

@girish1430: This pull request references HYPBLD-844 which is a valid jira issue.

Details

In response to this:

Summary

Adds images/*.yml for the 24 in-scope stolostron components on HYPBLD-844, building on the merged mce-2.11 skeleton (#10627).

  • 24 image configs aligned to the Jira stolostron checklist (backplane-2.11, existing Konflux/RHTAP Dockerfiles — not Dockerfile.art)
  • OCM monorepo components (addon-manager, placement, registration, registration-operator, work) use stolostron/ocm with build/Dockerfile.*.rhtap
  • group.yml aligned with ACM onboarding pattern (hermetic konflux, simplified cachi2)
  • streams.yml: rhel-9-nodejs-20 for console-mce
  • DECISIONS.md: component → repo → Dockerfile reference

Out of scope (follow-up)

  • Jira External (AI tenant) and External (OCP) sections (~17 components)
  • art-tools mce product mapping (namespace / CPE — see ACM art-tools Pin microshift build for openshift-4.13 rc.8 #2923)
  • Pyxis verification of multicluster-engine/*-rhel9 delivery names
  • Operator bundle image

Test plan

Made with Cursor

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 20, 2026

[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 fgallott 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:

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

@openshift-ci openshift-ci Bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label May 20, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 20, 2026

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.

Regular contributors should join the org to skip this step.

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.

Comment thread group.yml Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants