Skip to content

Releases: NetApp/trident

v22.10.0

31 Oct 22:37
e0353f0
Compare
Choose a tag to compare

Changes since v22.07.0

  • IMPORTANT: Kubernetes 1.25 is now supported in Trident. Please upgrade Trident prior to upgrading Kubernetes.
  • IMPORTANT: Trident will now strictly enforce the use of multipathing configuration in SAN environments, with a recommended value of find_multipaths: no in multipath.conf file. Use of non-multipathing configuration or use of find_multipaths: yes or find_multipaths: smart value in multipath.conf file will result in mount failures. Trident has recommended the use of find_multipaths: no since the 21.07 release.

Fixes:

  • Fixed issue specific to ONTAP backend created using credentials field failing to come online during 22.07.0
    upgrade (Issue #759)
  • Docker: Fixed an issue causing the Docker volume plugin to fail to start in some environments (Issues #548, #760).
  • Fixed SLM issue specific to ONTAP SAN backends to ensure only subset of data LIFs belonging to reporting nodes are published.
  • Fixed performance issue where unnecessary scans for iSCSI LUNs happened when attaching a volume.
  • Removed granular retries within Trident's iSCSI workflow to fail fast and reduce external retry intervals.
  • Fixed issue where an error was returned when flushing an iSCSI device when the corresponding multipath device was already flushed.

Enhancements

  • Kubernetes: Added support for Kubernetes 1.25.
    • Added new operator yaml (bundle_post_1_25.yaml) without a PodSecurityPolicy to support Kubernetes 1.25.
  • Kubernetes: Added a separate ServiceAccount, ClusterRole, and ClusterRoleBinding for the Trident Deployment and DaemonSet to allow future permissions enhancements.
  • Kubernetes: Added support for cross-namespace volume sharing.
  • All Trident ontap-* storage drivers now work with the ONTAP REST API.
  • Added support for LUKS-encrypted volumes for ontap-san and ontap-san-economy storage drivers.
  • Added support for Windows Server 2019 nodes.
  • Added support for SMB volumes on Windows nodes through the azure-netapp-files storage driver.

Deprecations:

  • Kubernetes: Updated minimum supported Kubernetes to 1.20.
  • Removed Astra Data Store (ADS) driver.
  • Removed support for yes and smart options for find_multipaths when configuring worker node multipathing for iSCSI.

v22.07.0

29 Jul 16:40
a957050
Compare
Choose a tag to compare

Changes since v22.04.0

Fixes:

  • Kubernetes: Fixed issue to handle boolean and number values for node selector when configuring Trident with Helm or the Trident Operator. (Issue #700)
  • Kubernetes: Fixed issue in handling errors from non-CHAP path, so that kubelet will retry if it fails. (Issue #736)

Enhancements

  • Kubernetes: Transition from k8s.gcr.io to registry.k8s.io as default registry for CSI images.
  • Kubernetes: ONTAP-SAN volumes will now use per-node igroups and only map LUNs to igroups while actively
    published to those nodes to improve our security posture. Existing volumes will be opportunistically switched to
    the new igroup scheme when Trident determines it is safe to do so without impacting active workloads.
  • Kubernetes: Included a ResourceQuota with Trident installations to ensure Trident DaemonSet is scheduled when PriorityClass consumption is limited by default.
  • Added support for Network Features to ANF driver. (Issue #717)
  • Added tech preview automatic MetroCluster switchover detection to ONTAP drivers. (Issue #228)
  • Kubernetes: Do not allow any volume plugins to be used by operator pods. (Issue #606)
  • Kubernetes: Added support for Pod Security Standards.

Deprecations:

  • Kubernetes: Updated minimum supported Kubernetes to 1.19.
  • Astra Data Store (ADS) driver updated to v1beta1 CRDs, so this version of Trident requires ADS 22.5.0 or later.
  • Backend config no longer allows multiple authentication types in single config.

Removals

  • AWS CVS driver (deprecated since 22.04) has been removed.
  • Kubernetes: Removed unnecessary SYS_ADMIN capability from node pods.
  • Kubernetes: Reduces nodeprep down to simple host info and active service discovery to do a best-effort
    confirmation that NFS/iSCSI services are available on worker nodes.

v22.04.0

29 Apr 18:22
e721974
Compare
Choose a tag to compare

Changes since v22.01.0

Fixes:

  • Improved parsing of iSCSI initiator names. (Issue #681)
  • Fixed issue where CSI storage class parameters weren't allowed. (Issue #598)
  • Fixed duplicate key declaration in Trident CRD. (Issue #671)
  • Fixed inaccurate CSI Snapshot logs. (Issue #629)
  • Fixed issue with unpublishing volumes on deleted nodes. (Issue #691)
  • Added handling of filesystem inconsistencies on block devices. (Issue #656)
  • Fixed issue pulling auto-support images when setting the imageRegistry flag during installation. (Issue #715)
  • Fixed issue where ANF driver failed to clone a volume with multiple export rules.
  • Fixed panic when accessing nil fields for aggregate space in ONTAP API responses.

Enhancements

  • Inbound connections to Trident's secure endpoints now require a minimum of TLS 1.3. (Issue #698)
  • Trident now adds HSTS headers to responses from its secure endpoints.
  • Trident now attempts to enable the Azure NetApp Files unix permissions feature automatically.
  • Kubernetes Trident daemonset now runs at system-node-critical priority class. (Issue #694)

Removals

  • ESeries driver (disabled since 21.07) has been removed.

v22.01.1

18 Mar 16:33
d6ad6c5
Compare
Choose a tag to compare

Changes since v22.01.0

Fixes:

  • Fixed issue with unpublishing volumes on deleted nodes. (Issue #691)
  • Fixed panic when accessing nil fields for aggregate space in ONTAP API responses.

v22.01.0

31 Jan 18:14
c6f1516
Compare
Choose a tag to compare

Changes since v21.10.0

  • IMPORTANT: If you are upgrading from any previous Trident release and use Azure NetApp Files, the location config parameter is now a mandatory, singleton field.

Fixes:

  • Fixed issue where azure-netapp-files driver could be confused by multiple resources with the same name.
  • ONTAP SAN IPv6 Data LIFs now work if specified with brackets.
  • Kubernetes: Increase node registration backoff retry time for large clusters.
  • Fixed issue where attempting to import an already imported volume returns EOF leaving PVC in pending state (Issue #489).
  • Fixed issue when Astra Trident performance slows down when > 32 snapshots are created on a SolidFire volume.
  • Replaced SHA-1 with SHA-256 in SSL certificate creation.
  • Fixed ANF driver to allow duplicate resource names and limit operations to a single location.

Enhancements:

  • Added ability to limit azure-netapp-files driver to specific resource groups, NetApp accounts, capacity pools.
  • Kubernetes: Added support for Kubernetes 1.23.
  • Allow cross-region volumes in GCP driver (Issue #633)
  • Kubernetes: Add scheduling options for Trident pods when installed via Trident Operator or Helm (Issue #651)
  • Added support for 'unixPermissions' option to ANF volumes. (Issue #666)

Deprecations:

  • Trident REST interface can listen and serve only at 127.0.0.1 or [::1] addresses

v21.10.1

24 Dec 04:29
68c809f
Compare
Choose a tag to compare

Changes since v21.10.0

  • IMPORTANT: The v21.10.0 release has an issue that can put the Trident controller into a CrashLoopBackOff state when a node is removed and then added back to the Kubernetes cluster. This issue is fixed in v21.10.1.

Fixes:

  • Fixed potential race condition when importing a volume on a GCP CVS backend resulting in failure to import
  • Fixed an issue that can put the Trident controller into a CrashLoopBackOff state when a node is removed and then added back to the Kubernetes cluster (Issue #669).
  • Fixed issue where SVM's were no longer discovered if no SVM name was specified (Issue #612).

v21.10.0

27 Oct 20:22
2b24824
Compare
Choose a tag to compare

Changes since v21.07.0

  • IMPORTANT: The v21.10.0 release has an issue that can put the Trident controller into a CrashLoopBackOff state when a node is removed and then added back to the Kubernetes cluster. This issue is fixed in v21.10.1.

Fixes:

  • Fixed issue where clones of XFS volumes could not be mounted on the same node as the source volume (Issue #514).
  • Fixed issue where Trident logged a fatal error on shutdown (Issue #597).
  • Kubernetes: Return a volume's used space as the minimum restoreSize when creating snapshots with ONTAP-NAS and ONTAP-NAS-Flexgroup drivers (Issue #645).
  • Kubernetes: Fixed issue where "Failed to expand filesystem" error was logged after volume resize (Issue #560).
  • Kubernetes: Fixed issue where a pod could get stuck in Terminating state (Issue #572).
  • Kubernetes: Fixed the case where an ONTAP-SAN-Economy FlexVol may be full of snapshot LUNs (Issue #533).
  • Kubernetes: Fixed custom YAML installer issue with different image (Issue #613).
  • Kubernetes: Fixed snapshot size calculation (Issue #611).
  • Kubernetes: Fixed issue where all Trident installers could identify plain Kubernetes as OpenShift (Issue #639).
  • Kubernetes: Fixed the Trident operator to stop reconciliation if the Kubernetes API server is unreachable (Issue #599).

Enhancements:

  • Added support for 'unixPermissions' option to GCP-CVS Performance volumes.
  • Added support for scale-optimized CVS volumes in GCP in the range 600 GiB to 1 TiB.
  • Kubernetes: Added support for Kubernetes 1.22.
  • Kubernetes: Enabled the Trident operator and Helm chart to work with Kubernetes 1.22 (Issue #628).
  • Kubernetes: Added operator image to tridentctl images command (Issue #570).

Experimental Enhancements:

  • Added support for volume replication in ONTAP SAN driver.
  • Added tech preview REST support for the ONTAP-NAS-Flexgroup, ONTAP-SAN, and ONTAP-NAS-Economy drivers.
  • Added driver for Astra Data Store.

Deprecations:

v21.07.2

01 Oct 15:45
34f41a4
Compare
Choose a tag to compare

Changes since v21.07.1

Fixes:

  • Fixed issue where clones of XFS volumes could not be mounted on the same node as the source volume (Issue #514).

Enhancements:

  • Kubernetes: Added support for Kubernetes 1.22.
  • Kubernetes: Enabled the Trident operator and Helm chart to work with Kubernetes 1.22 (Issue #628).

v21.07.1

12 Aug 18:13
Compare
Choose a tag to compare

Changes since v21.07.0

Fixes:

  • Fixed custom YAML installer issue with different image (Issue #613).
  • Fixed snapshot size calculation (Issue #611).

v21.07.0

30 Jul 22:53
3e2a87f
Compare
Choose a tag to compare

Users are informed that Trident v21.07.0 is NOT AVAILABLE FOR DOWNLOAD. Changes introduced to snapshotReserve with v21.07.0 can result in CSI VolumeSnapshots being unusable to create PersistentVolumeClaim(s).

This will be fixed with v21.07.1. If you have already upgraded to v21.07.0, users are advised to delete newly created VolumeSnapshots (provisioned with v21.07.0) and downgrade to the previous release in use.

Changes since v21.04.0

  • IMPORTANT: Trident has updated its recommendations for the iSCSI setup on worker nodes. Please carefully
    read the Preparing the worker node section of the documentation. Please ensure worker node multipathing
    configuration uses the find_multipaths value set to no.

  • IMPORTANT: In Trident versions earlier than 21.07, you could create ANF backend with no valid Capacity Pools
    corresponding to a Service Level. As a result the volumes were provisioned in the Capacity Pool of different
    Service Level type. This issue has been fixed but for an ANF backend, where there are no Capacity Pools
    corresponding to a Service Level, the backend might get into a failed state. To correct this, fix the
    serviceLevel in the ANF backend file or add a Capacity Pool that matches the backend's serviceLevel, and
    then run the backend update operation.

Fixes:

  • Updated the "Preparing the worker node" section of documentation to use default find_multipaths value for iSCSI multipathing.
  • Fixed the issue of not waiting for the multipath device to appear when discovered device count is 1 (Issue #511).
  • Fixed ANF issue with backend creation even when there are no valid Capacity Pool corresponding to a Service Level.
  • Kubernetes: Kubernetes version check for Helm install now matches prerelease versions (Issue #530).
  • Fixed issue where Trident crashed when ONTAP did not return serial number.
  • Kubernetes: Installer now selects correct csi-snapshotter version for Kubernetes and snapshot CRD versions.
  • Fixed issue where automatic node prep could not parse floating-point OS versions.
  • Changed ASUP image pull policy to IfNotPresent.

Enhancements:

  • Kubernetes: Updated to csi-snapshotter v4.0.0 for Kubernetes 1.20+.
  • Added ability to restrict volume provisioning to a subset of Capacity Pools using capacityPools field in the ANF backends.
  • ONTAP-SAN, ONTAP-NAS, and ONTAP-NAS-Flexgroup drivers now regard the snapshotReserve percentage as a percentage of the whole FlexVol size for new volumes (Issues #554, #496).
  • ONTAP-SAN adds extra 10% to FlexVol size to account for LUN metadata (Issue #555).
  • tridentctl install now shows timestamps in debug mode.
  • Kubernetes: Reduced HTTP timeout for CSI frontend to optimize node registration.
  • Kubernetes: Liveness port is now configurable and default changed to 17546.
  • Updated minimum TLS version to 1.2.

Experimental Enhancements:

  • Added tech preview REST support for the ONTAP NAS driver.
  • Added support for volume replication in ONTAP NAS driver.

Deprecations:

  • Kubernetes: Updated minimum supported Kubernetes to 1.17.
  • Disabled E-series driver.
  • Kubernetes: Removed pre-CSI support.