v21.04.1

Changes since v21.04.0

Fixes:

• Kubernetes: Switched the node pod liveness/readiness probe port to default to a port in the registered port
  range rather than ephemeral. This port can also now be changed easily during installation (Issue #578).
• Fixed issue where snapshot & tiering policies were not handled correctly by ontap-san-economy driver.

v21.04.0

Changes since v21.01.0

Fixes:

• OpenShift: Fixed issue where the Trident Operator fails to patch ClusterRole and ClusterRoleBinding (Issue #517).
• Fixed a parsing error when iscsiadm listed target portals with a negative group tag (Issue #523).
• Docker: Fixed issue where Docker plugin could not be upgraded from v19.10 to v21.01 (Issue #507).
• Fixed issue where disabled data LIFs are picked up by controller during ControllerPublishVolume (Issue #524).
• Fixed issue where unexpected output in iscsiadm discovery commands may cause target discovery to fail.
• Fixed issue where ontap-san-economy snapshots could not be restored or deleted with storage prefix (Issue #461).
• Kubernetes: Trident in CSI mode now uses a unique igroup for each ONTAP SAN backend (Issue 437).

Enhancements:

• Added support for shared VPC host projects to the GCP CVS driver (Issue #529).
• Added support for smaller (300 GiB) scale-optimized CVS volumes in GCP. Smaller volume support must be enabled in GCP CVS account.
• Added snapshotDir parameter to Azure NetApp Files backend definition.
• Kubernetes: Added recreate strategy in Trident Operator deployment (Issue #508).
• Kubernetes: Added an images sub-command to tridentctl to display the container images required for a Trident installation on a specific Kubernetes version.
• Kubernetes: Added support for Kubernetes 1.21.
• Kubernetes: Added support for Trident backend creation using kubectl (Issue #358).
• Kubernetes: Added startup, liveness and readiness probes for Trident node pods (Issue #436).

v21.01.2

Changes since v21.01.1

• IMPORTANT: CSI sidecars are pulled from k8s.gcr.io/sig-storage when the Kubernetes version is 1.17 or greater, and
  quay.io/k8scsi otherwise. Private registries are still supported and will be used without any
  modification if provided.

Enhancements:

• Added snapshotDir parameter to Azure NetApp Files backend definition.

v21.01.1

Changes since v21.01.0

• IMPORTANT: CSI sidecars are pulled from k8s.gcr.io/sig-storage when the Kubernetes version is 1.17 or greater, and
  quay.io/k8scsi otherwise. Private registries are still supported and will be used without any
  modification if provided.

Fixes:

• OpenShift: Fixed issue where the Trident Operator fails to patch ClusterRole and ClusterRoleBinding (Issue #517).
• Fixed a parsing error when iscsiadm listed target portals with a negative group tag (Issue #523)

v21.01.0

Changes since v20.10.0

KNOWN ISSUE: The Trident Operator that was released as part of v21.01.0, when used with Red Hat OpenShift Container Platform (OCP) 4.x, is unable to apply changes to the Trident deployment after the initial installation/upgrade. Installations that are impacted by this issue will report this error: no kind ‘ClusterRole’ is registered for version ‘authorization.openshift.io/v1\’ in scheme ’k8s.io/kubernetes/pkg/api/legacyscheme/scheme.go:30.

This issue does not affect the normal functioning of Trident, only the Trident Operator. This prevents changes made to the TridentOrchestrator custom resource (CR) after the install/upgrade from taking effect. You can work around this issue by deleting the 'trident-csi' ClusterRole and 'trident-csi' ClusterRoleBinding. The operator will be able to complete the reconcile, make required changes and will also re-create the ClusterRole and ClusterRoleBinding.

All other installation methods, including tridentctl-based installs and Operator/Helm installs on non-OCP distributions are not impacted.

We are actively working on a 21.01.1 hot-fix for this issue, however at this time we ask that if you are using OpenShift Container Platform and the Trident Operator or Helm that you hold off upgrading until we release 21.01.1.

---

• IMPORTANT: CSI sidecars are pulled from k8s.gcr.io/sig-storage when the Kubernetes version is 1.17 or greater, and
  quay.io/k8scsi otherwise. Private registries are still supported and will be used without any
  modification if provided.

Fixes:

• Kubernetes: Fixed issue where the Trident node failed to register with the Trident controller (Issue #468).
• Kubernetes: Fixed issue where CHAP credentials may be logged by CSI sidecars.
• Kubernetes: Fixed issue of Ownership References set by Trident Operator on cluster-scoped Trident resources
  (Issue #474).
• Kubernetes: Fixed issue where the operator could leave a Trident node unregistered with kubelet (Issue #487).
• Kubernetes: Fixed issue Operator reporting Trident installation multiple times (Issue #431).
• Fixed issue where digits in the storage prefix were disallowed from the ONTAP economy drivers (Issue #476).
• Changed iSCSI static discovery to sendtargets
• Fixed E-series intermittent HTTP 422 error on volume creation.
• Kubernetes: Fixed issue where a snapshot transaction could keep Trident from starting (Issue #490).
• Kubernetes: Handle the case where blkid fails to provide any output (Issue #418).

Enhancements:

• Kubernetes: Added support for Kubernetes 1.20
• Kubernetes: Updated CSI sidecars.
• Kubernetes: Updated scope of the Trident Operator to cluster-scope.
• Kubernetes: Added Helm Chart Support
• Updated GCP driver to allow CVS-Performance volumes as small as 100 GiB.
• Added support for ONTAP QoS policy groups (Issue #108)
• Added lunsPerFlexvol option to allow customizing the number of LUNs per FlexVol in the ontap-san-economy driver.
• Allow user to authenticate with certificate and key for ONTAP backends.
• Allow CA certificates for validating ONTAP certificates.
• Set provisioning labels for all volumes for ONTAP-NAS, ONTAP-SAN, ONTAP-NAS-FLEXGROUP, SolidFire, and CVS drivers

v20.10.1

Changes since v20.10.0

• IMPORTANT: If you are upgrading from Trident 19.07 or 19.10 please carefully read this.
• IMPORTANT Trident relies on the trident-autosupport sidecar container to periodically send usage and support telemetry data to NetApp by default. Usage of the trident-autosupport project falls under the NetApp EULA. Automatic sending of this data can be disabled at Trident install time via the "--silence-autosupport" flag.

Fixes:

• Kubernetes: Fixed issue where the Trident node failed to register with the Trident controller (Issue #468).
• Kubernetes: Fixed issue of Ownership References set by Trident Operator on cluster-scoped Trident resources
  (Issue #474).
• Changed iSCSI static discovery to sendtargets
• Fixed E-series intermittent HTTP 422 error on volume creation.

Enhancements:

• Kubernetes: Added support for Kubernetes 1.20
• Kubernetes: Updated CSI sidecars.
• Updated GCP driver to allow CVS-Performance volumes as small as 100 GiB.

v20.10.0

Changes since v20.07.0

• IMPORTANT: If you are upgrading from Trident 19.07 or 19.10 please carefully read this.
• IMPORTANT Trident relies on the trident-autosupport sidecar container to periodically send usage and support telemetry data to NetApp by default. Usage of the trident-autosupport project falls under the NetApp EULA. Automatic sending of this data can be disabled at Trident install time via the "--silence-autosupport" flag.

Fixes:

• Fixed issue of SLM portal login for iSCSI backends (Issue #387).
• Fixed issue where Trident would crash when creating a volume if ONTAP FCP interfaces were present in the target SVM.
• Fixed issue where storage prefix with period would cause backend to fail when updating or creating backend or upgrading Trident from v20.01 (Issue #455).
• Fixed ONTAP SAN drivers to clean up if provisioning fails (Issue #442).
• Kubernetes: Fixed issue that would cause initiators to be removed from the igroup in the ontap-san and ontap-san-economy drivers in non-CSI installations in Kubernetes <= 1.13 (Issue #463).
• Fixed issue where volume resizes may fail when large ONTAP snapshots were present for the FlexVol.
• Kubernetes: Fixed issue where Trident may panic with a concurrent map write (Issue #456).
• Kubernetes: Fixed issue where Trident Operator may create additional service account secrets (Issue #469).
• Kubernetes: Fixed issue where Trident uses old Kubernetes secrets after Operator updates the service account (Issue #444).

Enhancements:

• Kubernetes: Added support for Kubernetes 1.19
• Kubernetes: Updated CSI sidecars to newest major versions.
• Switched to distroless for base-image, reducing size and attack surface.
• Added qtreesPerFlexvol option to allow customizing the number of qtrees per FlexVol in the ontap-nas-economy driver.
• Kubernetes: Added support for WaitForFirstConsumer via CSI-topology (Issue #405).
• Added requestID fields to most log statements to assist in following individual request through Trident.
• Kubernetes Trident can now send its logs to NetApp Autosupport Telemetry.
• Added support for storage volume labels in ANF, AWS, and GCP backends.

Beta Features:
These should not be used in production scenarios and are for testing and preview purposes only.

• Kubernetes: Automatic node preparation for NFS and iSCSI protocols. Trident can now attempt to make sure NFS and/or iSCSI packages and services are installed and running the first time an NFS or iSCSI volume is mounted on a worker node. Can be enabled with --enable-node-prep installation option.
• Added support for the default CVS service type on GCP.

Deprecations:

• Kubernetes: Removed etcd support, including ability to upgrade directly from etcd-based Trident (v19.04.1 or older).

v20.07.1

Changes since v20.07.0

• Known issues: Take a look at the Known issues associated with 20.07.1, specifically with respect to igroup management on Kubernetes 1.11 - 1.13, and enforcing fsGroup for StorageClasses with an empty fsType.
• IMPORTANT: If you are upgrading from Trident 19.07 or 19.10 please carefully read this.
• IMPORTANT Trident relies on the trident-autosupport sidecar container to periodically send usage and support telemetry data to NetApp by default. Usage of the trident-autosupport project falls under the NetApp EULA. Automatic sending of this data can be disabled at Trident install time via the "--silence-autosupport" flag.

Fixes:

• Kubernetes: Redacted sensitive information in Trident logs for CVS drivers.
• Kubernetes: Fix for allowing empty storage prefix. (Issue #430)
• Kubernetes: Fix for Trident Operator's patching of Service Account to avoid unintended creation of secrets.

Enhancements:

• Kubernetes: Added support for Kubernetes 1.19. (Issue #440)
• Kubernetes: Added GoStringer interface for all the drivers to support sensitive information redaction.

v20.07.0

Changes since v20.04.0

• Known issues: Take a look at the Known issues associated with 20.07.0, specifically with respect to igroup management on Kubernetes 1.11 - 1.13
• IMPORTANT: If you are upgrading from Trident 19.07 or 19.10 please carefully read this.
  IMPORTANT Trident relies on the trident-autosupport sidecar container to periodically send usage and support telemetry data to NetApp by default. Usage of the trident-autosupport project falls under the NetApp EULA. Automatic sending of this data can be disabled at Trident install time via the "--silence-autosupport" flag.

Fixes:

• Disabled automatic iSCSI scans and shortened the iSCSI session replacement timeout. (Issue #410)
• Fixed volume cloning in the Azure NetApp Files driver.
• Kubernetes: Fixed an issue where the NFS client could not start rpc-statd.
• Kubernetes: Fixed various usability issues with the Trident Operator. (Issues #409, #389, #399)
• Kubernetes: Fixed an issue with bidirectional iSCSI CHAP authentication. (Issue #404)
• Kubernetes: Set unix permissions correctly during volume import. (Issue #398)
• Kubernetes: Added various checks to improve resiliency of iSCSI volumes. (Issue #418)
• Kubernetes: Enhanced startup logic to reconcile volume access rules with current cluster nodes. (Issues #391, #352)
• Kubernetes: Added storage prefix validation to ONTAP drivers. (Issue #401)
• Kubernetes: Fixed issue where an unmanaged volume prevented the backend from being removed
• Kubernetes: Redacted sensitive information in Trident logs

Enhancements

• Added support for NFS v4.1 volumes to Azure NetApp Files, CVS-AWS, and CVS-GCP drivers. (Issue #334)
• Added cloning to ONTAP FlexGroup driver.
• Kubernetes: Added support for CSI NodeGetVolumeStats endpoint. (Issue #400)
• Kubernetes: Added volume import to ONTAP SAN driver. (Issue #310)
• Kubernetes: Added automatic igroup management to ONTAP SAN and ONTAP SAN Economy drivers.
• Kubernetes: Added more usage and capacity metrics. (Issue #400)
• Kubernetes: Added upgrade support to the Trident Operator.
• Kubernetes: Automatic NetApp autosupport telemetry reporting via trident-autosupport sidecar, disabled via --silence-autosupport option in tridentctl install command

Deprecations:

• Kubernetes: Deprecated all of the 'core' metrics because their names are changing.

v20.04.0

Changes since v20.01.0

IMPORTANT: If you are upgrading from Trident 19.07 or 19.10 please carefully read this.

Fixes:

• Kubernetes: Changed Trident node server to use downward API instead of relying on Kubernetes DNS to find Trident service. (Issue #328)
• Fixed FlexGroup volume deletion with ONTAP version 9.7. (Issue #326)
• Refer to backend storage for current volume size during resize. (Issue #345)
• Fixed a potential hang during iSCSI detach.
• Kubernetes: Fixed volume import for ANF backends.
• Kubernetes: Fixed cloning imported volumes for CVS & ANF backends.
• Kubernetes: Fixed displaying volume sizes in Gi. (Issue #305)
• Fixed dataLIF specification in backend config for IPv6.

Enhancements

• Updated to GoLang 1.14.
• Kubernetes: Added ability to remove CSI nodes from Trident's database via tridentctl.
• Kubernetes: Introduced Trident Operator to manage new Trident installations.
• Kubernetes: Added ability for Trident to automatically create and update export policies for NAS-based drivers to provide access to all nodes in your Kubernetes cluster. (Issue #252)
• Kubernetes: Trident now uses its own security context constraint in OpenShift. (Issue #374)
• Kubernetes: Added support for CRD API v1. (Issue #346)
• Kubernetes: Added support for additional auth providers. (Issue #348)
• Added support for bi-directional CHAP for ONTAP SAN drivers. (Issues #212 and #7)