In addition, when users roll back Rancher on the same cluster using the Rancher Backup and Restore app in 2.6.4+, the updated steps to create the Restore Custom Resource must be followed. This script can be found in the rancherlabs/support-tools repo and the usage of the script can be found in the backup-restore operator docs. To avoid this, the Rancher resource cleanup script should be run before the restore or rollback is attempted. This has the effect of causing rollbacks from Rancher v2.6.4 to any previous version of Rancher v2.6.x to fail because the previous version the CRDs needed to roll back are no longer available in v1beta1. In Rancher v2.6.4, the cluster-api module has been upgraded from v0.4.4 to v1.0.2 in which the apiVersion of CAPI CRDs are upgraded from /v1alpha4 to /v1beta1. It is important to review the Install/Upgrade Notes below before upgrading to any Rancher version. Please use containerd-based images instead.

Provisioning K8s 1.23+ GKE clusters with the default option of “Container-Optimized OS with Docker” for “Image Type” fails due to GKE no longer supporting Docker-based images per GKE documentation.Cluster could be a fresh installation or upgraded to v1.24.x. High CPU usage is observed on RKE1 v1.24.x clusters.This causes issues with RKE1 cluster upgrades if user addons template has cattle-* or other system namespaces. RKE v1.3.10-v1.3.13 in Rancher v2.6.7-v2.6.8 removes user addons during an upgrade before redeploying them.Fixed an issue in which custom branding, color, and theme in Rancher Manager v2.6.7 was not correctly applied in the UI.Update to v2.6.8 or later to prevent potential data loss.

Note that this data loss only affects applications deployed through Fleet, including Longhorn. Fleet bundle pruning was too aggressive when GitJobs had multiple paths.Rancher v2.6.8 is a mirror release of v2.6.7 to address the following issues: Major Bug Fixes

Starus File Recovery 6.8 download