Cherry-pick-859-3.1 version - Added the table for clusters and methods for upgrade (#859)#908
Open
ranjinimn wants to merge 2 commits intosuse-edge:release-3.1from
Open
Cherry-pick-859-3.1 version - Added the table for clusters and methods for upgrade (#859)#908ranjinimn wants to merge 2 commits intosuse-edge:release-3.1from
ranjinimn wants to merge 2 commits intosuse-edge:release-3.1from
Conversation
Signed-off-by: Ranjini M N <ranjini.n@suse.com>
hardys
requested changes
Oct 16, 2025
hardys
added a commit
to hardys/suse-edge.github.io
that referenced
this pull request
Oct 16, 2025
Currently issues like that mentioned in suse-edge#908 won't be caught because we're not testing stable branch PRs
hardys
added a commit
that referenced
this pull request
Oct 16, 2025
Currently issues like that mentioned in #908 won't be caught because we're not testing stable branch PRs
Closed
hardys
added a commit
to hardys/suse-edge.github.io
that referenced
this pull request
Oct 16, 2025
Currently issues like that mentioned in suse-edge#908 won't be caught because we're not testing stable branch PRs (cherry picked from commit 7229178)
hardys
added a commit
to hardys/suse-edge.github.io
that referenced
this pull request
Oct 16, 2025
Currently issues like that mentioned in suse-edge#908 won't be caught because we're not testing stable branch PRs (cherry picked from commit 7229178)
hardys
added a commit
to hardys/suse-edge.github.io
that referenced
this pull request
Oct 16, 2025
Currently issues like that mentioned in suse-edge#908 won't be caught because we're not testing stable branch PRs (cherry picked from commit 7229178)
hardys
added a commit
to hardys/suse-edge.github.io
that referenced
this pull request
Oct 16, 2025
Currently issues like that mentioned in suse-edge#908 won't be caught because we're not testing stable branch PRs (cherry picked from commit 7229178)
This was referenced Oct 16, 2025
ranjinimn
commented
Oct 16, 2025
| | Cluster type | Method | ||
|
|
||
| |EIB provisioned clusters | ||
| |See <<day2-migration-mgmt-fleet>> for details. |
Collaborator
Author
There was a problem hiding this comment.
@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.
ranjinimn
pushed a commit
to ranjinimn/suse-edge.github.io
that referenced
this pull request
Oct 21, 2025
Currently issues like that mentioned in suse-edge#908 won't be caught because we're not testing stable branch PRs (cherry picked from commit 7229178)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://github.com/suse-edge/suse-edge.github.io/pull/859/files
#829 (comment)