No new features as part of this release.
OCP dynamic forms - inability to enter certain mandatory fields. All mandatory fields are supported now.
Restore by location from Target Browser not loading metadata for transformations and exclusions.
OLM Based Upgrade/Install
Clustered
The v2.0.1
version will be automatically upgraded to v2.0.2
via OLM if the subscription is set to automatic. If not, manually approve the subscription upgrade.
v1.1.1 or v2.0.0
to v2.0.2
- either incrementally upgrade to the next version up till to 2.0.2 or uninstall the current operator and reinstall the 2.0.2 operator from OperatorHub.
Namespaced
Install - Use a custom catalog source to install TVK at a namespace scope.
Upgrade - Uninstall current operator and install the 2.0.2 operator via custom catalog source.
Clustered <-> namespaces
Same as before - full reinstall
In 2.1.0 (late March) all clustered installations would have to go through full reinstalls as namespace to cluster and vice-versa upgrades will be supported.
Multi-namespace backup in the same workflow not supported yet.
Custom certificates for on-premise S3 targets not supported.
MinIO targets are not supported as MinIO does not support empty folders.
Management Console:
Namespace and application toggle for changing monitoring.
Filters added for backup view on landing page under monitoring panel
Filters available for backup overview page
Status log with information specific to each PV is available.
Delete backup and delete restore in place from backup tab under monitoring panel on landing page
Consolidated views for backup/restore summary and overview pages will be part of upcoming release
Reusable resources view added to manage backupPlans, retention policies, targets and hooks.
Validation and checks for all workflows added.
Help screens for landing page and Backup/Restore Overview pages added.
Backend:
Ability to set/configure resources configurations for Trilio Pods.
UI related multiple bugs resolved related to user experience and cosmetics.
Post-hook being triggered after upload is fixed.
OLM Based Upgrade/Install
Clustered
The v2.0.0
version will not be automatically upgraded to v2.0.1
if the auto publish is enabled as the images for 2.0.0 were being served from the namespace channel. The channel will have to be changed back to cluster to receive the update. A video has been provided on the Upgrade page that demonstrates the process
Clustered <-> namespaces
Same as before - full reinstall
In 2.1.0 all clustered installations would have to go through full reinstalls as namespace to cluster and vice-versa upgrades will be supported.
Multi-namespace backup in the same workflow not supported yet.
Custom certificates for on-premise S3 targets not supported.
MinIO targets are not supported as MinIO does not support empty folders.
TrilioVault for Kubernetes Management Console
Namespace Level Backups
Restore Enhancements
Transformation
Exclusions
PatchCRD
Skip Operator Resources
Omit Metadata
Restore Hooks
Target Browser
Support for Helm Charts with sub-charts for helm based backup.
Metadata for Helm resources now available in Status sub-resource
OLM Based Upgrade
Upgrading from 1.x -> 2.0
Namespace install -> Namespace install
User will have to use custom catalog source for upgrade
Uninstall current Operator
Reinstall Operator via Catalog Source
Clustered install -> Clustered install
Instead of using upgrade mechanism via OLM, do the following:
Uninstall current operator
Reinstall 2.0 from OperatorHub
Clustered <-> namespaces
Same as before - full reinstall
In 2.1.0 (End of January) all clustered installations would have to go through full reinstalls as namespace to cluster and vice-versa upgrades will be supported.
Custom certificates for on-premise S3 targets not supported.
MinIO targets are not supported as MinIO does not support empty folders.
No new features.
Licensing bug fixed where Master nodes were being counted for licensing.
Unable to update cron schedule in a BackupPlan.
Same as 1.1.0
Sub-charts in case of helm backup not supported.
Custom certificates for on-premise S3 targets not supported.
Metadata information for Helm apps not supported.
Dynamic Forms in OCP should not be used for TVK administration as the forms feature is still under development and does not provide the level of nesting needed by TVK CRDs.
CRDs not deleted when uninstalling - OpenShift does not delete CRDs as part of Operator uninstall. Since TVK supports namespace and clustered installation, this may cause unexpected behavior with the application. Customers must ensure that the CRDs are deleted after Operator uninstall.
Migration capability from 1.0.0 and v1alpha1 versions.
Customers using Kubernetes lower than v1.15 must enable the CustomResourceWebhookConversion
feature gate on the cluster
Restore By Location
Snapshot issue where backups were getting stuck at 6%
Sub-charts in case of helm backup not supported.
Custom certificates for on-premise S3 targets not supported.
Metadata information for Helm apps not supported.
Dynamic Forms in OCP should not be used for TVK administration as the forms feature is still under development and does not provide the level of nesting needed by TVK CRDs.
CRDs not deleted when uninstalling - OpenShift does not delete CRDs as part of Operator uninstall. Since TVK supports namespace and clustered installation, this may cause unexpected behavior with the application. Customers must ensure that the CRDs are deleted after Operator uninstall.
IBM CloudPak Certified
IBM MultiCloud Management Certified
Migrated from v1alpha1 to v1 API version
Licensing Enabled.
Label Backup - ability to provide multiple label selectors where the corresponding logic is ORR’ed instead of AND’ed
Upstream Operator Backup - Support for Multiple CRDs
Added support for pre-backup validations
Upstream Operator Backup - Ability to select Operator resources by providing helm release name
Backup Metadata information - Ability to view metadata information of a backup in terms of objects/resources captured.
Grafana Dashboards - 10 Grafana dashboards that are pivoted on Backups/Restores/Targets/Applications (BackupPlans) that provide an overview, summary, and details around TVK resources.
NFS Timeout issue - Issue with NFS target creation where mount validation would fail due to a timing issue.
Backup by Labels - Backup only top-level items as nested items were being double-counted in the restore, causing it to fail.
Restore by location not supported.
Upgrades are not supported directly and will be supported as a patch before the next released version.
Sub-charts in case of helm backup not supported.
Custom certificates for on-premise S3 targets not supported.
Metadata information for Helm apps not supported.
Dynamic Forms in OCP should not be used for TVK administration as the forms feature is still under development and does not provide the level of nesting needed by TVK CRDs.
CRDs not deleted when uninstalling - OpenShift does not delete CRDs as part of Operator uninstall. Since TVK supports namespace and clustered installation, this may cause unexpected behavior with the application. Customers must ensure that the CRDs are deleted after Operator uninstall.
Issues post uninstall:
MutatingWebhookConfiguration and ValidatingWebhookConfiguration is not cleaned up
The Cleaner cronjob is not cleaned up.
Cleaner cronjob will fail to create jobs due to RBAC revocation
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
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
OCP UI forms should not be used for resource creation. Instead, the YAML/JSON editor should be used
Listing CRD resources don’t show correct status on OCP UI for operator details
OLM does not consider the scope of CRD it is installing.
Problem: In case TrilioVault 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