v1.3.0

New Features

• Added support for Kubernetes v1.30.
• Added support for QuTS hero, allowing you to use QuTS hero as a persistent volume.
• Added support for QTS 5.1.x and QuTS hero h5.1.x.
• You can now enable SSD cache in the QoS configuration instead of using annotation in the volume.

      features:
        raidLevel: "0"
        ssdCache: "true"

• The backend can now automatically update physical pools.
• Added a new QoS setting for RAID levels in QTS and QuTS hero.

    - serviceLevel: RAID1
      labels:
        performance: basic
      features:
        raidLevel: "1"

• Added support for volume features such as deduplication, compression, and fast clone in QuTS hero.

kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: pvc-premium-hero
  annotations:
    # thin allocate is customized
    trident.qnap.io/ThinAllocate: "false"

    # QuTS-hero features
    trident.qnap.io/Deduplication: "true"
    trident.qnap.io/Compression: "true"
    trident.qnap.io/FastClone: "true"
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 5Gi
  storageClassName: premium

v1.2.1

Fixed Issue

• Fixed an issue that caused pool creation to fail when using a virtual switch.

v1.2.0

New Features

• A new backend parameter called "NetworkInterface" is now available, which allows users to specify the network adapter for iSCSI connections. If you leave this parameter empty, the backend IP address becomes the default route.

spec:
  version: 1
  storageDriverName: qnap-iscsi
  backendName: qts-david
  networkInterfaces: ["K8s-ISCSI"] #optional
  credentials:

• Users can now use the TridentBackendConfig custom resource to create and manage Trident backends directly through the Kubernetes interface.
• Added support for ARM64 and ARMv7 architectures.

Fixed Issue

• Fixed an issue where when creating a volume on QTS 5.1.x, the creation status would get stuck on "Pending" and an "iSCSI CREATE Failed" log message would be recorded.