Version 4.0.X Release Highlights

4.0.5

Bugs fixed in this release:

• Fixed an issue where Coalescing state backups were going to Failed state after Control plane restart.

• Fixed the issue with OLM application restore sequence where custom resources were getting restored before persistentVolumeClaims.

• Fixed the Dex service account issue.

• Added a fix to avoid putting the backups in Coalescing state if both backups marked for retention are Full backups.

4.0.4

Bugs fixed in this release:

• Fixed an issue where clusterBackupPlan was getting stuck in InProgress state because of namespace deletion that was part of clusterBackupPlan.

• Fixed an issue in resource cleaner cronjob causing backups to fail intermittently.

• Target credential secret update operation is allowed now. User can change the credentials and expired certificates.

• Fixed the intermittent backup failures caused by image backup issues.

4.0.3

Bugs fixed in this release:

• Fixed the issue where backups were getting stuck in coalescing state.

• Fixed an issue where data upload part of a backup sometimes failed with storage capacity errors.

• Fixes to continuous restore where the continuous restore service and target watcher stopped working because of a communication issue.

4.0.2

Bugs fixed in this release:

• Fixed the Dex login issue where redirection was failing from http to https

• Removed the compulsion of ipv6 configuration for T4k web server.

• Fixed the issue where backup scheduler was not triggering backups as per the given schedules.

• Fixed the PVC name transformation issue while performing restore.

4.0.1

Features added:

• Added support for IBM Power PC. With this support, T4K can run with PPC64LE architecture.

Bugs fixed in this release:

• Fixed an issue where backups were failing for multiple revision helm charts in namespaced backup with Retain Helm Application flag set to true.

• Fixed an issue where Event target was not usable as backup target. With the fix, user can use the event target as a backup target as well.

Known issues:

• Openshift dynamic plugin is not supported for IBM power PC deployments.

Version 4 of Trilio for Kubernets introduces major new capabilities as follows :

4.0.0

• Red Hat OpenShift: Support for natively backing up and restoring the OLM operators and maintaining their lifecycle post the restore.

• Trilio for Kubernetes resource manager configuration is now available through UI.

• Red Hat OpenShift: Added support for RHOCP Console to include the Trilio UI functionality:

  • NS scoped backup.

  • NS scoped restore.

  • Manage Hooks, targets, policies management.

• Security improvement: Trilio now runs all the operations/jobs in the namespace where T4K is installed allowing administrators to control any privileges and access.

• Added Continuous Restore support for virtual machines running on KubeVirt and OpenShift Virtualization to reduce time during disaster recovery.