Warn users that upgrades should not skip intermediate minor versions

Signed-off-by: Manuel Buil <[email protected]>

docs/upgrade/automated_upgrade.md

@@ -26,6 +26,9 @@ To automate upgrades in this manner you must:
 1. Install the system-upgrade-controller into your cluster
 2. Configure plans
 
+:::tip
+When attempting to upgrade to a new version of RKE2, the [Kubernetes version skew policy](https://kubernetes.io/docs/setup/release/version-skew-policy/) applies. Ensure that your plan does not skip intermediate minor versions when upgrading. The system-upgrade-controller itself will not protect against unsupported changes to the Kubernetes version.
+:::
 
 ### Install the system-upgrade-controller
 The system-upgrade-controller can be installed as a deployment into your cluster. The deployment requires a service-account, clusterRoleBinding, and a configmap. To install these components, run the following command:

docs/upgrade/manual_upgrade.md

@@ -19,6 +19,11 @@ Upgrades performed via the installation script or using our [automated upgrades]
 
 For an exhaustive and up-to-date list of channels, you can visit the [rke2 channel service API](https://update.rke2.io/v1-release/channels). For more technical details on how channels work, you can see the [channelserver project](https://github.com/rancher/channelserver).
 
+:::tip
+When attempting to upgrade to a new version of RKE2, the [Kubernetes version skew policy](https://kubernetes.io/docs/setup/release/version-skew-policy/) applies. Ensure that your plan does not skip intermediate minor versions when upgrading. Nothing in the upgrade process will protect against unsupported changes to the Kubernetes version.
+:::
+
+
 ### Upgrade rke2 Using the Installation Script
 
 To upgrade rke2 from an older version you can re-run the installation script using the same flags, for example: