chore(KONFLUX-6210): fix and set name and cpe label for hive-mce-29

[ralphbean]

For https://issues.redhat.com/browse/KONFLUX-6210, clair needs access to a name and cpe label that it can use to look up the image in VEX statements.

See also release-engineering/rhtap-ec-policy#149

Signed-off-by: Ralph Bean rbean@redhat.com
Assisted-by: Gemini

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ralphbean
Once this PR has been reviewed and has the lgtm label, please assign 2uasimojo 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]

@ralphbean: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/security	2b66ccc	link	true	/test security

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.

[2uasimojo]

/assign @dlom

I don't love having MCE-specific things in our otherwise-generic Dockerfile. Is there some other way to get that injected?

You can override security when ready to merge, Mark. This is a new, unrelated failure tracked by HIVE-2937.

[dlom]

@ralphbean We use the same Dockerfile to build all MCE images for all version 2.6-2.10. Hardcoding an MCE 2.9 string in the Dockerfile isn't a viable solution IMO. I think we can pass in these labels as environment variables, and configure the version one level up (in the konflux pipeline definitions)

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale