Releases: qnap-dev/QNAP-CSI-PlugIn
Releases · qnap-dev/QNAP-CSI-PlugIn
v1.6.0
New Features
- K8s v1.35 Support: Upgraded compatibility to Kubernetes version 1.35.
- iSCSI Multipath: Added support for iSCSI multipath to enhance storage redundancy.
- CHAP Authentication: Enabled CHAP configuration for improved iSCSI connection security.
Bug Fixes
- LUN Name Limit: Fixed an issue where long PVC names exceeded the 32-character limit.
v1.5.2
New Features
- Automatically detect the Rancher environment and grant the necessary permissions.
- Add secure connection (HTTPS) configuration.
apiVersion: v1
kind: Secret
metadata:
name: backend-qts-secret # Required. Name your secret.
namespace: trident
type: Opaque
stringData:
username: user # Required. Your NAS username.
password: 0000 # Required. Your NAS password.
storageAddress: 0.0.0.0 # Required. Your NAS IP address.
https: false # Optional. Whether to enable a secure connection. Default: False.
port: 8080 # Optional. Specify the port. Default: 8080.
trustedCACertificate: <Base64-encoded-trusted-ca-certificate-for-backend> # Optional. Base64-encoded value of trusted CA certificate. Used for certificate-based authentication. - Extend Default iSCSI Timeout and Allow User Customization.
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: storageclass1 # Required. Name your storageclass.
provisioner: csi.trident.qnap.io
parameters:
selector: "performance=performance1" # Required. Corresponds to the labels in the virtual pool.
fsType: "ext4" # Optional. You can choose to enter ext4 (default), xfs, or ext3.
replacementTimeout: '120' # Optional. Define the iSCSI timeout, with a default value of 120 seconds
allowVolumeExpansion: trueBug Fixes
- Trivy scan identified a security vulnerability in one of the containers used by CSI Plugin 1.5.0.
v1.5.1
Fixed Issue
- Fixed compatibility issues with QuTS hero firmware version h5.3.0 and later.
v1.5.0
New Features
- Support for Kubernetes version 1.32
- Support enabling recycle bin via PVC configuration in SMB protocol
annotations: trident.qnap.io/SharedFolderRecycleBin: "true"
v1.4.0
New Features
- Support for Talos 1.8 and latest as a host OS.
- Support the SMB protocol.
- Supports specifying
fsType(ext4 (default), xfs, or ext3) in StorageClass when using the iSCSI protocol.
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.