CMP-4572: Switch runtime base image to ubi9-minimal-pqc for PQC support

[guzalv]

What

Switch the Dockerfile.openshift runtime base image from registry.redhat.io/rhel9-4-els/rhel-minimal to registry.redhat.io/ubi9/ubi-minimal-pqc to enable Post-Quantum Cryptography (PQC) support via the DEFAULT:PQ crypto policy in OpenSSL.

Also fix the runtime package install: libbpf-devel -> libbpf. The runtime only needs the shared library (.so), not development headers.

This is the konflux (dev) branch counterpart of #249 (which targets release-0.10).

Why

Required by OCPSTRAT-3113. See epic CMP-4570.

Changes

Line	Before	After
Runtime FROM	registry.redhat.io/rhel9-4-els/rhel-minimal:latest	registry.redhat.io/ubi9/ubi-minimal-pqc:latest
Runtime packages	tar libseccomp libbpf-devel	tar libseccomp libbpf

Fixes: CMP-4572

[openshift-ci-robot]

@guzalv: This pull request references CMP-4572 which is a valid jira issue.

Details

In response to this:

What

Switch the Dockerfile.openshift runtime base image from registry.redhat.io/rhel9-4-els/rhel-minimal to registry.redhat.io/ubi9/ubi-minimal-pqc to enable Post-Quantum Cryptography (PQC) support via the DEFAULT:PQ crypto policy in OpenSSL.

Also fix the runtime package install: libbpf-devel -> libbpf. The runtime only needs the shared library (.so), not development headers.

This is the konflux (dev) branch counterpart of #249 (which targets release-0.10).

Why

Required by OCPSTRAT-3113. See epic CMP-4570.

Changes

Line	Before	After
Runtime FROM	registry.redhat.io/rhel9-4-els/rhel-minimal:latest	registry.redhat.io/ubi9/ubi-minimal-pqc:latest
Runtime packages	tar libseccomp libbpf-devel	tar libseccomp libbpf

Fixes: CMP-4572

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: guzalv
Once this PR has been reviewed and has the lgtm label, please assign rhmdnd 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 @guzalv. Thanks for your PR.

I'm waiting for a openshift 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.

[yuumasato]

/ok-to-test

[openshift-ci]

@guzalv: 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/e2e-flaky	fcd1e8b	link	false	/test e2e-flaky

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.