v19.04.0

Attention

An issue with upgrades to 19.04.0 has been identified that may cause existing backends to get set to an unknown state. That issue is resolved in 19.04.1.

Changes since v19.01.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.04.0-beta.1

Changes since v19.01.0

Fixes:

Enhancements:

• Trident driver for NetApp Cloud Volumes Service in AWS
• Kubernetes: Updated etcd to v3.3.11.

Deprecations:

v19.01.0

Changes since v18.10.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

Changes since v18.07.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.1

Changes since v18.07.0

Fixes:

• Docker: Resolved issue where containers might not restart after restarting Docker (Issue #160).
• Kubernetes: Will now send correct RBAC format based on UCP version being used (Issue #161).

Enhancements:

v18.04.1

Changes since v18.04.0

Fixes:

• Docker: Resolved issue where containers might not restart after restarting Docker (Issue #160).

Enhancements:

v18.10.0-beta.1

Changes since v18.07.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).
• Kubernetes: Added support for expanding NFS Persistent Volumes (Issue #21).
• Kubernetes: Modified Trident installer to do most of its work in a pod.

v18.07.0

Changes since v18.04.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.07.0-beta.1

Changes since v18.04.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.
• Kubernetes: Fixed an issue where the Trident installer could fail if a default storage class is set.
• Docker: Fixed an issue where deleted qtrees could appear in Docker volume list.

Enhancements:

• Changed ONTAP drivers so that the snapshot reserve is set to zero when snapshotPolicy is "none"
• 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

Changes since v18.01.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.