2022 is here! According to the Chinese zodiac, this year will be the year of the Tiger. “The Year of the Tiger will be about making big changes. This will be a year of risk-taking and adventure. We’re finding enthusiasm again, both for ourselves and for others. Everyone is fired up; generosity is at an all-time high and social progress feels possible again”. With only a month into 2022, here’s to hoping it all rings true!


As always, the end of January marks the delivery of the first Astra Trident release of this calendar year. Astra Trident v22.01 is now GA and is the 49th release to date. Here is the rundown of everything you can expect to see:


Deploy Trident better with NodeSelectors and Tolerations: v22.01 allows you to selectively deploy Trident on a subset of nodes in a Kubernetes cluster using NodeSelectors and Tolerations. This is supported while deploying Trident using either the operator or the Helm chart. This will allow you to restrict Trident deployments to a desired set of nodes in clusters that:

  • Contain mixed nodes, such as nodes with different capabilities (OS image, hardware add-ons).
  • Require Trident to run only on a specific set of nodes for business or security reasons, instead of all nodes in the cluster.


When deploying Trident using the operator, you can choose where the controller runs, as well as the nodes on which the daemonset is allowed to run. The operator and the Helm chart provide four new parameters to customize Trident installs.


Configure “unixPermissions” for Azure NetApp Files (ANF): A preview feature for ANF, v22.01 allows backend configurations to provide default UNIX permissions on the Azure NetApp Files (ANF) volumes created on it. Remember we did this back in the previous release (v21.10) for the gcp-cvs storage driver. For applications that need to define the ownership of files on their ANF volumes (and not achieve it through securityContexts alone), this is exactly what the doctor ordered.


Cross-region access of GCP-CVS volumes: Rejoice Google Cloud users, you can now access GCP-CVS volumes from clients in a different region. This marks a change from previous versions, which required CVS volumes to be provisioned and used (by Kubernetes clients) in the same Google Cloud region. It is important to note that with cross-region access comes cross-region egress costs.


Improvements to the azure-netapp-files driver: Updates to the azure-netapp-files driver in this release include:

  • Restricting operations such as resource discovery to a single “location” in Azure. This implies that each backend must now provide the “location” it is to be used in. If you are looking to upgrade to v22.01, do not forget to update backends and provide a “location”.
  • Detection of distinct resources that share the same name.


Better handling of large (500+ nodes) K8s clusters – Node registrations will now take advantage of a newly introduced exponential backoff based retry logic.


Additional Notes:

  • Kubernetes v1.23 is now supported.
  • The aws-cvs driver is marked for deprecation and will be removed in a future release.


For a complete list, here is the GitHub CHANGELOG. Get started today by heading over to our repository and giving it a go.


Join us on Slack today for a more involved experience! The #containers channel is home to Kubernetes conversations and more.

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