Update release documentation with additional steps #1738
Conversation
| #### Checks required from Distro's First Mates | ||
|
|
||
| + Confirm that the correct versions for the latest monthly rke2/k3s release have been properly ported to all dev branches which will be released. | ||
| + Confirm that the `appDefaults` ranges listed in `channels.yaml` and `channels-rke2.yaml` match the expected Kubernetes release version range for the new Rancher minor version. |
There was a problem hiding this comment.
Thanks for updating the checklist! 🎉
appDefaults and min/max ChannelServerVersion have different purposes:
-
appDefaultsis only there to indicate the default k8s version for rancher server version. Rancher server version range is set byappVersionand the intended default k8s version is set bydefaultVersion. For example, if a new release of Rancher v2.12.0 is being released, we need to have the upper bound of theappVersionto at least< v2.12.100-0for the intended default k8s version (defaultVersion: v1.33.x). Updating other k8s versions isn't required. -
The actual decision of whether the k8s version will be available for a particular rancher server is decided by
releasessection which hasmin/maxChannelServerVersionand must be updated for all supported k8s versions.
2 participants
Small updates to the release docs based off of the 2.12 KDM release