-
Notifications
You must be signed in to change notification settings - Fork 40
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.
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
base: release-3.1
Are you sure you want to change the base?
Conversation
Signed-off-by: Ranjini M N <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Currently issues like that mentioned in suse-edge#908 won't be caught because we're not testing stable branch PRs
Currently issues like that mentioned in #908 won't be caught because we're not testing stable branch PRs
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)
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)
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)
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)
| | Cluster type | Method | ||
|
|
||
| |EIB provisioned clusters | ||
| |See <<day2-migration-mgmt-fleet>> for details. |
There was a problem hiding this comment.
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.
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)
https://github.com/suse-edge/suse-edge.github.io/pull/859/files
#829 (comment)