github-actions[bot]
commented
1 year ago This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 90 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 30 days. Thank you for your contributions.
Request: A document that outlines a Rancher tested/recommended upgrade path for clusters that have Rancher-installed kubernetes. Purpose: 1 "source of truth". A recommended/official upgrade path that the Rancher team has vetted to be able to provide to administrators as the product continues to be adopted by more and more organizations.
Examples of items to include:
If a cluster has Rancher-installed Apps in the System project (grafana cluster monitoring, longhorn, etc) and there are 2 true conditions:
What is recommended upgrade path? if the newest version of the App that's showing to the admin isn't supported on the current version of k8s, will Rancher tell the admin that? will Rancher not show updates that aren't supported in the currently installed k8s version?
Does the administrator need to do any specific actions to prepare a cluster for upgrade from X version to Y version?
Were there any special considerations or abnormalities that the team Rancher team noticed/experienced during their testing of the same upgrade?
Were specific Apps installed in the System Project during the Rancher team's testing? ie officially supported vs unsupported apps. Did all the official Apps succeed through the upgrade without issues? Note any issues experienced for version upgrade.
Benefit: It would be beneficial to answer and document questions like these with a recommended upgrade path. I hope to see Rancher continue to grow. I know many organizations could benefit from an official document like this, and hopefully help avoid an administrator introducing any issues during an upgrade. An official document from Rancher would also allow for easier troubleshooting when administrators experience issues. ie "I followed up to step 4 in the official guide and that is when the error was produced. I have X, Y, and Z Apps installed in my System Project and followed the recommended upgrade path by doing...." when reporting issues during upgrades.