Skip to content

Latest commit

 

History

History
830 lines (619 loc) · 55.2 KB

CHANGELOG.md

File metadata and controls

830 lines (619 loc) · 55.2 KB
Raw

Change Log

Releases

Changes since v24.02.0

  • IMPORTANT: The 'limitVolumeSize' parameter now limits qtree/LUN sizes in the ONTAP economy drivers. Use the new 'limitVolumePoolSize' parameter to control Flexvol sizes in those drivers. (Issue #341).

Fixes:

  • Fixed Trident installation failures due to stale transactions.
  • Fixed tridentctl to ignore warning messages from Kubernetes (Issue #892).
  • Changed Trident controller SecurityContextConstraint priority to 0 (Issue #887).
  • ONTAP drivers now accept volume sizes below 20MiB (Issue#885).
  • Prevent shrinking of Flexvols during resize operation for the ONTAP-SAN driver.
  • Fixed ANF volume import failure with NFS v4.1.

Enhancements:

  • Kubernetes: Trident DaemonSet will now clean zombie mounts and residual tracking files at startup (Issue #883).
  • Kubernetes: Added PVC annotation trident.netapp.io/luksEncryption for dynamically importing LUKS volumes (Issue #849).
  • Kubernetes: Added topology awareness to ANF driver.
  • iSCSI self-healing will now initiate SCSI scans by exact LUN ID if deprecated igroups are in use (Issue #883).
  • Operations such as Clone and Resize are now allowed even when the backend is in suspended mode.
  • User-configured log settings for the Trident controller can now be propagated to Trident node pods.
  • Trident defaults to use REST instead of ZAPI for ONTAP versions 9.15.1 and later.
  • Added support for custom volume names and metadata (labels) on the ONTAP storage backends.
  • Added tech preview driver for Google Cloud NetApp Volumes.
  • Enhanced the azure-netapp-files (ANF) driver to automatically enable the snapshot directory by default when the NFS mount options are set to use NFS version 4.x.
  • Added Bottlerocket support for NFS volumes.

Deprecations:

  • Removed support for EOL Windows server 2019.

v24.02.0

Fixes:

  • Fixed ACP warning messages when ACP is not enabled (Issue #866).
  • Added a 10-second delay before performing a clone split during snapshot delete for ONTAP drivers, when a clone is associated with the snapshot.

Enhancements:

  • Kubernetes: Added support for Kubernetes 1.29.
  • Added ability to configure and disable iSCSI self-healing (Issue #864).
  • Added support for Cloud Identity.
    • AKS with ANF - Azure Workload Identity will be used as Cloud Identity
    • EKS with FSxN - AWS IAM role will be used as Cloud Identity
  • Added FSx personality to ONTAP drivers to enable integration with IAM and SecretsManager, and to enable Trident to delete FSx volumes with backups (Issue #453).
  • Trident can be installed as an EKS add-on via the EKS console.

Deprecations:

  • Removed in-toto attestations framework from multi-platform image manifests.

v23.10.0

Fixes:

  • Fixed volume expansion if a new requested size is smaller than the total volume size for ontap-nas and ontap-nas-flexgroup storage drivers (Issue #834).
  • Fixed volume size to display only usable size of the volume during import for ontap-nas and ontap-nas-flexgroup storage drivers (Issue #722).
  • Fixed FlexVol name conversion for ONTAP-NAS-Economy.
  • Fixed Trident initialization issue on a windows node when node is rebooted.

Enhancements:

  • Kubernetes: Added support for Kubernetes 1.28.
  • Added support for using Azure Managed Identities (AMI) with azure-netapp-files storage driver.
  • Added support for NVMe over TCP for the ONTAP-SAN driver.
  • Added ability to pause the provisioning of a volume when backend is set to suspended state by user (Issue #558).

Other advanced storage management/provisioning/access features available in Astra Control include:

  • Read-only clones
  • Snapshot Restore
  • Support for Kerberos in-flight encryption
  • Volume Replication

Please refer to Astra Control Documentation for details on these features.

Deprecations:

  • Kubernetes: Updated minimum supported Kubernetes to 1.23.

v23.07.0

Fixes:

  • Kubernetes: Fixed Trident upgrade to disregard old pods stuck in terminating state (Issue #740).
  • Kubernetes: Added toleration to "transient-trident-version-pod" definition (Issue #795).
  • Fixed ONTAP ZAPI requests to ensure LUN serial numbers are queried when getting LUN attributes to identify and fix ghost iSCSI devices during Node Staging operations.
  • Fixed error handling in storage driver code (Issue #816).
  • Fixed quota resize when using ONTAP drivers with use-rest=true.
  • Fixed LUN clone creation in ontap-san-economy.
  • Revert publish info field from rawDevicePath to devicePath; added logic to populate and recover (in some cases) devicePath field.

Enhancements:

  • Kubernetes: Added support for importing pre-provisioned snapshots.
  • Kubernetes: Minimized deployment and daemonset linux permissions (Issue #817).
  • No longer reporting the state field for "online" volumes and snapshots.
  • Updates the backend state if the ONTAP backend is offline (Issues #801, #543).
  • LUN Serial Number is always retrieved and published during the ControllerVolumePublish workflow.
  • Added additional logic to verify iSCSI multipath device serial number and size.
  • Additional verification for iSCSI volumes to ensure correct multipath device is unstaged.

Experimental Enhancements:

  • Added tech preview support for NVMe over TCP for the ONTAP-SAN driver.

Deprecations:

  • Kubernetes: Removed support for v1beta1 snapshots.
  • Kubernetes: Removed support for pre-CSI volumes and storage classes.
  • Kubernetes: Updated minimum supported Kubernetes to 1.22.

v23.04.0

  • IMPORTANT: Force volume detach for ONTAP-SAN-* volumes is only supported with Kubernetes versions which have enabled the Non-Graceful Node Shutdown feature gate. Force detach must be enabled at install time via --enable-force-detach Trident installer flag.

Fixes:

  • Fixed Trident Operator to use IPv6 localhost for installation when specified in spec.
  • Fixed Trident Operator cluster role permissions to be in sync with the bundle permissions (Issue #799).
  • Fixed issue with attaching raw block volume on multiple nodes in RWX mode.
  • Fixed FlexGroup cloning support and volume import for SMB volumes.
  • Fixed issue where Trident controller could not shut down immediately (Issue #811).
  • Added fix to list all igroup names associated with a specified LUN provisioned with ontap-san-* drivers.
  • Added a fix to allow external processes to run to completion.
  • Fixed compilation error for s390 architecture (Issue #537).
  • Fixed incorrect logging level during volume mount operations (Issue #781).
  • Fixed potential type assertion error (Issue #802).

Enhancements:

  • Kubernetes: Added support for Kubernetes 1.27.
  • Kubernetes: Added support for importing LUKS volumes.
  • Kubernetes: Added support for ReadWriteOncePod PVC access mode.
  • Kubernetes: Added support for force detach for ONTAP-SAN-* volumes during Non-Graceful Node Shutdown scenarios.
  • Kubernetes: All ONTAP-SAN-* volumes will now use per-node igroups. LUNs will only be mapped 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 (Issue #758).
  • Kubernetes: Improved Trident security by cleaning up unused Trident-managed igroups from ONTAP-SAN-* backends.
  • Added support for SMB volumes with Amazon FSx to the ontap-nas-economy and ontap-nas-flexgroup storage drivers.
  • Added support for SMB volumes with on-prem to the ontap-nas, ontap-nas-economy and ontap-nas-flexgroup storage drivers.
  • Added support for creation of SMB shares through Trident for on-prem and Amazon FSx.
  • Added support for linux/arm64 nodes (Issue #732).
  • Improved Trident shutdown procedure by deactivating API servers first (Issue #811).
  • Added cross-platform build support for Windows and linux/arm64 hosts to Makefile; see BUILD.md.

Deprecations:

  • Kubernetes: Backend-scoped igroups will no longer be created when configuring ontap-san and ontap-san-economy drivers (Issue #758).

v23.01.0

  • IMPORTANT: Kubernetes 1.26 is now supported in Trident. Please upgrade Trident prior to upgrading Kubernetes.

Fixes:

  • Kubernetes: Added options to exclude Pod Security Policy creation to fix Trident installations via Helm (Issues #783, #794).

Enhancements

  • Kubernetes: Added support for Kubernetes 1.26.
  • Kubernetes: Improved overall Trident RBAC resource utilization (Issue #757).
  • Kubernetes: Added automation to detect and fix broken or stale iSCSI sessions on host nodes.
  • Kubernetes: Added support for expanding LUKS encrypted volumes.
  • Kubernetes: Added credential rotation support for LUKS encrypted volumes.
  • Added support for SMB volumes with Amazon FSx to the ontap-nas storage driver.
  • Added support for NTFS permissions when using SMB volumes.
  • Added support for storage pools for GCP volumes with CVS service level.
  • Added support for optional use of flexgroupAggregateList when creating FlexGroups with the ontap-nas-flexgroup storage driver.
  • Improved performance for the ontap-nas-economy storage driver when managing multiple FlexVols.
  • Enabled dataLIF updates for all ONTAP NAS storage drivers.
  • Updated the Trident Deployment and DaemonSet naming convention to reflect the host node OS.

Deprecations:

  • Kubernetes: Updated minimum supported Kubernetes to 1.21.
  • Data LIFs should no longer be specified when configuring ontap-san or ontap-san-economy drivers.

v22.10.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

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

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)
  • Fixed Registry missing issue. (Issue #702)
  • 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.

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 20.07) has been removed.

v22.01.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.0

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.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.

v21.04.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).
  • Kubernetes: Increased speed of node pod registrations.

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.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:

  • 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

Beta Features:

Deprecations:

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:

  • 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.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:

  • 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

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)

v20.01.0

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

Fixes:

  • Kubernetes: Updated CSI sidecars to address CVE-2019-11255.
  • Set default SVM-DR tiering to snapshot-only for ONTAP cluster version 9.4 or less. (Issue #318)

Enhancements:

  • Kubernetes: Added support for Kubernetes 1.17. (Issue #327)
  • Kubernetes: Added support for IPv6. (Issue #122)
  • Kubernetes: Added support for Prometheus metrics. (Issue #121)
  • Switched from glide to go modules for dependency management.
  • ONTAP drivers now support virtual pools.
  • Kubernetes: Added --image-registry switch to installer. (Issue #311)
  • Kubernetes: Added --kubelet-dir switch to installer to simplify installation on some Kubernetes distributions. (Issue #314)
  • Added support for ONTAP tiering policy in backend config file (Issue #199)
  • Kubernetes: Added support for v1beta1 Kubernetes snapshots in Kubernetes 1.17.

Deprecations:

  • Kubernetes: Removed support for v1alpha1 Kubernetes snapshots.

Known Issues:

  • Flexgroup driver does not work properly with ONTAP 9.7

v19.10.0

Fixes:

  • Kubernetes: Added fix to ensure Trident pods only run on amd64/linux nodes. (Issue #264)
  • Kubernetes: Reduced log verbosity in CSI sidecars. (Issue #275)
  • Kubernetes: Added fix for volume names longer than 64 characters in solidfire and ontap-nas-economy drivers. (Issue #260, Issue #273)
  • Kubernetes: Node now retries registration with controller indefinitely (Issue #283)
  • Kubernetes: Fixed a panic when adding a storage backend fails.
  • Kubernetes: Fixed Azure NetApp Files to work with non-CSI deployments. (Issue #274)
  • Worked around a breaking API change in NetApp Cloud Volumes Service in AWS. (Issue #288)
  • Fixed NFS 4.1 access denied issue in ontap-nas-economy driver (Issue #256)
  • Disabled FabricPool tiering for ONTAP volumes created by Trident. (Issue #199)
  • Fixed bug when IFace is not set in the Element backend config. (Issue #272)

Enhancements:

  • Kubernetes: Added support to CSI Trident for volume expansion for iSCSI PVs.
  • Kubernetes: Added unsupported tridentctl for MacOS. (Issue #167)
  • Kubernetes: Added support to CSI Trident for raw block volumes with multi-attach for iSCSI PVs.
  • Kubernetes: Added support for Kubernetes 1.16 and OpenShift 4.2.
  • Kubernetes: Made installer setup directory optional and relative to working directory. (Issue #230)
  • Kubernetes: Support volume cloning using a PVC as the source.
  • Kubernetes: Added enhancements to 'tridentctl logs' command for CSI mode.
  • Added HTTP proxy support for NetApp Cloud Volumes Service in AWS driver. (Issue #246)
  • Added snapshotDir option to NetApp Cloud Volumes Service in AWS driver.
  • Added driver for NetApp Cloud Volumes Service in Google Cloud Platform.
  • Added option for JSON-formatted logging. (Issue #286)

Deprecations:

  • Kubernetes: Removed 'dry-run' switch from the installer. (Issue #192)
  • Changed minimum supported ONTAP version to 9.1.
  • Removed support for running Trident with an external etcd instance.

v19.07.0

Fixes:

  • Kubernetes: Improved volume import transaction cleanup during failure scenarios.
  • Kubernetes: Fix unknown backend states after Trident upgrade.
  • Kubernetes: Prevent operations on failed backends.
  • Kubernetes: Removed size requirement for volume import PVC file.

Enhancements:

  • Trident driver for Azure NetApp Files.
  • Kubernetes: Implemented CSI Trident (optional for Kubernetes 1.13, exclusive for Kubernetes 1.14+).
  • Kubernetes: Added support to CSI Trident for volume snapshots.
  • Kubernetes: Converted Trident to use custom resource definitions instead of etcd.
  • Kubernetes: Added support for Kubernetes 1.15.
  • Kubernetes: CSI Trident only supports CHAP authentication for Element backends.
  • Trident now allows Solidfire backends without Types defined. However, such backends will have one default storage pool with the default backend QoS values.
  • Added CONTRIBUTING.md file to describe the process for contributing changes to Trident.
  • Behavioral change: Enabled space-allocation feature for ONTAP SAN LUNs by default. Setting spaceAllocation parameter to false in ONTAP SAN backend's default config section would disable the space-allocation feature for those LUNs.
  • Kubernetes: Fix failure to set snapshot directory access during FlexGroup creation.

v19.04.0

Fixes:

  • Fixed panic if no aggregates are assigned to an ONTAP SVM.
  • Kubernetes: Updated CSI driver for 1.0 spec and Kubernetes 1.13. (Alpha release - unsupported)
  • Kubernetes: Allow Trident to start if one or more backend drivers fail to initialize.
  • Kubernetes: Fixed Trident to install on Kubectl 1.14. (Issue #241)

Enhancements:

  • Trident driver for NetApp Cloud Volumes Service in AWS.
  • Kubernetes: Import pre-existing volumes using the ontap-nas, ontap-nas-flexgroup, solidfire-san, and aws-cvs drivers. (Issue #74)
  • Kubernetes: Added support for Kubernetes 1.14.
  • Kubernetes: Updated etcd to v3.3.12.

v19.01.0

Fixes:

  • Fixed an issue where Trident did not allow specifying a port in the management LIF config (Issue #195). Thank you, @vnandha!
  • Only strip prefix on volume name if volume name starts with prefix.
  • Kubernetes: Refactored BackendExternal which fixed the output of "tridentctl get backend -o json" where details like "limitAggregateUsage" and "limitVolumeSize" were not found. (Issue #188)

Enhancements:

  • Updated Trident's 3rd-party dependencies for 19.01 release.
  • Added support for Docker 18.09, Docker Enterprise Edition 2.1, OpenShift 3.11 and Kubernetes 1.13.
  • Removed support for Docker Enterprise Edition 2.0 and Kubernetes 1.8.
  • Kubernetes: Added support for raw block volumes for iSCSI PVs.
  • Kubernetes: Added retry logic to installer for Kubernetes object creation.
  • Kubernetes: Updated etcd to v3.3.10 and client-go to v10.0.0.
  • Kubernetes: Trident now honors the nfsMountOptions parameter in ONTAP NAS backend config files.
  • Behavioural change: The Trident installer now automatically adds the backend used to provision the Trident volume in new installations.

Deprecations:

  • Kubernetes: Deprecated PVC annotation trident.netapp.io/reclaimPolicy as the reclaim policy can be set in the storage class since Kubernetes v1.8.

v18.10.0

Fixes:

  • Modified log messages about ONTAP media types not associated with performance classes (Issue #158).
  • Docker: Resolved issue where containers might not restart after restarting Docker (Issue #160).

Enhancements:

  • Added ability to set snapshotReserve in backend config files, volume creation options, and PVC annotations (Issue #43).
  • Added ability to limit the size of requested volumes.
  • Added ability to limit the ONTAP Aggregate usage percentage (Issue #64).
  • Added ability to limit the ONTAP Flexvol size for the ontap-nas-economy driver (Issue #141).
  • Kubernetes: Added support for expanding NFS Persistent Volumes (Issue #21).
  • Kubernetes: Modified Trident installer to do most of its work in a pod.
  • Kubernetes: Updated etcd to v3.3.9 and client-go to v9.0.0.

Deprecations:

  • Docker: Trident's support for Docker EE 2.0's UCP access control will be removed in the v19.01 release, replaced by the native Kubernetes access control support in Docker EE 2.1 and beyond. The --ucp-host and --ucp-bearer-token parameters will be deprecated and will not be needed in order to install or uninstall Trident.

v18.07.0

Fixes:

  • Fixed cleanup of the transaction object upon failed deletion (Issue #126).
  • Kubernetes: Fixed an issue where Trident would provision a ReadWriteMany PVC to an iSCSI backend.
  • Kubernetes: Fixed an installer issue where the Trident PV could be bound to the wrong PVC (Issue #120).
  • Kubernetes: Fixed an issue where the Trident installer could fail if a default storage class is set (Issue #120).
  • Kubernetes: Fixed an issue where the Trident installer could fail to delete objects on some Kubernetes versions (Issue #132).
  • Docker: Fixed an issue where deleted qtrees could appear in Docker volume list.
  • Docker: Fixed plugin restart issue for newer versions of Docker (Issue #129).
  • Docker: Trident no longer crashes if ONTAP volumes are offline (Issue #151).

Enhancements:

  • Added ontap-nas-flexgroup driver to support ONTAP FlexGroup Volumes.
  • Changed ONTAP drivers so that the snapshot reserve is set to zero when snapshotPolicy is "none".
  • Added support for Docker EE UCP.
  • Kubernetes: Added regex matching to storage pool selection as well as a new excludeStoragePools option for Kubernetes storage classes (Issue #118).
  • Kubernetes: Added support for iSCSI multipath (Issue #69).
  • Kubernetes: Updated etcd to v3.2.19 and client-go to v7.0.0.
  • Kubernetes: Added --previous switch to 'tridentctl logs' command.
  • Kubernetes: Added liveness probes to the trident-main and etcd containers.
  • Kubernetes: Added --trident-image and --etcd-image switches to 'tridentctl install' command.
  • Kubernetes: Added prototype CSI implementation to Trident.

v18.04.0

Fixes:

  • Clone operations are more resilient to busy storage controllers.
  • Fixed cleanup of goroutines.
  • Extended timeouts for storage controller API invocations.
  • Prevented exit if a startup error occurs so Docker and Kubernetes don't restart Trident continuously.
  • Fixed an issue where SolidFire cloned volumes were not updated with new QoS values.
  • Kubernetes: Trident no longer emits SCSI bus rescan errors into log.
  • Kubernetes: Fixed incorrect association of volumes with backends after backend update (Issue #111).
  • Docker: iSCSI device discovery and removal is faster, more granular, and more reliable.
  • Docker: Fixed default size handling (Issue #102).
  • Docker: Client interfaces start immediately to avoid Docker plugin timeouts.

Enhancements:

  • Added FQDN support for the management and data LIF of ONTAP backends.
  • For Kubernetes 1.9+, CHAP secrets will be created in Trident's namespace instead of the PVC's namespace.
  • Return new HTTP codes from REST interface to indicate Trident startup status.
  • Set the minimum supported SolidFire Element version to 8.0.
  • Kubernetes: Simplified installing Trident with a new installer.
  • Kubernetes: Added the ability to define a custom name for a storage backend. This enhancement enables adding multiple instances of the same backend with different policies (e.g., different snapshot policies), which obviates extending the Trident storage class API to support new parameters (Issue #93).
  • Kubernetes: Added the ability to rename an existing backend.
  • Kubernetes: SolidFire defaults to use CHAP if Kubernetes version is >= 1.7 and a trident access group doesn't exist. Setting AccessGroup or UseCHAP in config overrides this behavior.
  • Docker: The aggregate attribute in ONTAP config files is now optional.

v18.01.0

Fixes:

  • Volume deletion is an idempotent operation with the ontap-nas-economy driver (Issue #65).
  • Enabled Trident installation on an EF-series (all-flash) array.
  • Fixed an issue where qtrees with names near the 64-character limit could not be deleted.
  • Enforced fencing of ONTAP aggregates and E-series pools to match config file values.
  • Fixed an issue where deleting volumes using the ONTAP SAN driver could leave volumes stuck in a partially deleted state.
  • Fixed an issue where the ONTAP SAN driver would create junction paths for cloned iSCSI volumes

Enhancements:

  • Trident can now serve as a Docker Volume Plugin.
  • Enabled cloning volumes via a new PVC annotation.
  • Added support for Kubernetes 1.8 Storage Classes to set the mount options and reclaim policy of PVs (Issue #49).
  • Introduced the fsType parameter in the Kubernetes Storage Class to set the file system type of iSCSI PVs.
  • Added CHAP support for SolidFire (Issue #42).
  • Decoupled Trident storage pools from volumes to facilitate "vol move" and SVM-DR with ONTAP backends.
  • Added support for the etcdv3 API (Issue #45).
  • Added the etcd-copy utility to migrate data between etcd clusters.
  • Enabled TLS for Trident's etcd client and the etcd-copy utility.
  • Added scripts and instructions for setting up an external etcd cluster using etcd operator.
  • Significantly reduced Trident and Trident-Launcher Docker image sizes.
  • Clarified and enhanced storage class pool selection by introducing storagePools and renaming requiredStorage to additionalStoragePools.
  • Added hostname support to the dataLIF option in the config file for ontap-nas and ontap-nas-economy drivers.
  • Added minimum volume size checks to all plugins.
  • Docker: Improved iSCSI rescan performance for ONTAP SAN and E-series plugins.

v17.10.0

Fixes:

  • tridentctl correctly handles larger payloads using chunked encoding.
  • Trident installs correctly in a Kubernetes pod with E-series and ONTAP SAN.
  • Trident allows periods in PVC names (Issue #40).
  • Fixed issue where ONTAP NAS volumes were not mountable immediately after creation when using load-sharing mirrors for the SVM root volume (Issue #44).
  • File system type is not set for NFS volumes in the persistent store (Issue #57).
  • Deprecated the update script.

Enhancements:

  • Controller serial numbers are reported by the REST interface and tridentctl.
  • tridentctl logs can display launcher and ephemeral logs, and it can create a support archive.
  • Added ontap-nas-economy driver (Issue #2).
  • Added support for NetApp Volume Encryption to the ONTAP drivers (Issue #3).
  • Trident installer now works with Kubernetes 1.8.
  • tridentctl can detect and use 'oc' in OpenShift environments.

v17.07.0

Fixes:

  • Trident and Trident launcher no longer fail if they cannot validate the container orchestrator version.
  • When running in a pod, the Trident REST interface is no longer accessible by default from outside the pod.
  • Trident correctly handles updating backends that have volumes provisioned using storage classes that no longer exist (Issue #29).
  • Installer script correctly creates a new namespace (Issue #39).

Enhancements:

  • Added support for storage.k8s.io/v1 storage classes and the default storage class introduced in Kubernetes v1.6.0.
  • Changed the installer script to support both Kubernetes and OpenShift deployments in a uniform manner and to leverage Role-Based Access Control (RBAC) authorization for better security.
  • Added scripts for uninstalling and updating Trident.
  • Added tridentctl CLI tool for managing Trident.
  • SolidFire backend configuration file accepts up to four Volume Access Group IDs (Issue #24).
  • Improved efficiency of ONTAP LUN ID selection.
  • Added PVC annotation trident.netapp.io/blockSize to specify block/sector size for SolidFire backends (Issues #33 and #37).
  • Added PVC annotation trident.netapp.io/fileSystem to specify the file system type for iSCSI volumes (Issue #37).

v17.04.0

Fixes:

  • Trident now rejects ONTAP backends with no aggregates assigned to the SVM.
  • Trident now allows ONTAP backends even if it cannot read the aggregate media type, or if the media type is unknown. However, such backends will be ignored for storage classes that require a specific media type.
  • Trident launcher supports creating the ConfigMap in a non-default namespace.

Enhancements:

  • The improved Trident launcher has a better support for failure recovery, error reporting, user arguments, and unit testing.
  • Enabled SVM-scoped users for ONTAP backends.
  • Switched to using vserver-show-aggr-get-iter API for ONTAP 9.0 and later to get aggregate media type.
  • Added support for E-Series.
  • Upgraded the etcd version to v3.1.3.
  • Added release notes (CHANGELOG.md).

v1.0

  • Trident v1.0 provides storage orchestration for Kubernetes, acting as an external provisioner for NetApp ONTAP and SolidFire systems.
  • Through its REST interface, Trident can provide storage orchestration for non-Kubernetes deployments.