Known issues
Known issues identify problems that might prevent you from using this release of the product successfully.
The following known issues affect the current release:
Volumes remain attached after upgrading from Trident 22.10 or earlier
This issue affects customers who upgrade directly from Trident 22.10 or earlier to Trident 26.10 while volumes are attached. Upgrades from Trident 23.01 or later are not affected.
After the upgrade, affected volumes might not detach. Pods using ReadWriteOnce (RWO) volumes cannot move to another node and might report a multi-attach error. Deleting the PersistentVolume (PV) might also hang.
To work around this issue, on the node that has the stale volume attachment, delete the leftover volumePublishInfo.json file from that volume's globalmount directory.
VolumeSnapshots not reaching ReadyToUse state
|
|
There is a known issue with the |
Two workarounds are available:
-
Delete the VolumeGroupSnapshots CRDs to disable VolumeGroupSnapshots, and then reinstall Trident.
-
Install VolumeGroupSnapshots
v1beta2andsnapshot-controllerversion 8.4.0 or later, and then reinstall Trident. VolumeGroupSnapshots do not function on Kubernetes versions earlier than v1.34.
Restoring Restic backups of large files can fail
When restoring 30GB or larger files from an Amazon S3 backup that was made using Restic, the restore operation can fail. As a workaround, back up the data using Kopia as the data mover (Kopia is the default data mover for backups). Refer to Protect applications using Trident Protect for instructions.