Skip to content

NO-JIRA: [RHCOS10] Test existing UBI9 base images on RHCOS10 nodes (no changes) #452

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
PillaiManish wants to merge 1 commit into
base: main
Choose a base branch
from
+39 −0
Open

NO-JIRA: [RHCOS10] Test existing UBI9 base images on RHCOS10 nodes (no changes) #452

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 39 additions & 0 deletions .work/compliance/rhcos10/PR1-ubi9-compat-test.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
# PR1: RHCOS10 Compatibility Test — Existing UBI9 Images

## Purpose

This PR contains **no Dockerfile changes**. Its goal is to validate that the existing
UBI9-based images build and run correctly on RHCOS10 cluster nodes, before committing
to a full base-image migration.

## Background

Red Hat CoreOS 10 (RHCOS10) ships with RHEL10 as its host OS. While UBI9-based container
images are expected to remain compatible with RHCOS10 (containers are isolated from the
host), this PR triggers CI against an RHCOS10 cluster to confirm there are no runtime
surprises before we proceed with the UBI10 migration (see PR2).

## Images Under Test

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:
Comment on lines +18 to +19
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot Mar 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

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.


| Image | Dockerfile | Base Image |
|---|---|---|
| helm-operator | `images/helm-operator/Dockerfile` | `ubi9/ubi-minimal:9.6` |
| operator-sdk | `images/operator-sdk/Dockerfile` | `ubi9/ubi-minimal:9.6` |
| scorecard-test | `images/scorecard-test/Dockerfile` | `ubi9/ubi-minimal:9.6` |
| custom-scorecard-tests | `images/custom-scorecard-tests/Dockerfile` | `ubi9/ubi-minimal:9.6` |
| scorecard-untar | `images/scorecard-untar/Dockerfile` | `ubi9/ubi:9.5` |
| go-e2e (CI) | `ci/dockerfiles/go-e2e.Dockerfile` | `ubi9/ubi-minimal:latest` |
| scorecard-proxy (CI) | `ci/dockerfiles/scorecard-proxy.Dockerfile` | `ubi9/ubi-minimal:latest` |

## Expected Outcome

- All existing CI jobs pass on RHCOS10 nodes with UBI9 base images unchanged
- No runtime incompatibilities between UBI9 containers and the RHCOS10 host

## Follow-up

If this PR passes, PR2 (`rhcos10-ubi10-migration`) migrates all base images to UBI10,
which is the native base for RHCOS10.