Add 10-15 minute synchronization wait guidance to upgrade documentation

[chinameok]

Summary by CodeRabbit

• Documentation
  • Updated cluster plugin upgrade guidance to include synchronization wait time (10–15 minutes) after uploading new versions.
  • Enhanced operator upgrade documentation with conditional upgrade paths: automatic upgrades for Automatic approval strategy, and manual approval options (batch or individual) for Manual strategy.
  • Clarified workload cluster upgrade instructions with improved formatting and timing expectations for upgrade availability.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Documentation updates across three upgrade-related files add synchronization wait instructions (10–15 minutes post-upload) and expand Operator upgrade guidance with conditional approval strategies and detailed manual upgrade methods.

Changes

Cohort / File(s)	Summary
Synchronization Wait Guidance docs/en/extend/cluster_plugin.mdx, docs/en/extend/operator.mdx, docs/en/upgrade/upgrade_workload_cluster.mdx	Adds ~10–15 minute post-upload/post-command synchronization wait instructions to upgrade processes.
Operator Upgrade Enhancement docs/en/extend/operator.mdx	Rewrites Upgrade Process section with conditional upgrade behavior based on Subscription Approval Strategy (Automatic vs. Manual), expands Manual upgrade guidance (Batch and Individual methods), and adds vendor-specific note for batch upgrades.
Workload Cluster Upgrade Formatting docs/en/upgrade/upgrade_workload_cluster.mdx	Removes numbered list formatting, converts to plain text, adds blank lines for readability, and appends post-command synchronization wait instruction.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

• Review focuses on documentation clarity and consistency of the synchronization wait guidance across three files.
• Verify the conditional Approval Strategy logic in Operator upgrade documentation is accurately described.
• Confirm formatting changes in workload cluster upgrade documentation improve readability without altering meaning.

Possibly related PRs

• Upgrade/violet push #180: Adds the same ~10–15 minute post-upload/synchronization wait guidance to upgrade documentation files.
• doc: get upgrade instructions ready for 4.2.x #352: Modifies upgrade_workload_cluster.mdx and Operator/Cluster Plugin docs with similar synchronization wait instructions and upgrade flow simplification.
• install, upgrade for acp 4.1 and fix dr #104: Updates upgrade/upload documentation files (upgrade_workload_cluster.mdx, Operator, and Cluster Plugin docs) with synchronized post-action wait steps.

Poem

🐰 Patience, dear users, a virtue most grand,
Ten minutes to sync—let the platform expand,
Approval paths split: auto or hand,
The docs now run clearer across all the land! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title accurately captures the main change: adding synchronization wait guidance (10-15 minutes) across three upgrade documentation files.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch AIT-56860

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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