Skip to content

NE-2760: Update base image references to 5.0 for DEFAULT:PQ crypto-policy#191

Closed
davidesalerno wants to merge 1 commit into
openshift:release-5.0from
davidesalerno:NE-2760-update-base-image-5.0
Closed

NE-2760: Update base image references to 5.0 for DEFAULT:PQ crypto-policy#191
davidesalerno wants to merge 1 commit into
openshift:release-5.0from
davidesalerno:NE-2760-update-base-image-5.0

Conversation

@davidesalerno

Copy link
Copy Markdown

Summary

  • Update Dockerfile.ocp builder image from rhel-9-golang-1.25-openshift-4.22 to rhel-9-golang-1.26-openshift-5.0
  • Update Dockerfile.ocp base image from ocp/4.22:base-rhel9 to ocp/5.0:base-rhel9
  • Update .ci-operator.yaml build root tag to rhel-9-release-golang-1.26-openshift-5.0

The 5.0 base image includes the DEFAULT:PQ crypto-policy configuration from openshift/images#230, enabling post-quantum cryptography support.

Related: #190

Test plan

  • CI e2e tests pass with updated base image
  • Verify coredns binary runs correctly on the new base image with DEFAULT:PQ policy

🤖 Generated with Claude Code

…licy

Update Dockerfile.ocp and .ci-operator.yaml to reference the 5.0 base
and builder images which include the DEFAULT:PQ crypto-policy configuration
from openshift/images#230.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.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 Jun 26, 2026
@openshift-ci

openshift-ci Bot commented Jun 26, 2026

Copy link
Copy Markdown

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci-robot

openshift-ci-robot commented Jun 26, 2026

Copy link
Copy Markdown

@davidesalerno: This pull request references NE-2760 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 story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

  • Update Dockerfile.ocp builder image from rhel-9-golang-1.25-openshift-4.22 to rhel-9-golang-1.26-openshift-5.0
  • Update Dockerfile.ocp base image from ocp/4.22:base-rhel9 to ocp/5.0:base-rhel9
  • Update .ci-operator.yaml build root tag to rhel-9-release-golang-1.26-openshift-5.0

The 5.0 base image includes the DEFAULT:PQ crypto-policy configuration from openshift/images#230, enabling post-quantum cryptography support.

Related: #190

Test plan

  • CI e2e tests pass with updated base image
  • Verify coredns binary runs correctly on the new base image with DEFAULT:PQ policy

🤖 Generated with Claude Code

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 openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 26, 2026
@coderabbitai

coderabbitai Bot commented Jun 26, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: d71f08aa-cedd-4cf4-9ed7-015892f8de92

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@openshift-ci

openshift-ci Bot commented Jun 26, 2026

Copy link
Copy Markdown

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants