docs: add RHOAI to MaaS release mapping table [RHOAIENG-62677]

[jira-autofix]

Add an authoritative version-mapping reference so support, CI, and field
teams can look up the MaaS component version (and production image tag)
for any given RHOAI GA release without reverse-engineering build artifacts.

The new page lives under docs/content/reference/rhoai-maas-versions.md
and is linked from both the mkdocs nav (Home section) and the existing
release-strategy doc.

Closes RHOAIENG-62677

Co-Authored-By: Claude noreply@anthropic.com
Signed-off-by: Jamie Land jland@redhat.com

Summary by CodeRabbit

• Documentation
  • Added a new version-mapping guide that defines supported RHOAI versions and corresponding MaaS versions, including GA/TP status and notes.
  • Provided a clear version mapping table and guidance on how image tags map to RHOAI vs MaaS versions.
  • Documented branch-to-RHOAI feed relationships and the operator channel for RHOAI 3.x.
  • Included instructions for updating the mapping when GA releases change bundled MaaS versions.
  • Added a navigation entry and updated the release strategy to reference the authoritative mapping.

[openshift-ci-robot]

@jira-autofix[bot]: This pull request references RHOAIENG-62677 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target either version "5.0." or "openshift-5.0.", but it targets "rhoai-3.5" instead.

Details

In response to this:

Add an authoritative version-mapping reference so support, CI, and field
teams can look up the MaaS component version (and production image tag)
for any given RHOAI GA release without reverse-engineering build artifacts.

The new page lives under docs/content/reference/rhoai-maas-versions.md
and is linked from both the mkdocs nav (Home section) and the existing
release-strategy doc.

Closes RHOAIENG-62677

Co-Authored-By: Claude noreply@anthropic.com
Signed-off-by: Jamie Land jland@redhat.com

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.

[openshift-ci]

Hi @jira-autofix[bot]. Thanks for your PR.

I'm waiting for a opendatahub-io member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR adds a new reference page docs/content/reference/rhoai-maas-versions.md that documents RHOAI-to-MaaS version mappings, image/tag guidance, branch-to-RHOAI feed mappings, operator channel info, and an update rule for GA bumps. It also references the new page from docs/content/contributing/release-strategy.md and adds a “RHOAI ↔ MaaS Versions” entry to the site navigation in docs/mkdocs.yml.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding RHOAI ↔ MaaS version mapping documentation with a new reference page and navigation updates.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/content/reference/rhoai-maas-versions.md`:
- Around line 11-12: The table currently lists RHOAI 3.4 twice mapped to MaaS
v0.1.1 and v0.1.0, causing ambiguity; update the table so each RHOAI release
maps to a single MaaS release by either (a) splitting RHOAI 3.4 into explicit
sub-releases (e.g., "RHOAI 3.4.0" vs "RHOAI 3.4.1") and updating the rows for
MaaS v0.1.0 and v0.1.1 accordingly, or (b) removing/marking the stale MaaS entry
(v0.1.0 or v0.1.1) as deprecated and leaving only the current mapping, and add a
brief note or new "Sub-release/Status" column to indicate upgrade relationships
so users can unambiguously determine which MaaS version corresponds to RHOAI
3.4.
- Line 14: Update the table row containing the MaaS version value "0.0.1" so it
uses the same "v" prefix as the other entries (change "0.0.1" to "v0.0.1" in the
row "| 3.0           | 0.0.1        | —               | TP     | Initial MaaS
release; tier-based access model, manual deployment only. |"), preserving
spacing/alignment so the table formatting remains consistent.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 64dfd1c3-2f44-45a9-96bd-c3002c63330f

📥 Commits

Reviewing files that changed from the base of the PR and between 7f759eb and 7793728.

📒 Files selected for processing (3)

• docs/content/contributing/release-strategy.md
• docs/content/reference/rhoai-maas-versions.md
• docs/mkdocs.yml

[openshift-ci-robot]

@jira-autofix[bot]: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

Add an authoritative version-mapping reference so support, CI, and field
teams can look up the MaaS component version (and production image tag)
for any given RHOAI GA release without reverse-engineering build artifacts.

The new page lives under docs/content/reference/rhoai-maas-versions.md
and is linked from both the mkdocs nav (Home section) and the existing
release-strategy doc.

Closes RHOAIENG-62677

Co-Authored-By: Claude noreply@anthropic.com
Signed-off-by: Jamie Land jland@redhat.com

Summary by CodeRabbit

• Documentation
• Added a new version-mapping guide that defines supported RHOAI versions and corresponding MaaS versions, including GA/TP status and notes.
• Provided a clear version mapping table and guidance on how image tags map to RHOAI vs MaaS versions.
• Documented branch-to-RHOAI feed relationships and the operator channel for RHOAI 3.x.
• Included instructions for updating the mapping when GA releases change bundled MaaS versions.
• Added a navigation entry and updated the release strategy to reference the authoritative mapping.

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.

[Jaland]

lgtm

[openshift-ci]

@Jaland: changing LGTM is restricted to collaborators

Details

In response to this:

lgtm

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Jaland, jira-autofix[bot]
Once this PR has been reviewed and has the lgtm label, please assign jland-redhat 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]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/content/reference/rhoai-maas-versions.md`:
- Line 11: The markdown table row contains a broken link
`../migration/upgrade-3.2-to-3.4.md` which fails link validation and blocks
deployment; fix by either creating the missing migration guide file at that path
with the upgrade content, or remove/replace the link in the table cell (the row
containing "3.4 | v0.1.0 | `v3.4` | GA | Subscription-driven...") so it uses
plain text or a valid existing link instead.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 3aa5e097-30d3-41c2-88b8-4886ecafad3c

📥 Commits

Reviewing files that changed from the base of the PR and between 08258d2 and cf53ca9.

📒 Files selected for processing (1)

• docs/content/reference/rhoai-maas-versions.md

[coderabbitai]

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Broken link blocks deployment.

Pipeline failures confirm ../migration/upgrade-3.2-to-3.4.md does not exist. Link-validation check fails deployment. Either remove the link reference or create the migration guide file.

🔧 Immediate fix: remove broken link

-| 3.4           | v0.1.0       | `v3.4`          | GA     | Subscription-driven access model; tier system removed. See [upgrade guide](../migration/upgrade-3.2-to-3.4.md). |
+| 3.4           | v0.1.0       | `v3.4`          | GA     | Subscription-driven access model; tier system removed. |

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	| 3.4 | v0.1.0 | `v3.4` | GA | Subscription-driven access model; tier system removed. See [upgrade guide](../migration/upgrade-3.2-to-3.4.md). |
	| 3.4 | v0.1.0 | `v3.4` | GA | Subscription-driven access model; tier system removed. |

🧰 Tools

🪛 GitHub Actions: Deploy Documentation to GitHub Pages / 1_link-validation.txt

[error] 11-120: mlc markup link checker failed: Target filename not found for relative link '../migration/upgrade-3.2-to-3.4.md'.

🪛 GitHub Actions: Deploy Documentation to GitHub Pages / link-validation

[error] 11-120: mlc link checker failed: target filename not found for reference '../migration/upgrade-3.2-to-3.4.md'.

🪛 GitHub Check: link-validation

[failure] 11-11: broken link
/github/workspace/docs/content/reference/../migration/upgrade-3.2-to-3.4.md. Target filename not found.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/content/reference/rhoai-maas-versions.md` at line 11, The markdown table
row contains a broken link `../migration/upgrade-3.2-to-3.4.md` which fails link
validation and blocks deployment; fix by either creating the missing migration
guide file at that path with the upgrade content, or remove/replace the link in
the table cell (the row containing "3.4 | v0.1.0 | `v3.4` | GA |
Subscription-driven...") so it uses plain text or a valid existing link instead.