Documentation mismatch: aarch64 (arm64) support claimed in README but images missing on quay.io

[EdisonSu768]

Description

There is a discrepancy between the stated architecture support in the README.md and the actual images published to quay.io.

The README's Image Inventory List marks several CPU workbench images (such as jupyter-minimal-ubi9-python-3.12 / jupyter-minimal-cpu-py312-ubi9) with a ✅ for aarch64 support.

However, when pulling these images or checking the tags on quay.io (e.g., odh-workbench-jupyter-minimal-cpu-py312-ubi9 tags), there are no arm64 / aarch64 manifests available.

Investigation

Looking at the CI configuration in ci/cached-builds/gen_gha_matrix_jobs.py, it appears the ARM64_COMPATIBLE list is currently restricted to:

• codeserver-ubi9-python-3.12
• cuda-jupyter-minimal-ubi9-python-3.12
• cuda-jupyter-tensorflow-ubi9-python-3.12
• runtime-cuda-tensorflow-ubi9-python-3.12

The standard CPU workbenches (like jupyter-minimal or jupyter-datascience) are missing from this CI matrix, which explains why they aren't being built and pushed to quay.io for arm64.

Questions/Suggestions

1. Are there blockers preventing the inclusion of these CPU images in the ARM64_COMPATIBLE list for the CI pipeline?
2. If arm64 builds for these CPU images are not ready or supported yet, should we update the README.md to remove the ✅ for aarch64 to avoid confusing users?