[v2.7] KDM Update for K8s March patch release about rancher HOT 1 CLOSED

Fresh install checks - PASS

• On rancher version v2.7.12, KDM pointing to dev-v2.7-2024-03-patches branch, cluster creation succeeds for v1.26.15-rancher1-1 and v1.27.12-rancher1-1 on all network providers - canal/flannel/weave/calico
• Network checks look good
• Canal network checks look good

Upgrade checks - PASS

• On rancher v2.7.12, KDM pointing to release-v2.7, cluster creation succeeds for k8s v1.26.14-rancher1-1 and v1.27.11-rancher1-1 versions with all network providers.
• Pre-upgrade checks look good.
• Pointed the KDM branch to dev-v2.7-2024-03-patches.
• Upgraded cluster to k8s versions - v1.26.15-rancher1-1 and v1.27.12-rancher1-1.
• Post upgrade checks look good.

Minimum rancher version checks - PASS

• On rancher v2.7.11 with KDM pointing to dev-v2.7-2023-11-patches branch, cluster creation succeeds for v1.27.12-rancher1-1 versions with all network providers.
• Network checks look good.

Minimum rancher version checks - PASS

• On rancher v2.7.5 with KDM pointing to dev-v2.7-2023-11-patches branch, cluster creation succeeds for v1.26.15-rancher1-1 versions with all network providers.
• Network checks look good.

RKE default k8s version - PASS

dev-v2.7-2024-03-patches should have the default as v1.27.12-rancher1-1

 "RKEDefaultK8sVersions": {
  "0.3": "v1.16.3-rancher1-1",
  "default": "v1.27.12-rancher1-1"
 },

RKE Checks passed with rke v1.4.17-rc1. Also, checked if images are getting pulled successfully.

• Ran rke config --system-images
• Pulled all the docker images manually.
• Made sure all the images are getting pulled successfully.

RKE checks passed. Hence closing the issue.

from rancher.