Skip to content

Conversation

atheo89
Copy link
Member

@atheo89 atheo89 commented Sep 19, 2025

Added inventory table with the list of images

Description

How Has This Been Tested?

Self checklist (all need to be checked):

  • Ensure that you have run make test (gmake on macOS) before asking for review
  • Changes to everything except Dockerfile.konflux files should be done in odh/notebooks and automatically synced to rhds/notebooks. For Konflux-specific changes, modify Dockerfile.konflux files directly in rhds/notebooks as these require special attention in the downstream repository and flow to the upcoming RHOAI release.

Merge criteria:

  • The commits are squashed in a cohesive manner and have meaningful messages.
  • Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
  • The developer has manually tested the changes and verified that the changes work

Summary by CodeRabbit

  • Documentation
    • Added “Image Inventory List” section detailing support statuses for container images, including Workbench and Runtime tables with per-architecture availability and container URLs.
    • Included a legend explaining status icons for quick reference.
    • Introduced a “For AI Agents” subsection linking to the Agents Guide for further guidance.

@github-actions github-actions bot added the review-requested GitHub Bot creates notification on #pr-review-ai-ide-team slack channel label Sep 19, 2025
Copy link
Contributor

coderabbitai bot commented Sep 19, 2025

Walkthrough

Adds an “Image Inventory List” section with two tables (Workbench and Runtime) indicating per-architecture support and container URLs, plus a legend for status icons. Inserts this inventory block twice in README.md. Also adds a “For AI Agents” subsection linking to an Agents Guide. No code or API changes.

Changes

Cohort / File(s) Summary
Docs update
README.md
Added “Image Inventory List” section with Workbench and Runtime tables, status legend, and container URLs; inserted the inventory block in two locations (duplicate). Added “For AI Agents” subsection linking to Agents Guide.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Description Check ⚠️ Warning The PR description contains the repository template but is largely unfilled: the Description section provides no details about the changes, the "How Has This Been Tested?" section has no test steps or results, and the self-checklist and merge criteria boxes are left unchecked, which prevents reviewers from assessing validation and readiness. Because these required sections are missing substantive content, the description does not meet the repository's template expectations. This makes the check fail as reviewers lack the information needed to validate the change. Please populate the Description with a clear summary of what was changed (e.g., that image inventory tables were added to README and note duplicated insertion), fill "How Has This Been Tested?" with environment, commands run and test outcomes (include whether you ran make test), and update the self-checklist and merge criteria boxes or explain exceptions; also add any testing instructions and ensure commits are squashed with meaningful messages before requesting review. After these updates reviewers can verify functionality and approve the PR.
✅ Passed checks (2 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
Title Check ✅ Passed The title accurately and concisely describes the primary change — adding an inventory table of images and supported architectures to the README — and matches the PR summary and file diffs. It is specific, relevant to the main change, and uses a conventional commit scope which helps history scanning. The phrasing is clear and sufficient for a reviewer to understand the PR's purpose at a glance.
✨ Finishing touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@openshift-ci openshift-ci bot added size/m and removed size/m labels Sep 19, 2025
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (6)
README.md (6)

183-185: Add provenance: last-updated note and source-of-truth pointer.

This static table will drift. Add a “Last updated: YYYY‑MM‑DD” note and link to the source-of-truth manifests (runtime/workbench JSON or build matrix), or mark the section as auto‑generated with regeneration instructions.


186-201: Normalize status symbols; avoid “/?” variants.

Cells like “⚠️/?” and “⏰/?” are ambiguous. Keep to the legend’s four states only: ✅, ⚠️, ⏰, ❌. If unknown, prefer ⚠️ with a footnote.


193-197: CUDA/RHEL minor versions could become stale.

“UBI9/RHEL9.6” in OS may age quickly. Consider “UBI9/RHEL9 (tested on 9.6)” or footnote the tested minor to reduce churn.


212-216: Fix markdownlint MD004: use dashes for unordered list.

Switch asterisks to dashes to satisfy the linter.

Apply this diff:

-* ✅ supported
-* ⚠️ under development
-* ⏰ planned in the future
-* ❌ not supported by vendor
+- ✅ supported
+- ⚠️ under development
+- ⏰ planned in the future
+- ❌ not supported by vendor

186-204: Unify column headers across tables.

Workbench uses “OS”; Runtime uses “UBI”. Pick one (“OS”) and keep consistent ordering.

Also applies to: 206-209


186-201: Replace per-image quay.io links in README with quay.io/repository/opendatahub/workbench-images (prefer image@sha256 for immutability).

Manifests/kustomize in the repo reference workbench-images; the README table currently links to per-image repos (e.g., quay.io/repository/opendatahub/odh-workbench-…), replace the Container column with the workbench-images tag pattern or immutable digests.
Location: README.md (table around lines 186–201).

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3859361 and aad9f19.

📒 Files selected for processing (1)
  • README.md (1 hunks)
🧰 Additional context used
🧠 Learnings (3)
📚 Learning: 2025-09-12T08:39:17.540Z
Learnt from: jiridanek
PR: opendatahub-io/notebooks#2432
File: jupyter/datascience/ubi9-python-3.12/pylock.toml:534-536
Timestamp: 2025-09-12T08:39:17.540Z
Learning: In the opendatahub-io/notebooks project, not all container images are s390x enabled yet. Images without platform markers (like `marker = "platform_machine != 's390x'"`) simply haven't been patched for s390x support yet, indicating a phased rollout approach for s390x enablement across different notebook images.

Applied to files:

  • README.md
📚 Learning: 2025-07-29T15:56:20.036Z
Learnt from: jiridanek
PR: opendatahub-io/notebooks#1519
File: jupyter/pytorch+llmcompressor/ubi9-python-3.11/runtime-images/llmcompressor-pytorch-ubi9-py311.json:2-9
Timestamp: 2025-07-29T15:56:20.036Z
Learning: Current practice for runtime-images JSON files in opendatahub-io/notebooks: All runtime image configurations use SHA256 digest pinning (format: `sha256:<digest>`) instead of mutable tags for immutability, use `quay.io/opendatahub/workbench-images` registry, include `schema_name: "runtime-image"` field, and follow consistent structure as seen in existing files like datascience-ubi9-py311.json, pytorch-ubi9-py311.json, etc.

Applied to files:

  • README.md
📚 Learning: 2025-07-04T10:41:13.061Z
Learnt from: grdryn
PR: opendatahub-io/notebooks#1320
File: rstudio/rhel9-python-3.11/Dockerfile.cuda:34-35
Timestamp: 2025-07-04T10:41:13.061Z
Learning: In the opendatahub-io/notebooks repository, when adapting NVIDIA CUDA Dockerfiles, the project intentionally maintains consistency with upstream NVIDIA patterns even when it might involve potential risks like empty variable expansions in package installation commands. This is considered acceptable because the containers only run on RHEL 9 with known yum/dnf behavior, and upstream consistency is prioritized over defensive coding practices.

Applied to files:

  • README.md
🪛 markdownlint-cli2 (0.17.2)
README.md

212-212: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


213-213: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


214-214: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


215-215: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: code-static-analysis
🔇 Additional comments (2)
README.md (2)

186-201: Architecture status likely over-claimed; verify s390x/ppc64le/aarch64 columns.

Several rows mark s390x as fully supported (✅). In this repo, s390x enablement is still rolling out and gated per image. Please cross-check before publishing.

To audit quickly from the repo:

If uncertain, downgrade to ⚠️ (under development) or ⏰ (planned) until verified.


202-211: Confirm runtime table: repo links and arch support

  • Links in README.md (Runtime table) point to per-image repos (quay.io/repository/opendatahub/odh-pipeline-runtime-…). Use the canonical workbench-images repo for published images or confirm the intent and update links.
  • Verify architecture columns (aarch64 / ppc64le / s390x / x86_64) with the same scripts used for the Workbench table and align the Runtime rows (replace ⏰/? with accurate ✅/❌).

Location: README.md lines 202–211.

@atheo89
Copy link
Member Author

atheo89 commented Sep 19, 2025

Hey @Shafi-Hussain and @Nash-123 👋
I am trying to create a inventory table with our images and the supporting archs check here. I have added on some images the archs that we already support, but i left some others with ⚠️/? or ⏰/?. Could you please help me finalize that table? Like which are will be under under development, or planned in the future, or no scope -. Looking forward for you comments.

@jiridanek jiridanek changed the title Added inventory table with the list of images chore(README.md): add inventory table with the list of images and supported architectures Sep 19, 2025
@openshift-ci openshift-ci bot added size/m and removed size/m labels Sep 19, 2025
Copy link
Member

@jiridanek jiridanek left a comment

Choose a reason for hiding this comment

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

this will be annoying to maintain, but it does look nice ;p

Copy link
Contributor

openshift-ci bot commented Sep 19, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jiridanek

The full list of commands accepted by this bot can be found here.

The pull request process is described here

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

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 39a5bf4 and 2 for PR HEAD aad9f19 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 40b9290 and 1 for PR HEAD aad9f19 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD fdc238b and 0 for PR HEAD aad9f19 in total

Copy link
Contributor

openshift-ci bot commented Sep 22, 2025

@atheo89: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/images aad9f19 link true /test images

Full PR test history. Your PR dashboard.

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.

@openshift-ci-robot
Copy link

/hold

Revision aad9f19 was retested 3 times: holding

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved do-not-merge/hold lgtm review-requested GitHub Bot creates notification on #pr-review-ai-ide-team slack channel size/m
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants