1.0.X-1.1.X(Deprecated)

Release Notes

A list of known issues and limitations with the current release are provided within this section.

Deprecated Documentation

This document is deprecated and no longer supported. For accurate, up-to-date information, please refer to the documentation for the latest version of Trilio.

Release Notes

1.1.1

What's New

  1. No new features.

Bugs Fixed

  1. Licensing bug fixed where Master nodes were being counted for licensing.

  2. Unable to update cron schedule in a BackupPlan.

Known Issues/Limitations

Same as 1.1.0

  1. Sub-charts in case of helm backup not supported.

  2. Custom certificates for on-premise S3 targets not supported.

  3. Metadata information for Helm apps not supported.

  4. Dynamic Forms in OCP should not be used for T4K administration as the forms feature is still under development and does not provide the level of nesting needed by T4K CRDs.

  5. CRDs not deleted when uninstalling - OpenShift does not delete CRDs as part of Operator uninstall. Since T4K supports namespace and clustered installation, this may cause unexpected behavior with the application. Customers must ensure that the CRDs are deleted after Operator uninstall.

  6. Update 11/01 - Due to an internal error by RedHat converting Trilio CRDs, the namespace installation is facing issues currently when being installed via OLM. Please use clustered install or Helm charts (instead of OLM) to install Trilio for Kubernetes

1.1.0

What's New

  1. Migration capability from 1.0.0 and v1alpha1 versions.

    1. Customers using Kubernetes lower than v1.15 must enable the CustomResourceWebhookConversion feature gate on the cluster

  2. Restore By Location

Bugs Fixed

  1. Snapshot issue where backups were getting stuck at 6%

Known Issues/Limitations

  1. Sub-charts in case of helm backup not supported.

  2. Custom certificates for on-premise S3 targets not supported.

  3. Metadata information for Helm apps not supported.

  4. Dynamic Forms in OCP should not be used for T4K administration as the forms feature is still under development and does not provide the level of nesting needed by T4K CRDs.

  5. CRDs not deleted when uninstalling - OpenShift does not delete CRDs as part of Operator uninstall. Since T4K supports namespace and clustered installation, this may cause unexpected behavior with the application. Customers must ensure that the CRDs are deleted after Operator uninstall.

1.0.0

What’s New:

  1. IBM CloudPak Certified

  2. IBM MultiCloud Management Certified

  3. Migrated from v1alpha1 to v1 API version

  4. Licensing Enabled.

  5. Label Backup - ability to provide multiple label selectors where the corresponding logic is ORR’ed instead of AND’ed

  6. Upstream Operator Backup - Support for Multiple CRDs

  7. Added support for pre-backup validations

  8. Upstream Operator Backup - Ability to select Operator resources by providing helm release name

  9. Backup Metadata information - Ability to view metadata information of a backup in terms of objects/resources captured.

  10. Grafana Dashboards - 10 Grafana dashboards that are pivoted on Backups/Restores/Targets/Applications (BackupPlans) that provide an overview, summary, and details around T4K resources.

Bugs Fixed:

  1. NFS Timeout issue - Issue with NFS target creation where mount validation would fail due to a timing issue.

  2. Backup by Labels - Backup only top-level items as nested items were being double-counted in the restore, causing it to fail.

Known Issues/Limitations:

  1. Restore by location not supported.

  2. Upgrades are not supported directly and will be supported as a patch before the next released version.

  3. Sub-charts in case of helm backup not supported.

  4. Custom certificates for on-premise S3 targets not supported.

  5. Metadata information for Helm apps not supported.

  6. Dynamic Forms in OCP should not be used for T4K administration as the forms feature is still under development and does not provide the level of nesting needed by T4K CRDs.

  7. CRDs not deleted when uninstalling - OpenShift does not delete CRDs as part of Operator uninstall. Since T4K supports namespace and clustered installation, this may cause unexpected behavior with the application. Customers must ensure that the CRDs are deleted after Operator uninstall.

0.2.3 - 0.2.5

  1. Issues post uninstall:

    1. MutatingWebhookConfiguration and ValidatingWebhookConfiguration is not cleaned up

    2. The Cleaner cronjob is not cleaned up.

    3. Cleaner cronjob will fail to create jobs due to RBAC revocation

    4. In case of scheduled backups defined for any BackupPlan, the cronjob for the same will not be cleaned up unless the BackupPlan is deleted. This will lead to failed jobs due to RBAC revocation Helm charts with sub-charts are not yet supported

  2. In case there is a problem with Target after it is created (change in IP, removal of keys in use), it won’t change the state of Target and will still show Available

  3. OCP UI forms should not be used for resource creation. Instead, the YAML/JSON editor should be used

  4. Listing CRD resources don’t show correct status on OCP UI for operator details

  5. OLM does not consider the scope of CRD it is installing.

    1. Problem: In case Trilio is installed in cluster scope and then deleted and after then if the user tries to install in namespaced scope, OLM allows it. On operator deletion, CRD’s are not deleted. So even when the user did the namespaced installation, the underlying CRD’s are installed in cluster scope, leading to issues with application functioning

PreviousPrefaceNextIntroduction

Last updated