Release v2.8.0
New Features/Changes
- #724 - [FEATURE]: CSM support for Openshift 4.13
- #877 - [FEATURE]: Make standalone helm chart available from helm repository : https://dell.github.io/dell/helm-charts
- #878 - [FEATURE]: CSI 1.5 spec support: Implement Volume Limits
- #879 - [FEATURE]: Configurable Volume Attributes use recommended naming convention /
- #922 - [FEATURE]: Use ubi9 micro as base image
Fixed Issues
- #916 - [BUG]: Remove references to deprecated io/ioutil package
- #928 - [BUG]: PowerStore Replication - Delete RG request hangs
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.