Skip to content

docs: update Migration Guide version mapping for current releases - #1280

Open
sudhishmk wants to merge 1 commit into
redhat-developer:masterfrom
sudhishmk:docs/update-migration-guide-version-table
Open

docs: update Migration Guide version mapping for current releases#1280
sudhishmk wants to merge 1 commit into
redhat-developer:masterfrom
sudhishmk:docs/update-migration-guide-version-table

Conversation

@sudhishmk

@sudhishmk sudhishmk commented Sep 6, 2026

Copy link
Copy Markdown

Extend the community-operator-to-GitOps migration table through v1.20 and add a pointer to RH release notes for exact patch versions. Fixes #1279

What type of PR is this?
/kind documentation

What does this PR do / why we need it:
Updates the version mapping table in docs/Migration_Guide.md so users migrating from Argo CD Community Operator can choose a current GitOps Operator release (through v1.20.x).

Have you updated the necessary documentation?

  • Documentation update is required by this PR.
  • Documentation has been updated.

Which issue(s) this PR fixes:
Fixes #1279

Test acceptance criteria:

  • Unit Test
  • E2E Test

How to test changes / Special notes to the reviewer:
Docs-only change. Please verify version rows against RH OpenShift GitOps 1.20/1.16/1.15 release notes.

Extend the community-operator-to-GitOps migration table through v1.20
and add a pointer to RH release notes for exact patch versions.
Fixes redhat-developer#1279

Signed-off-by: Sudhish Nair <sudhish_mk@yahoo.co.in>
@openshift-ci openshift-ci Bot added the kind/documentation Improvements or additions to documentation label Sep 6, 2026
@openshift-ci

openshift-ci Bot commented Sep 6, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign olivergondza 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:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci

openshift-ci Bot commented Sep 6, 2026

Copy link
Copy Markdown

Hi @sudhishmk. Thanks for your PR.

I'm waiting for a redhat-developer 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

coderabbitai Bot commented Sep 6, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Team

Run ID: a2ecd91d-030f-47cc-b811-7a5676753465

📥 Commits

Reviewing files that changed from the base of the PR and between fb60a7a and 4b9e697.

📒 Files selected for processing (1)
  • docs/Migration_Guide.md
🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

  • argoproj-labs/argocd-operator (manual)

Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review.


📝 Summary

Summary by CodeRabbit

  • Documentation
    • Updated the migration guide’s version compatibility table with current GitOps and Argo CD Operator mappings.
    • Added support information for newer Argo CD versions.
    • Added a reference to Red Hat OpenShift GitOps release notes for exact component versions.

Walkthrough

The migration guide updates its version compatibility table with GitOps Operator releases from v1.15.z through v1.20.z, corresponding Argo CD Operator versions, default Argo CD versions, and a link to Red Hat OpenShift GitOps release notes.

Changes

Migration guide version mapping

Layer / File(s) Summary
Update version compatibility mappings
docs/Migration_Guide.md
The table replaces older release rows with current GitOps Operator, Argo CD Operator, and default Argo CD version mappings. A release-notes link provides exact component versions.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 4b9e6

The migration guide now documents newer GitOps Operator and Argo CD version mappings and directs readers to release notes for patch-level details. No current merge-readiness risk remains.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Linked Issues check ✅ Passed The change extends the Migration Guide table with the requested current GitOps Operator, Community Operator, and Argo CD versions, and adds a Red Hat release-notes link for exact patch versions [#1279
Out of Scope Changes check ✅ Passed The changes are limited to the requested Migration Guide version table and related release-notes reference.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Title check ✅ Passed The title clearly identifies the documentation change and the updated version mapping.
Description check ✅ Passed The description accurately explains the migration table update, release-notes link, scope, and testing context.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind/documentation Improvements or additions to documentation needs-ok-to-test

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: Update Migration Guide version mapping table for current GitOps releases

1 participant