It has been a lightning-quick beginning to the new year. As we still wonder where January went (can you believe a month has gone by so quickly?!), the Trident team is pleased to announce our first release for this calendar year. The 20.01 release introduces support for Kubernetes 1.17, among a host of other cool new stuff: 


  1. Beta Volume Snapshots: As the Kubernetes Volume Snapshots API graduates to beta with Kubernetes 1.17, 20.01 now exclusively enables the creation of beta Volume Snapshots for K8s 1.17 and above. Have you been using alpha Snapshots before that you would like to migrate? Take a look at our recommendation here.
  2. Virtual Storage Pools for ONTAP drivers: All ONTAP drivers now support the creation of Virtual Storage Pools. With this addition, Trident’s entire set of backend drivers can have Virtual Storage Pools defined, providing greater control to K8s admins on where and how volumes are grouped and identified. If you haven’t done so, be sure to take a look at our documentation and design guide for how Virtual Storage Pools work. This blog provides a quickstart for defining Virtual Storage Pools for ONTAP backends.
  3. Trident on IPv6: Good news for all the IPv6 users, as Trident can now be used with IPv6 addresses for ONTAP backends. The installer now contains a new flag (--use-ipv6) that instructs Trident to bind to the IPv6 localhost and use IPv6 addresses for the managementLIF and dataLIF parameters. For all you single-stack IPv6 K8s users out there, this is a great way to have Trident talk to the storage cluster over IPv6.
  4. Prometheus Metrics: Thanks to the new set of endpoints exposed for Prometheus, you can now gather insight on how Trident orchestrates storage. There’s a host of information that can be queried through Prometheus, such as the number of backends, volumes, storage classes, API calls, bytes managed and so on.
  5. Airgapped installs, now simpler than ever: The --image-registry switch can now be used to pass a private registry that contains all the required images for Trident. You can download the Trident and CSI sidecar images to your internal registry, then have Trident fetch the images.


You can obtain the 20.01 release here. For a complete list of all the new stuff that’s out with 20.01, be sure to check our Release Notes. Take a look at the Trident documentation to get started today! 

If you haven’t heard about it before, our Slack workspace is the place to be for all things Trident. Be sure to head on over to the #containers channel for more great stuff! 

About 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