Caleb Warren

High Level Test Plan: * deploy windows cluster via vsphere node driver, then update the cluster * deploy rancher 2.8.0 with windows downstream cluster -> upgrade to latest rancher version...

tested on v2.8.3-rc5, I was still able to reproduce this issue. It appears that when the node is rebooted, the DNS name in vsphere is reset. This likely has something...

p.s. the request changes is just to block the PR til shepherd in go mod is fixed as a preventative measure

tested as part of regression tests in rancher, tracked in Qase. All tests are passing on 2.7.11-alpha3

tested as part of regression tests in rancher, tracked in Qase. All tests are passing on 2.7.11-alpha3. Leaving open since this is a release-note item

tested as part of regression tests in rancher, tracked in Qase. All tests are passing on 2.7.11-alpha3

Getting this error when trying to install rancher on 1.27: ``` chart requires kubeVersion: < 1.27.0-0 which is incompatible with Kubernetes v1.27.9+rke2r1\n' ``` using the registry version of rancher for...

New issue - prime is not enabled by default

awaiting testing now that rc3 has been cut

tested and tracked in Qase - working on 2.7.11-rc3