v1.7.0

This release adds support for LINSTORs x-replicas-on-different feature via the xReplicasOnDifferent storage class parameter.

For example, you may want to have 2 copies of the volume available in each zone, with 4 copies in total:

...
parameters:
  autoPlace: "4"
  xReplicasOnDifferent: |
    topology.kubernetes.io/zone: 2

---

Added

• Add XReplicasOnDifferent parameter.

v1.6.5

This release fixes the behaviour when attempting to use volumes where DRBD refuses to promote. Because of the defaults of the mount call, such volumes could have been mounted as RO, even if RW was requested. We now properly fail to mount such volumes.

---

Fixed

• Disable mount fallback to mount a volume RO even if a RW mount was requested.

v1.6.4

This release fixes two issues: one where it would attempt to resize a block-mode volume if it could detect a file system on it, and the other fixes attempts to restore snapshot on nodes that are currently not available.

Note

This was released back in November 2024, but we missed to announce it back then.

---

Fixed

• Fixed an issue that caused the node publish call to attempt to resize a block volume: block volumes are now never
  attempted to be resized.
• Ensure that snapshot restore requests are tried on nodes that are actually available.

v1.6.3

This release fixes an issue with volume provisioning not placing the resources on the intended node when the intended node itself does not have a storage pool. The eligible nodes should then be determined by the remoteAccessPolicy. Due to a bug introducing with caching back in release 1.2.3, this instead allowed placement on all nodes.

---

Fixed

• Fixed node filtering when initial placement was not possible. This now takes the remoteAccessPolicy into account like
  intended.

v1.6.2

Small fix for the previous release. LINSTOR does not always return a device path immediately after creating a resource, so we check that the device path is set before passing it to the csi node agent.

---

Fixed

• Fix device path passdown when LINSTOR does not report a device path.

v1.6.1

A small release that fixes an issue introduced by the recent caching changes. The fix also means that the csi-node plugin does not need to query LINSTOR for volume information.

---

Added

• Pass device paths down from CSI Controller on publish, reducing LINSTOR API requests from the CSI Node.

v1.6.0

This release brings support for a new snapshot type Linstor: This enables users to use Linstor-to-Linstor backup shipping using the CSI driver. This is currently limited to the creation of backups, restoring requires manual interaction.

---

Added

• Support for creating backups with LINSTOR-to-LINSTOR shipping.

v1.5.0

Update the base image to have access to newer FS utilities. This fixes a bug when running on new kernels that make use of "new" ext4 and XFS features.

---

Added

• Support specifying multiple storage pools in the parameters, separated by spaces.

Changed

• Update base image to Debian 12.

v1.4.0

Remove support for Openflex layers: these caused LINSTOR 1.26.0 to return errors in some edge cases.

---

Breaking

• Update golinstor to support LINSTOR 1.26.0, removing support for Openflex layers.

v1.3.1

This release contains some fixes when attaching volumes (i.e. when a volume is mounted on behalf of a Pod).

---

Changed

• Default access policy for resources without replication layer is now "local only".

Fixed

• Do not try to create diskless resource if there is no compatible diskless layer (DRBD or NVMe) available.
• Do not allow attaching a volume that has no existing replica.