v2.14.0

Release v2.14.0 Rancher General Features and Enhancements Behavior Changes Major Bug Fixes Rancher App (Global UI) Features and Enhancements Major Bug Fixes Rancher CLI Behavior Changes Authentication Features and Enhancements Behavior Changes Major Bug Fixes Cluster Provisioning Features and Enhancements Behavior Changes Major Bug Fixes K3s and RKE2 Provisioning Features and Enhancements Known Issues Backup/Restore Behavior Changes Continuous Delivery (Fleet) Behavior Changes Known Issues Install/Upgrade Notes Changes in Image Artifacts Upgrade Requirements Versions Images Tools Kubernetes Versions for RKE2/K3s Rancher Helm Chart Versions Previous Rancher Behavior Changes Previous Rancher Behavior Changes - Rancher General Previous Rancher Behavior Changes - Rancher App (Global UI) Future Rancher Behavior Changes Retention Policy for Rancher App Charts Long-standing Known Issues Long-standing Known Issues - Cluster Provisioning Long-standing Known Issues - RKE2 Provisioning Long-standing Known Issues - K3s Provisioning Long-standing Known Issues - Rancher App (Global UI) Long-standing Known Issues - EKS Long-standing Known Issues - Authentication Long-standing Known Issues - Rancher Webhook Long-standing Known Issues - Virtualization Management (Harvester) Long-standing Known Issues - Backup/Restore Important If you are using Google OAuth as an authentication provider, upgrading to Rancher v2.14.0 may break authentication, preventing users from logging in. This issue is targeted for a fix in in the upcoming Rancher v2.14.1 release. See #54387 for more details. If you are using Google OAuth as an authentication provider, upgrading to Rancher v2.14.0 may break authentication, preventing users from logging in. This issue is targeted for a fix in in the upcoming Rancher v2.14.1 release. See #54387 for more details. For more information, see #48655. These issues can be corrected by either of two methods: Updating the Relying Party Trust information from federation metadata (Relying Party Trust → Update from Federation Metadata…​). Directly adding the certificate (Relying Party Trust → Properties → Signature tab → Add → Select the certificate). For more information, see #48655. These issues can be corrected by either of two methods: Updating the Relying Party Trust information from federation metadata (Relying Party Trust → Update from Federation Metadata…​). Updating the Relying Party Trust information from federation metadata (Relying Party Trust → Update from Federation Metadata…​).