NO-JIRA: [RHCOS10] Test existing UBI9 base images on RHCOS10 nodes (no changes)#452
NO-JIRA: [RHCOS10] Test existing UBI9 base images on RHCOS10 nodes (no changes)#452PillaiManish wants to merge 1 commit intoopenshift:mainfrom
Conversation
Add documentation to track the RHCOS10 baseline compatibility test. No Dockerfile changes — this PR validates existing UBI9-based images run correctly on RHCOS10 cluster nodes before migrating to UBI10. Made-with: Cursor
openshift-ci-robot
added
the
jira/valid-reference
|
@PillaiManish: This pull request explicitly references no jira issue. DetailsIn response to this:
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. |
WalkthroughAdded a new CI compliance documentation file describing an RHCOS10 compatibility test for existing UBI9-based container images, outlining test purpose, affected images, expected outcomes, and follow-up UBI10 migration actions. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/test e2e-helm-fips e2e-helm-rhcos10-fips e2e-helm-rhcos10 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.work/compliance/rhcos10/PR1-ubi9-compat-test.md:
- Around line 18-19: Update the statement that currently claims "All images
currently use `registry.access.redhat.com/ubi9/ubi-minimal:9.6` or
`registry.access.redhat.com/ubi9/ubi:9.5`" so it matches the table entries that
also reference `ubi9/ubi-minimal:latest`: either add `:latest` to the list
(e.g., "9.6, 9.5, or latest") or split into two clauses distinguishing product
images vs CI images (e.g., "product images use 9.6/9.5; CI images use
ubi9/ubi-minimal:latest") ensuring the sentence near the top and the CI image
rows in the table are consistent.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 382d9dc8-00af-4cf9-94c9-08a085432200
📒 Files selected for processing (1)
.work/compliance/rhcos10/PR1-ubi9-compat-test.md
| All images currently use `registry.access.redhat.com/ubi9/ubi-minimal:9.6` or | ||
| `registry.access.redhat.com/ubi9/ubi:9.5` as their final base image: |
There was a problem hiding this comment.
Clarify base-image version statement to match the table.
Line 18–19 says all images use only 9.6/9.5, but Line 28–29 lists CI images on ubi9/ubi-minimal:latest. Please update the sentence to include latest (or split product vs CI image wording) so the document is internally consistent.
Also applies to: 28-29
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.work/compliance/rhcos10/PR1-ubi9-compat-test.md around lines 18 - 19,
Update the statement that currently claims "All images currently use
`registry.access.redhat.com/ubi9/ubi-minimal:9.6` or
`registry.access.redhat.com/ubi9/ubi:9.5`" so it matches the table entries that
also reference `ubi9/ubi-minimal:latest`: either add `:latest` to the list
(e.g., "9.6, 9.5, or latest") or split into two clauses distinguishing product
images vs CI images (e.g., "product images use 9.6/9.5; CI images use
ubi9/ubi-minimal:latest") ensuring the sentence near the top and the CI image
rows in the table are consistent.
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: PillaiManish The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/retest |
|
/test e2e-helm-fips e2e-helm-rhcos10-fips e2e-helm-rhcos10 |
|
@PillaiManish: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
2 participants
Summary
Validate that the existing UBI9-based images run correctly on RHCOS10 cluster nodes without any changes.
RHCOS10 ships with RHEL10 as its host OS. This PR triggers CI against an RHCOS10 cluster to confirm
UBI9 containers remain compatible before committing to a base image migration.
No Dockerfile changes. This is a baseline/smoke test only.
Follow-up
If CI passes → PR2 migrates all base images from UBI9 to UBI10.