No actual documentation behind link to upstream docs

[timirnich]

suse-edge.github.io/asciidoc/day2/downstream-cluster-k8s.adoc

Line 30 in 782271d

For more information regarding how the `rke2-upgrade` image performs the upgrade, see the link:https://github.com/rancher/rke2-upgrade/tree/master[upstream] documentation.

The link points to the GitHub repo for the upstream docs, which does not contain any actual documentation for the upgrade process. We should probably point to https://docs.rke2.io/upgrade/automated_upgrade instead.

[hardys]

Thanks @timirnich the main issue is https://docs.rke2.io/upgrade/automated_upgrade seems to mostly talk about SUC - and it links to the exact same upstream GH repos so I'm not sure replacing the link will make things clearer 🤔

@ipetrov117 what are your thoughts?

[ipetrov117]

My 2 cents.. IMO the https://docs.rke2.io/upgrade/automated_upgrade documentation does not offer much additional information and might cause confusion. Mainly because there they have a whole section explaining how to install SUC and configure its RKE2 plans which is in contradiction with the installation/configuration process that we want to suggest to our users. That is the main reason why we are not pointing to this documentation.

That said, if we want to point to this documentation instead, I am not opposed to it. I am a bit worried that it might mislead users to thinking that it is okay to install SUC from the upstream repo instead of the Rancher charts. Same concern is valid for the SUC Plans in the automated_upgrade documentation, I am worried that users might think that it is okay to use them instead.