Skip to content

Latest commit

 

History

History
185 lines (158 loc) · 10.2 KB

CHANGELOG.md

File metadata and controls

185 lines (158 loc) · 10.2 KB

Change Log

Releases

Changes since v18.07.0

Fixes:

  • Modified log messages about ONTAP media types not associated with performance classes (Issue #158).

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

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.