The world continues to come to grips with the Coronavirus and people are indefinitely stuck at home. Over the past few weeks, we have seen that life goes on. Families are coming together virtually. Societies are constantly reinventing to improvise and make sure daily routines continue. It is inspiring to see the warrior within each of us as we work hard to overcome obstacles and persevere against all odds.
It is no different for the Trident team. We have been working hard on the 20.04 release, which is now available and provides a host of new features and enhancements:
You’ve been asking and we’re happy to deliver! The Trident Operator is finally here. With it, you can now declaratively install Trident and have the operator take care of the Trident installation for you. Using the operator to manage Trident will address issues that may be encountered, such as an interrupted install run or accidental deletion of Trident objects. Automating Trident installs, handling upgrades to Kubernetes versions and updating Trident to match the Kubernetes release will be addressed by the operator. Creating backends and querying Trident for information will still require
tridentctl. Over time, the goal for the operator is to extend its scope and control operations that are achieved through
tridentctl today. The inaugural release of this operator targets fresh installations. If you are looking to upgrade to 20.04, you can do so with
tridentctl. Remember to take a look at the documentation to understand what the operator has to offer. Future releases will continue to build on the operator framework that 20.04 provides.
Bidirectional CHAP support for ONTAP
ontap-san-economy drivers are now equipped to automatically configure CHAP when a backend is created. As part of the backend definition, users can now pass
useCHAP=true and provide the client and target username and secrets per backend. Trident uses the information provided to configure CHAP on the SVM and use CHAP as the default authentication method for iSCSI connections. CHAP secrets can also be rotated with a backend update using
tridentctl update backend. Here is how you can define backends and understand how it works.
Automatic export policy creation and management
Trident can create export policies per backend and define export rules for the nodes in the cluster. The backend takes 2 new parameters:
autoExportCIDRs. The storage admin defines a set of CIDR blocks that Trident checks node IPs against to set up an export policy. This export policy will consist of rules per worker node and the export policy is named
trident-<backend-UUID>. When nodes are added or removed from the cluster, Trident automatically updates the rules in the export policy. The documentation explains how this works.
That’s not all. For the complete list of bug fixes and enhancements, be sure to check the release notes.