Skip to content

Conversation

@ranjinimn
Copy link
Collaborator

#829

I have created the table as per the description provided.

For downstream clusters, we have (at least) 3 different scenarios, and each of them involve different upgrade procedures/mechanisms. AFAIK:

For EIB provisioned clusters -> Fleet approach
For Metal3 provisioned clusters -> Redeploy with a fresh image
For phone-home provisioned clusters -> K8s upgrade via rancher + SUC for the OS and everything else
It would be nice to have a table/matrix/something to explicitly clarify each scenario.

@ranjinimn
Copy link
Collaborator Author

@hardys and @e-minguez I created the table based on the information provided.
One question I had was regarding the inclusion of the "Upgrade controller" in this table? Is there any specific cluster for which we need to use this? Or is this generic?

@e-minguez
Copy link
Collaborator

e-minguez commented Sep 30, 2025

@hardys and @e-minguez I created the table based on the information provided. One question I had was regarding the inclusion of the "Upgrade controller" in this table? Is there any specific cluster for which we need to use this? Or is this generic?

https://documentation.suse.com/suse-edge/3.4/html/edge/components-upgrade-controller.html#components-upgrade-controller-known-issues

Downstream cluster upgrades are not yet managed by the Upgrade Controller.

Also

Currently the Upgrade Controller supports non air-gapped environment upgrades only. Air-gapped upgrades are not
yet possible.

@ranjinimn
Copy link
Collaborator Author

ranjinimn commented Oct 1, 2025

@e-minguez Okay. I will also wait for @hardys inputs on this before I make any changes.
Does that table look okay?

e-minguez
e-minguez previously approved these changes Oct 3, 2025
@hardys
Copy link
Contributor

hardys commented Oct 8, 2025

lgtm but looks like the branch needs a rebase?

@ranjinimn ranjinimn merged commit d6df339 into suse-edge:main Oct 13, 2025
1 check passed
@ranjinimn ranjinimn deleted the ISSUE-829 branch October 13, 2025 15:10
ranjinimn added a commit to ranjinimn/suse-edge.github.io that referenced this pull request Oct 15, 2025
ranjinimn added a commit to ranjinimn/suse-edge.github.io that referenced this pull request Oct 15, 2025
ranjinimn added a commit to ranjinimn/suse-edge.github.io that referenced this pull request Oct 15, 2025
ranjinimn added a commit to ranjinimn/suse-edge.github.io that referenced this pull request Oct 15, 2025
hardys pushed a commit that referenced this pull request Oct 16, 2025
hardys pushed a commit that referenced this pull request Oct 16, 2025
hardys pushed a commit that referenced this pull request Oct 16, 2025
ranjinimn added a commit to ranjinimn/suse-edge.github.io that referenced this pull request Oct 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants