Releases: piraeusdatastore/linstor-csi
Releases · piraeusdatastore/linstor-csi
v0.15.1
Fixed
- A bug introduced in 0.14.0 meant that using the "FollowTopology" policy would not create the requested amount
of volume replicas. Instead, only a single replica was created. This bug is now fixed. Existing volumes can be
updated by usinglinstor rg adjust <resource group>
.
v0.15.0
Added
- New default volume scheduler
AutoPlaceTopology
. This new scheduler is a topology aware version of the old
AutoPlace
scheduler. Since it is topology aware, it can be used to optimize volume placement when using
WaitForFirstConsumer
volume binding or restricting placement viaallowedTopologies
, while still respecting
user-defined placement options such asreplicasOnSame
orreplicasOnDifferent
.
v0.14.1
v0.14.0
Added
-
Option to send a bearer token for authentication. This can be used when the API is secured by a project like
kube-rbac-proxy
. -
Add explicit namespace
linstor.csi.linbit.com
to volume parameters in storage class. This makes it easier to track
which parameter is handled by which component (for example:csi.storage.k8s.io/fstype
is handled by the CSI
infrastructure, not the plugin itself).Un-namespaced parameters are still supported, while explicitly namespaced
parameters with a foreign namespace are now ignored. These would produce "unknown parameter" errors previously.
Changed
- Calls to
GetCapacity
now take topology information (if any) into account.
0.13.1
0.13.0
Added
- Allow setting arbitrary properties using a parameter prefixed with the
property.linstor.csi.linbit.com
namespace.
Changed
- Generate a resource group name if non was provided. The name is generated based on the provided parameters. Since
storage classes are immutable, volumes provisioned using the same storage class will always receive the same
resource group name.
Removed
- Resource groups no longer update existing properties or remove additional properties if they not set in the storage
class. A resource group is immutable from the linstor-csi's point of view.
Fixed
- Failed snapshots are now cleaned up and retried properly. This mitigates an issue whereby the snapshot failed for
one reason or other, but the snapshot controller continously polls it for "completion".
0.12.1
Fixed
- Controller no longer treats LINSTOR resource(-definitions) as ready when the DELETE flag is set. Operations are now
aborted early and tried again later when the LINSTOR resource is really gone.
0.12.0
Changed
- PVCs can now be deleted independently of Snapshots. LINSTOR ResourceDefinitions for the PVC will exist until
both Snapshots and Resources are deleted.
Fixed
- Add
nouuid
to default XFS mount options. This enables mounting restored snapshots on the same node as the original. - Detach() operations no longer delete existing diskless resources (i.e. TieBreaker resources), only those created by
Attach() operations.
0.11.0
Changed
- Snapshot information is persisted using native LINSTOR Snapshots instead of storing it in properties of RDs.
- Snapshots are marked as ready only after LINSTOR reports success
- Generate fallback id for a snapshot based on the suggested name using UUIDv5
- Only create a single snapshot in volume-from-volume scenarios
Fixed
- LayerList was ignored when not using the AutoPlace scheduler. All schedulers not pass this information to LINSTOR. #102