With every New year comes a new release! Trident 21.01 is available today, and this marks our 39th release to date. The latest version comes with a host of significant updates to satisfy your fix for new and useful features. Here’s what’s new:

 

Certificate-based authentication for ONTAP backends

You can now authenticate ONTAP backends using self-signed certificates instead of providing username/password credentials for an ONTAP security role in the backend definitions. This feature provides a more secure method of creating backends. The clientPrivateKey, clientCertificate, and trustedCA will be new fields used in the backend definition to authenticate the backend. Keep in mind that if using username/password, they will always be stored as Kubernetes secrets and not in plaintext. For further reading, refer to the ONTAP backend guide.

 

Support for QoS policy groups with ONTAP backends

You can now reference pre-defined adaptive or traditional QoS policy groups for ONTAP Trident backends. This functionality is available for all ONTAP storage drivers, with the ontap-nas-economy driver supporting traditional QoS policy groups only. Using the qosPolicy and adaptiveQosPolicy parameters, it is now possible to point to an existing QoS policy group created on the ONTAP cluster. Depending on the storage driver, the QoS policy group is applied on FlexVols (ontap-nas), the LUN (ontap-san and ontap-san-economy), or the qtree (ontap-nas-economy). There are a few requirements associated with this feature, namely: 

  1. This feature is supported for ONTAP 9.8 and newer.
  2. Backends using the ontap-nas-economy driver must specify traditional QoS policy groups.
  3. Each backend can takes a QoS policy group in the defaults block. If multiple storage pools are defined (see Virtual Storage Pools), each storage pool can have a QoS policy group defined in its defaults block.

Here is an example.

 

Install and manage Trident using Helm

Trident now has its own Helm chart, available today in the Trident repository. This functionality provides an alternate method of deploying and managing Trident if you prefer managing your Kubernetes deployments using Helm. The Helm chart for Trident makes use of the Trident operator and exposes all the configuration options available in the operator enabling you to customize your deployment. The documentation contains a list of parameters that can be used with the Helm chart.

 

Cluster-scoped Trident Operator

The latest version of the Trident operator is cluster-scoped, introducing the TridentOrchestrator CRD to represent Trident installs. A cluster-scoped operator enables Trident to define and handle its resources at the cluster level. This makes it easier to reuse resources (such as ClusterRole, ClusterRoleBinding, and PodSecurityPolicy), auto-heal, and perform a complete clean-up if needed. Existing installations of Trident that were created using the operator will be automatically upgraded; for example, Trident installed using the 20.10 operator can be upgraded to 21.01 using the new cluster-scoped operator.

To understand how installs with the new operator would work, take a look at the documentation here.

 

Minimum supported size of Cloud Volumes Service (CVS)-GCP volumes is 100 GiB

Trident now allows you to create smaller CVS-Performance volumes in GCP, significantly reducing storage costs for your Kubernetes workloads. For all volume requests that are lesser than 100 GiB, Trident will create a 100 GiB CVS-Performance volume. The minimum supported size for CVS Scale Optimized volumes stays unchanged at 1TiB. Click here to view documentation on how to configure Trident for CVS-GCP.

 

Storage Volume Labeling for ONTAP and ElementOS/HCI backends

Adding to the capability introduced in 20.10, storage volume labeling is now available for ONTAP and ElementOS/HCI backends that utilize the ontap-san, ontap-nas,ontap-nas-flexgroup, and solidfire-san drivers. Backend definitions can now take a labels block with multiple key-value pairs to be used as labels. These labels will be appended to each FlexVol/FlexGroup/ElementOS LUN created in the backend (in the “comments” field). This allows storage admins to distinctly identify volumes created by Trident, the backend they belong to, the Kubernetes cluster where the volumes are created from, and other details.

 

Optionally configure the number of LUNs per FlexVol for ONTAP SAN Economy

Similar to qtreesPerFlexvol, backends using the ontap-san-economy driver now support a new configuration option lunsPerFlexvol in their backend definition. By default, each PV corresponds to a LUN created in a pool of managed FlexVols, with a maximum of 200 LUNs per FlexVol. You can now configure this option to be a value between 50 – 200 with a default value of 100.

 

That is not all! There are additional enhancements in store, namely:

  1. Trident v21.01 is compliant with CSI 1.3.
  2. A previously reported issue with numbered storagePrefixes for ONTAP economy drivers has been fixed.
  3. CSI Snapshots is now a feature that is GA with Kubernetes 1.20.

 

For a complete list of fixes, enhancements, and changes, you can look at the release notes here.

 

Questions? Here’s where to ask them

Contact the Trident community on Slack! The #containers channel is the place to hang. 

Bala RameshBabu
Bala is a Technical Marketing Engineer who focuses on Trident, NetApp's dynamic storage provisioner for Kubernetes and Docker. With a background in OpenStack, he focuses on open-source solutions and DevOps workflows. When not at work, you can find him in a soccer field or reading biographies

Pin It on Pinterest