Skip to content

[CP 1609] docs(release): claim Radeon AI PRO support and 1.5.1 GA updates#607

Merged
spraveenio merged 3 commits into
ROCm:mainfrom
ci-penbot-01:CP.O2O.pensando.gpu-operator.1609.rocm.gpu-operator.main
Jul 17, 2026
Merged

[CP 1609] docs(release): claim Radeon AI PRO support and 1.5.1 GA updates#607
spraveenio merged 3 commits into
ROCm:mainfrom
ci-penbot-01:CP.O2O.pensando.gpu-operator.1609.rocm.gpu-operator.main

Conversation

@ci-penbot-01

Copy link
Copy Markdown
Contributor

cp of pensando/gpu-operator#1609


Source PR Description (pensando/gpu-operator#1609):

Summary

Documentation-only change for GPUOP-990. The public docs framed the operator as managing AMD Instinct-only accelerators even though v1.5.1 adds AMD Radeon™ AI PRO (RDNA 4) support.

  • Claim Radeon support in product-level framing (docs/index.md, README.md intros). The index.md hardware table already listed the Radeon AI PRO SKUs.
  • Bump supported version matrix: Kubernetes 1.29-1.351.29-1.36; RHCOS/OpenShift 4.16—4.204.16—4.22 (docs/index.md, docs/installation/kubernetes-helm.md).
  • Promote v1.5.1 release notes beta → GA: drop "(beta)", normalize brand casing to AMD Radeon™ AI PRO (R9700/R9700S), update per-platform ANR notes and Platform Support versions.
  • Add GA fix entry: driver-upgrade reboot exec format error fix (sync-before-reboot + DRA in pre-reboot drain list), linked to #1604.

Feature-specific "Instinct" references (DCM partitioning, XGMI topology scheduling, AFID event lists, KubeVirt VF examples) are intentionally left unchanged — those are CDNA-only features that do not apply to Radeon (RDNA) GPUs.

Plan: docs-internal/knowledge/plans/2026-07-17-gpuop-990-radeon-docs-1.5.1-ga.md

Test plan

  • Sphinx docs build (docs/) renders without errors
  • Confirm k8s 1.36 / OpenShift 4.22 match what QA validated for the 1.5.1 GA cut
  • Manual review of rendered release notes and index compatibility tables

🤖 Generated with Claude Code

Cherrypick triggered by: ACP-Automation

* docs(release): claim Radeon AI PRO support and 1.5.1 GA updates

Claim AMD Radeon AI PRO support in product-level docs where the operator
was framed as Instinct-only, bump the supported version matrix (k8s 1.36,
OpenShift 4.22), and promote the v1.5.1 release notes from beta to GA
including the driver-upgrade reboot exec-format-error fix.

Plan: docs-internal/knowledge/plans/2026-07-17-gpuop-990-radeon-docs-1.5.1-ga.md
Jira: GPUOP-990

Co-Authored-By: Claude <noreply@anthropic.com>

* docs(release): note ROCm 7.14 packaged in v1.5.1 operand images

Co-Authored-By: Claude <noreply@anthropic.com>

* docs(release): scope ROCm 7.14 note to exporter, test runner, DCM

Co-Authored-By: Claude <noreply@anthropic.com>

* Update docs/releasenotes.md

* Update releasenotes.md with cper working

---------

Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Praveen Kumar Shanmugam <58961022+spraveenio@users.noreply.github.com>
(cherry picked from commit e3a807d4ac36647f9ae6c73998970fcd84d366af)
@ci-penbot-01

Copy link
Copy Markdown
Contributor Author

AI-Assisted Cherry-Pick

Source PR: #1609
Target Branch: main

The cherry-pick operation encountered merge conflicts which were resolved automatically using AI assistance.

Files with conflicts (resolved by AI):

  • docs/installation/kubernetes-helm.md:19-23
Original conflict in docs/installation/kubernetes-helm.md
<<<<<<< HEAD
- Kubernetes cluster v1.29.0 or later
=======
- Kubernetes cluster v1.29.0 to v1.36.x
>>>>>>> e3a807d4... docs(release): claim Radeon AI PRO support and 1.5.1 GA updates (#1609)

Cherry-pick triggered by: ACP-Automation

@spraveenio spraveenio left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

LGTM

@spraveenio
spraveenio merged commit 7fa2d2b into ROCm:main Jul 17, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants