Skip to content

Releases: dell/csi-powerstore

v2.11.0

26 Jul 23:02
v2.11.0
8734a44
Compare
Choose a tag to compare

What's Changed

  • Update OCP/K8s min/max support version to be consistent with documentation in #321
  • Update doc links in Readme in #322
  • Bump google.golang.org/protobuf from 1.31.0 to 1.33.0 in /tests/e2e in #319
  • Bump golang.org/x/net from 0.21.0 to 0.23.0 in /tests/e2e in #325
  • Bump golang.org/x/net from 0.21.0 to 0.23.0 in #324
  • Bump google.golang.org/protobuf from 1.32.0 to 1.33.0 in #320
  • Updating deprecated packages in #326
  • Add warning message if an higher k8s version is tested in #323
  • Adding CSM 1.10.2 changes in #327
  • Update linters.yaml in #328
  • Return FailedPrecondition if the volume has associated snapshot in #330
  • Adding k8 1.30 support in #331
  • Add non GA version check in #332
  • Remove unused code related to register k8s cluster in #333
  • Update golib dependencies in #334
  • Update OCP Version in #335
  • Updating package in #336

Full Changelog: v2.10.0...v2.11.0

Release v2.10.1

28 May 14:00
707d688
Compare
Choose a tag to compare

What's Changed

  • update OCP/K8s min/max support version to be consistent with documentation in #321
  • Update doc links in Readme in #322
  • Bump google.golang.org/protobuf from 1.31.0 to 1.33.0 in /tests/e2e by in #319
  • Bump golang.org/x/net from 0.21.0 to 0.23.0 in /tests/e2e in #325
  • Bump golang.org/x/net from 0.21.0 to 0.23.0 by in #324
  • Bump google.golang.org/protobuf from 1.32.0 to 1.33.0 in #320
  • Updating deprecated packages in #326
  • Add warning message if an higher k8s version is tested in #323
  • Adding CSM 1.10.2 changes in #327
  • Updating go dependencies in #329

Full Changelog: v2.10.0...v2.10.1

Release v2.10.0

20 Mar 13:58
v2.10.0
5dc891f
Compare
Choose a tag to compare

What's Changed

  • Update offline bundle instructions from CSI to CSM Operator in #295
  • Golint errors fixes in #297
  • Updating latest gopowerstore and packages in #299
  • Fixing Go mod tidy errors in #300
  • Bump golang.org/x/crypto from 0.16.0 to 0.17.0 in /tests/e2e in #301
  • Sanity Test Fixes in #296
  • Discover NVMe TCP addresses individually in #302
  • Updating latest gopowerstore commit in #303
  • Bump github.com/opencontainers/runc from 1.1.10 to 1.1.12 in /tests/e2e in #305
  • Update if-check for the failover REST failure in #307
  • Sanity Test Fixes in #306
  • update go version in action in #308
  • Implement multi-stage build in csi-powerstore driver in #311
  • Bump the csm version in #313
  • Use Common Go Image in #312
  • go version bump-up in #315
  • Updating latest go library commits in #316
  • Update go mod in #317
  • Update latest gobrick in #318

Full Changelog: v2.9.1...v2.10.0

Release v2.9.1

01 Feb 20:53
69801a9
Compare
Choose a tag to compare

What's Changed

  • Discover NVMe TCP addresses individually #302
  • Updating if check for a failover failure in #304
  • Security fixes for v2.9.1

Fixed Issue

  • Volumes failing to mount when User having NVMeTCP on Powerstore (dell/csm#1108)

Full Changelog: v2.9.0...v2.9.1

Release v2.9.0

13 Dec 10:38
v2.9.0
d62b826
Compare
Choose a tag to compare

New Features/Changes

Fixed Issues

Known Issues

Issue Resolution or workaround, if known
Delete namespace that has PVCs and pods created with the driver. The External health monitor sidecar crashes as a result of this operation Deleting the namespace deletes the PVCs first and then removes the pods in the namespace. This brings a condition where pods exist without their PVCs and causes the external-health-monitor sidecar to crash. This is a known issue and has been reported at kubernetes-csi/external-health-monitor#100
fsGroupPolicy may not work as expected without root privileges for NFS only
kubernetes/examples#260
To get the desired behavior set "allowRoot: "true" in the storage class parameter
If the NVMeFC pod is not getting created and the host looses the ssh connection, causing the driver pods to go to error state remove the nvme_tcp module from the host incase of NVMeFC connection
When a node goes down, the block volumes attached to the node cannot be attached to another node This is a known issue and has been reported at kubernetes-csi/external-attacher#215. Workaround:
1. Force delete the pod running on the node that went down
2. Delete the volumeattachment to the node that went down.
Now the volume can be attached to the new node.
When driver node pods enter CrashLoopBackOff and PVC remains in pending state with one of the following events:
1. failed to provision volume with StorageClass <storage-class-name>: error generating accessibility requirements: no available topology found
2. waiting for a volume to be created, either by external provisioner "csi-powerstore.dellemc.com" or manually created by system administrator.
Check whether all array details present in the secret file are valid and remove any invalid entries if present.
Redeploy the driver.
If an ephemeral pod is not being created in OpenShift 4.13 and is failing with the error "error when creating pod: the pod uses an inline volume provided by CSIDriver csi-powerstore.dellemc.com, and the namespace has a pod security enforcement level that is lower than privileged." This issue occurs because OpenShift 4.13 introduced the CSI Volume Admission plugin to restrict the use of a CSI driver capable of provisioning CSI ephemeral volumes during pod admission (https://docs.openshift.com/container-platform/4.13/storage/container_storage_interface/ephemeral-storage-csi-inline.html). Therefore, an additional label "security.openshift.io/csi-ephemeral-volume-profile" needs to be added to the CSIDriver object to support inline ephemeral volumes.
In OpenShift 4.13, the root user is not allowed to perform write operations on NFS shares, when root squashing is enabled. The workaround for this issue is to disable root squashing by setting allowRoot: "true" in the NFS storage class.
If the volume limit is exhausted and there are pending pods and PVCs due to exceed max volume count, the pending PVCs will be bound to PVs, and the pending pods will be scheduled to nodes when the driver pods are restarted. It is advised not to have any pending pods or PVCs once the volume limit per node is exhausted on a CSI Driver. There is an open issue reported with Kubenetes at kubernetes/kubernetes#95911 with the same behavior.

Documentation

Change Log

See the CHANGELOG for more details.

Release v2.8.0

20 Sep 12:12
v2.8.0
8d5060f
Compare
Choose a tag to compare

New Features/Changes

Fixed Issues

Known Issues

Issue Resolution or workaround, if known
If an ephemeral pod is not being created in OpenShift 4.13 and is failing with the error "error when creating pod: the pod uses an inline volume provided by CSIDriver csi-powerstore.dellemc.com, and the namespace has a pod security enforcement level that is lower than privileged." This issue occurs because OpenShift 4.13 introduced the CSI Volume Admission plugin to restrict the use of a CSI driver capable of provisioning CSI ephemeral volumes during pod admission (https://docs.openshift.com/container-platform/4.13/storage/container_storage_interface/ephemeral-storage-csi-inline.html). Therefore, an additional label "security.openshift.io/csi-ephemeral-volume-profile" needs to be added to the CSIDriver object to support inline ephemeral volumes.
In OpenShift 4.13, the root user is not allowed to perform write operations on NFS shares, when root squashing is enabled. The workaround for this issue is to disable root squashing by setting allowRoot: "true" in the NFS storage class.
If the volume limit is exhausted and there are pending pods and PVCs due to exceed max volume count, the pending PVCs will be bound to PVs, and the pending pods will be scheduled to nodes when the driver pods are restarted. It is advised not to have any pending pods or PVCs once the volume limit per node is exhausted on a CSI Driver. There is an open issue reported with Kubenetes at kubernetes/kubernetes#95911 with the same behavior.

Documentation

Change Log

See the CHANGELOG for more details.

Release v2.7.0

Release v2.6.0

27 Mar 11:09
v2.6.0
7c4bac3
Compare
Choose a tag to compare

New Features/Changes

  • Added support for CSM Resiliency
  • Added support for Kubernetes 1.26
  • UBI image update
  • Go version update to 1.20

Fixed Issues

Multiple iSCSI network support
Create volume successful but unable to map volumes to a hosts
Can't find IP in X_CSI_POWERSTORE_EXTERNAL_ACCESS for NFS provisioning

Documentation

Change Log

See the CHANGELOG for more details.

Release v2.5.1

22 Feb 16:21
v2.5.1
d011b77
Compare
Choose a tag to compare

New Features/Changes

There are no features/changes in this release.

Fixed Issues

Fixed issue where driver was not properly cleaning up resources when volumes were unmounted

Documentation

Change Log

See the CHANGELOG for more details.

Release v2.5.0

13 Dec 16:13
v2.5.0
9c0248a
Compare
Choose a tag to compare

New Features/Changes:

  • Added support for Storage Capacity Tracking
  • Added support for PowerStore v3.2
  • Added support for Kubernetes 1.25
  • Added support for OpenShift 4.11
  • UBI image update
  • Go version update to 1.19

Fixed Issues

There are no fixed issues in this release.

Documentation