Skip to content
Open
Changes from all commits
Commits
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
38 changes: 38 additions & 0 deletions docs/rhcos10-ubi9-compat-test.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
# RHCOS10 UBI9 Compatibility Test

## Summary

Validate that the existing UBI9/RHEL9-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 RHEL9-based containers remain compatible before committing to a base image
migration.

**No Dockerfile or manifest changes.** This is a baseline/smoke test only.

## Images Under Test

| Image | Current Base |
|-------|-------------|
| `secrets-store-csi-driver-operator` | `registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.24-openshift-4.22` (builder) / `registry.ci.openshift.org/ocp/4.22:base-rhel9` (runtime) |
| `secrets-store-csi-driver-mustgather` | `registry.ci.openshift.org/ocp/4.22:must-gather` |

CI build root: `rhel-9-release-golang-1.24-openshift-4.22`

## Test Matrix

| Cluster | Test Suite | Expected |
|---------|-----------|---------|
| RHCOS10 | e2e-azure-rhcos10 | Pass |
| RHCOS10 | e2e-azure-rhcos10-fips | Pass |

## Expected Outcome

- All existing e2e tests pass on RHCOS10 nodes with UBI9-based images.
- No runtime compatibility issues between RHEL9 containers and RHCOS10 hosts.

## Follow-up

If CI passes → PR2 ([rhcos10-ubi10-migration](../)) migrates all base images from
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Fix the broken link to the follow-up PR.

The link [rhcos10-ubi10-migration](../) points only to the parent directory instead of a specific PR or document. This will be confusing for readers trying to navigate to the referenced migration work.

Consider one of these options:

  • Link to a specific issue/PR number if it exists (e.g., #108 or full URL)
  • Remove the link and use plain text if the PR hasn't been created yet: PR2 (rhcos10-ubi10-migration)
  • Link to a tracking issue or epic that will contain the migration PR
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docs/rhcos10-ubi9-compat-test.md` at line 37, The markdown link
"[rhcos10-ubi10-migration](../)" is pointing to the parent directory instead of
a specific PR or doc; update the link target for clarity by either replacing the
relative "../" target with the full URL or issue/PR number (e.g., the PR URL or
"#<PR_NUMBER>") or, if the PR doesn't exist yet, remove the markdown link and
make it plain text "PR2 (rhcos10-ubi10-migration)"; locate and edit the link
text "[rhcos10-ubi10-migration](../)" in docs/rhcos10-ubi9-compat-test.md to
apply the chosen fix.

UBI9/RHEL9 to UBI10/RHEL10.