We are excited to announce that Trident 19.10 has been released and is now available for download. We integrated the Container Storage Interface (CSI) specification earlier this year to stay in lockstep with the community and Trident 19.10 continues to build upon that vision and commitment.
In Trident 19.10, we have introduced some really cool features that you have been looking forward to for some time. These new features include:
- A SAN economy driver for ONTAP which is analogous to the NAS Economy driver, but for iSCSI
- Resizing iSCSI Persistent Volumes
- Support for Cloud Volumes Service for Google Cloud Platform
We will briefly discuss these features in the following sections.
SAN Economy Driver
The “ontap-san-economy” driver has been introduced in Trident version 19.10. The economy drivers for NAS and SAN are designed to provide better scalability for Persistent Volumes (PVs), which means we allow the creation of a greater number of PVs, beyond the limits of FlexVol. The ontap-nas-economy driver creates PVs as ONTAP Qtrees, while the ontap-san-economy driver creates PVs as ONTAP LUNs. They are created within a pool of automatically managed FlexVols. The ontap-san-economy driver supports Kubernetes VolumeSnapshots and PVC Clones from VolumeSnapshots.
Configuring a backend for ontap-san-economy is easy. For details, please see the ONTAP driver documentation under the “Backend Configuration” section.
iSCSI Persistent Volume Resize
iSCSI volume resize is operational with Trident in the CSI mode and Kubernetes version 1.16 or greater. Resizing iSCSI PVs can be done the same way as NAS volume resize introduced earlier this year. To resize, just edit the PersistentVolumeClaim to which the PersistentVolume is bound and set the spec.resources.requests.storage parameter to the desired size. Please note, in order to resize, the StorageClass allowVolumeExpansion parameter must be set to true.
Once the PVC is updated, Trident handles everything behind-the-scenes after that. Trident will resize the volume on the storage, extends the filesystem, rescans the device and performs reattach. If there are any resource limits in play in Kubernetes, Trident, or in the storage platform itself, those are honored as well as, just as they were when the volume was originally provisioned. For the iSCSI PV resize to take effect, it must be attached to a pod. ontap-san-economy supports resize of iSCSI PVs for ONTAP, Element and E-Series backends.
For more information, head over to “Managing Volumes” in Trident documentation.
Cloud Volumes Service for GCP
Using Trident, you can now provision PVs in NetApp Cloud Volume Service (CVS) for Google Cloud! The CVS GCP service from NetApp helps customers get a fully managed, cloud-native file storage service for their high-performance enterprise workloads. They are also ideal for lift & shift of workloads like file services, analytics, databases, disaster recovery, and DevOps, making it easier to move data back and forth between the cloud and on-premises. NetApp Cloud Volume Services offers rich data management features like snapshotting and cloning. And, Trident’s gcp-cvs driver does its magic to provision PVs for this service.
The gcp-cvs driver also uses virtual storage pools which introduces a level of abstraction between Trident and the backend. This offers administrators greater control over volume placement in the appropriate storage backend as defined in relevant virtual pools parameters.
To get started, head on over to the CVS for GCP documentation under the “Backend Configuration” section.
- Support for Kubernetes 1.16 and OpenShift 4.2.
- Clone PVCs with CSI Volume Cloning
- Support for iSCSI raw block volumes in CSI mode, including multi-attach support
- Various bugfixes and Improvements
For the complete list of enhancements and bug fixes, check out the Release Info.
Try it and let us Know!
Go ahead and download the latest release of Trident and take advantage of all these new features. We are eager to hear your comments and feedback. If you have any questions, comments or requests, you can get in touch with us through our Slack workspace at netapp.io/slack.