docs: update Migration Guide version mapping for current releases - #1280
docs: update Migration Guide version mapping for current releases#1280sudhishmk wants to merge 1 commit into
Conversation
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>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
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 Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (1)
🔗 Linked repositories identifiedCodeRabbit considers these linked repositories for cross-repo context during reviews:
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. 📝 SummarySummary by CodeRabbit
WalkthroughThe 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. ChangesMigration guide version mapping
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to 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)
Comment |
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.mdso users migrating from Argo CD Community Operator can choose a current GitOps Operator release (through v1.20.x).Have you updated the necessary documentation?
Which issue(s) this PR fixes:
Fixes #1279
Test acceptance criteria:
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.