Upgrade table/matrix to clarify the upgrade procedures

[e-minguez]

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.

cc @hardys

@ranjinimn is this something you can take care of?

[ranjinimn]

@e-minguez I can work on this. Is this all the information that you want to include in the matrix? Any specific section where this needs to be included? Would https://documentation.suse.com/suse-edge/3.3/single-html/edge/#day-2-operations be okay?

[e-minguez]

@e-minguez I can work on this. Is this all the information that you want to include in the matrix?

I think so, what do you think?

Any specific section where this needs to be included? Would https://documentation.suse.com/suse-edge/3.3/single-html/edge/#day-2-operations be okay?

Yes.

[ranjinimn]

@e-minguez I was wondering if we can cross reference the respective sections which details the steps provided for upgrade. For example, you mention the Fleet approach, can we just provide the link to that section which mentions about upgrading using Fleet?

[e-minguez]

@e-minguez I was wondering if we can cross reference the respective sections which details the steps provided for upgrade. For example, you mention the Fleet approach, can we just provide the link to that section which mentions about upgrading using Fleet?

That would be nice.

[e-minguez]

After #859 I guess we can close this one? Or are we expecting to close it after the backports? /cc @ranjinimn

[ranjinimn]

Yes @e-minguez After the backport, I would like to close this.