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

[PillaiManish]

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.

[openshift-ci-robot]

@PillaiManish: This pull request explicitly references no jira issue.

Details

In response to this:

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.

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.

[coderabbitai]

Walkthrough

A new markdown document is added to .work/compliance/rhcos10/ defining an RHCOS10 compatibility smoke-test plan for UBI9-based container images on RHCOS10 cluster nodes. The specification outlines purpose, scope, expected outcomes, and follow-up migration steps without introducing code or configuration changes.

Changes

Cohort / File(s)	Summary
RHCOS10 Compatibility Test Specification .work/compliance/rhcos10/PR1-ubi9-compat-test.md	New test specification document defining an RHCOS10 compatibility smoke-test plan, including scope of UBI9 image mappings, expected CI outcomes, and migration follow-up procedures.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

[coderabbitai]

🧹 Nitpick comments (1)

.work/compliance/rhcos10/PR1-ubi9-compat-test.md (1)

30-31: Add explicit pass criteria for reproducibility.

Consider naming the exact CI job(s) or test lane(s) that must be green on RHCOS10 (and optionally where results are recorded). That makes this compliance note auditable later.

🤖 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 30 - 31, The
acceptance criteria bullet "All CI jobs pass on RHCOS10 nodes with UBI9 images
unchanged." is too vague—update the note to list the exact CI job(s)/test
lane(s) that must be green (e.g., unit-test, integration-e2e, upgrade-path
lanes) and specify where pass/fail evidence is recorded (e.g., CI dashboard link
or build IDs); replace the generic line with a concrete checklist naming those
job identifiers and the recording location so the requirement is auditable.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In @.work/compliance/rhcos10/PR1-ubi9-compat-test.md:
- Around line 30-31: The acceptance criteria bullet "All CI jobs pass on RHCOS10
nodes with UBI9 images unchanged." is too vague—update the note to list the
exact CI job(s)/test lane(s) that must be green (e.g., unit-test,
integration-e2e, upgrade-path lanes) and specify where pass/fail evidence is
recorded (e.g., CI dashboard link or build IDs); replace the generic line with a
concrete checklist naming those job identifiers and the recording location so
the requirement is auditable.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b1398725-f0dc-4e94-9b81-251b9c9263cb

📥 Commits

Reviewing files that changed from the base of the PR and between 8c00498 and e05cf85.

📒 Files selected for processing (1)

• .work/compliance/rhcos10/PR1-ubi9-compat-test.md

[PillaiManish]

/test e2e-ansible-fips e2e-ansible-rhcos10-fips e2e-ansible-rhcos10

[openshift-ci]

@PillaiManish: all tests passed!

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.