# Version 5.0.X Release Highlights ## Version 5 of Trilio for Kubernetes introduces major new capabilities as follows ## 5.0.4 Bugs Fixed in this release: * **Improved Backup Error Messages**: Clarified error messages in the backup flow to better indicate when a `VolumeSnapshot` is stuck due to a previously in-progress volumeSnapshot. * **Node Affinity Handling**: Fixed an issue where `nodeAffinity` settings were not being correctly applied. * **Target Browser Freeze**: Resolved an issue where the target browser UI appeared unresponsive or stuck. * **ImageStream Annotations**: Fixed a bug affecting backups of resources that contain `imageStream` annotations. * **Backup UI Flicker**: Addressed a UI glitch where failed backups would briefly appear and then disappear. * **Transformation Paths Visibility**: Fixed a UI issue that prevented transformation paths from being displayed properly. Known issues: * Updating the target of the ClusterBackupPlan is not yet supported. * Continuous Restore feature for Virtual Machine's **Encrypted Incremental** backup is not yet supported. * During VM restoration if transformation is provided for removing a network interface or Multus network then it will fail during restore validation part. * Images supporting ppc64le architecture are not available with release 5.0.4. ## 5.0.3 Bugs Fixed in this release: * **Backup Deletion Blocked by Webhook:** Resolved an issue where the T4k webhook was incorrectly preventing backup deletion if dependent backups were in a canceling or canceled state. * **ETCD Load During Upgrade:** Addressed an issue where upgrading to a new T4k version caused excessive load on ETCD. Features added in this release: * **Worker Job Affinity Support:** Introduced support for specifying affinity rules for worker jobs. This is distinct from the control plane affinity configuration. * **Sparse File Support:** Added support for backing up and restoring sparse files. * **BackupPlan Target Update:** Enabled the ability to update the target of a BackupPlan. Known issues: * Updating the target of the ClusterBackupPlan is not yet supported. * Continuous Restore feature for Virtual Machine's **Encrypted Incremental** backup is not yet supported. * During VM restoration if transformation is provided for removing a network interface or Multus network then it will fail during restore validation part. * Images supporting ppc64le architecture are not available with release 5.0.3. ## 5.0.2 Bugs Fixed in this release: * **Resource Cleanup Fix**: Resolved an issue in the resource cleaner code to properly clean up orphaned resources. * **CronJob Scheduling Fix**: Fixed a bug that caused CronJob scheduling failures due to insufficient command arguments. Additionally, ensured user-defined affinity settings are correctly applied in CronJob configurations. * **Object Store Target Creation**: Addressed a failure in object store target creation within the OCP plugin. * **Secrets Access Issue**: Fixed an issue where the Secrets box would become unresponsive if the user lacked read access to secrets across all namespaces in the OCP plugin. * **Pause Schedule Handling**: Resolved a bug where a CronJob would trigger immediately after `pauseSchedule` was set to `false` in `BackupPlans` and `ClusterBackupPlans`. * **VolumeSnapshot Readiness Check**: Improved the robustness of the VolumeSnapshot and VolumeSnapshotContent readiness check during Backup Snapshot process. * **Image Backup Parsing**: Fixed an issue with image backup parsing to ensure smoother processing. * **T4k Upgrade Process**: Resolved a migration issue where `BackupPlans` and `ClusterBackupPlans` failed during an upgrade from an older version. * **Non-CSI Storage Support**: Fixed a bug where `DataSnapshot` and `DataUpload` operations were incorrectly processed for non-CSI-based storage. These operations are now skipped as intended. * **IPv6 Compatibility**: Addressed failures in `Backups` and `Restores` caused by IPv6-related issues. * **Vendor Token Expiry Handling**: Improved session management for expired vendor tokens. Instead of a blank screen, users will now experience a proper session logout. * **Helm Release Panic Fix**: Resolved an issue where an empty Helm release within a Helm secret could cause an application panic. Known issues: * Continuous Restore feature for Virtual Machine's **Encrypted Incremental** backup is not yet supported. * During VM restoration if transformation is provided for removing a network interface or Multus network then it will fail during restore validation part. ## 5.0.1 Bugs fixed in this release: * Fixed the issue where volumeSnapshots were not getting cleaned up in the backup process. Known issues: * Continuous Restore feature for Virtual Machine's **Encrypted Incremental** backup is not yet supported. * During VM restoration if transformation is provided for removing a network interface or Multus network then it will fail during restore validation part. ## 5.0.0 Features added in this release: * Added support for Pausing the Backups/ClusterBackups schedules. * Added support to cancel the Backups/ClusterBackups. * Added support to include the specific resource while performing restore. * Improved the speed for VM/Block device incremental backups. * Added support for [Snapshot](/kubernetes/5.0.x/about-trilio-for-kubernetes/features-and-use-cases.md#snapshots). With this, content of the Persistent Volume will be kept in the cluster as a part of VolumeSnapshot. In this feature, only the application resources will be uploaded to target. * Added support for routing with sub-path in the UI. * UI enhancements. Bugs fixed in this release: * Fixed the issue where backupPlan and clusterBackupPlan status was getting populated with many sync messages. * Fixed the VM backup support to include the instance types and preferences. * Fixed the cronjob naming issue where invalid name was getting generated. * Fixed the operator ID validation as a part of BackupPlan creation. * Dependent resources are getting excluded now if parent resource is excluded as a part of Backup or Restore operation. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.trilio.io/kubernetes/5.0.x/about-trilio-for-kubernetes/release-notes.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.