HYPBLD-844: Add MCE product mapping for Konflux kubeconfig and CPE labels

[girish1430]

Summary

Adds mce product mappings for MCE 2.11 ART onboarding (HYPBLD-844), following the ACM changes in:

• art-tools #2923 — PRODUCT_KUBECONFIG_MAP / PRODUCT_NAMESPACE_MAP for acm
• art-tools #2910 — CPE_PRODUCT_NAME_MAPPING for acm

artcommon/artcommonlib/constants.py

Map	Entry
PRODUCT_NAMESPACE_MAP	"mce": "art-acm-tenant"
PRODUCT_KUBECONFIG_MAP	"mce": "ACM_KONFLUX_SA_KUBECONFIG"

MCE 2.11 Konflux builds run in crt-redhat-acm-tenant (same workspace/credential as ACM).

doozer/doozerlib/backend/rebaser.py

Map	Entry
CPE_PRODUCT_NAME_MAPPING	'mce': 'multicluster_engine'

Matches CPE labels used on MCE container images (e.g. cpe:/a:redhat:multicluster_engine:...).

Companion: ocp-build-data #10730 (product: mce on mce-2.11).

Test plan

• build-layered-products for mce-2.11 no longer raises ValueError: Kubeconfig required for Konflux builds
• Konflux builds use art-acm-tenant namespace for product mce
• Rebaser CPE labels on MCE images use multicluster_engine

Made with Cursor

[openshift-ci-robot]

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

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

Adds mce product mappings for MCE 2.11 ART onboarding (HYPBLD-844), following the ACM changes in:

• art-tools #2923 — PRODUCT_KUBECONFIG_MAP / PRODUCT_NAMESPACE_MAP for acm
• art-tools #2910 — CPE_PRODUCT_NAME_MAPPING for acm

artcommon/artcommonlib/constants.py

Map	Entry
PRODUCT_NAMESPACE_MAP	"mce": "art-acm-tenant"
PRODUCT_KUBECONFIG_MAP	"mce": "ACM_KONFLUX_SA_KUBECONFIG"

MCE 2.11 Konflux builds run in crt-redhat-acm-tenant (same workspace/credential as ACM).

doozer/doozerlib/backend/rebaser.py

Map	Entry
CPE_PRODUCT_NAME_MAPPING	'mce': 'multicluster_engine'

Matches CPE labels used on MCE container images (e.g. cpe:/a:redhat:multicluster_engine:...).

Companion: ocp-build-data #10730 (product: mce on mce-2.11).

Test plan

• build-layered-products for mce-2.11 no longer raises ValueError: Kubeconfig required for Konflux builds
• Konflux builds use art-acm-tenant namespace for product mce
• Rebaser CPE labels on MCE images use multicluster_engine

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.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: 7422f920-1b6f-4121-a301-4751e7f2784c

📥 Commits

Reviewing files that changed from the base of the PR and between 79b87e4 and cea75c6.

📒 Files selected for processing (2)

• artcommon/artcommonlib/constants.py
• doozer/doozerlib/backend/rebaser.py

---

Walkthrough

This PR adds MCE (multicluster engine) product support by registering it in three product configuration constant maps: the namespace map pointing to art-acm-tenant, the kubeconfig map pointing to ACM_KONFLUX_SA_KUBECONFIG, and the CPE product name map pointing to multicluster_engine.

Changes

MCE Product Registration

Layer / File(s)	Summary
Product mapping constants artcommon/artcommonlib/constants.py, doozer/doozerlib/backend/rebaser.py	MCE is registered in PRODUCT_NAMESPACE_MAP as art-acm-tenant, in PRODUCT_KUBECONFIG_MAP as ACM_KONFLUX_SA_KUBECONFIG, and in CPE_PRODUCT_NAME_MAPPING as multicluster_engine.

🎯 1 (Trivial) | ⏱️ ~3 minutes

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[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.

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ashwindasr

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:

• OWNERS [ashwindasr]

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

[ashwindasr]

/ok-to-test