Skip to content

Cherry-pick-859-3.1 version - Added the table for clusters and methods for upgrade (#859) #908

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: release-3.1
Choose a base branch
from
Open

Cherry-pick-859-3.1 version - Added the table for clusters and methods for upgrade (#859) #908

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b82c900
Added the table for clusters and methods for upgrade (#859)
ranjinimn Oct 13, 2025
8f15892
Feedback from Steven
ranjinimn Oct 16, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions asciidoc/day2/migration.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,23 @@ This section offers migration guidelines for existing `Edge 3.0` (including mino

For a list of `Edge 3.1.0` component versions, refer to the <<release-notes, release notes>>.

The following table lists the different types of clusters and the methods to upgrade clusters:

[[Clusters-and-methods-to-upgrade-downstream-clusters]]
.Clusters and methods to upgrade downstream clusters
|===
| Cluster type | Method

|EIB provisioned clusters
|See <<day2-migration-mgmt-fleet>> for details.
Copy link
Collaborator Author

@ranjinimn ranjinimn Oct 16, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

@hardys When I was checking 3.1 version, this section was not there. Should we remove this table if this is not relevant for 3.1?

The build fails because of the missing section.


|Metal^3^ provisioned clusters
|See <<atip-lifecycle-downstream, Downstream cluster upgrades>> for details.

|Phone-home provisioned clusters
|See https://ranchermanager.docs.rancher.com/v2.9/getting-started/installation-and-upgrade/upgrade-and-roll-back-kubernetes#upgrading-the-kubernetes-version[Upgrading the Kubernetes Version] for Kubernetes version upgrade and <<day2-downstream-clusters, Downstream clusters>> for SUC, Operating system, and other components.
|===

[#day2-migration-mgmt]
== Management cluster

Expand Down