Releases: dell/csi-unity
Releases · dell/csi-unity
Release v2.13.0
v2.13.0
This tag was signed with the committer’s verified signature.
harishp8889
Harish P
Documentation
What's Changed
- Update actions by @shaynafinocchiaro in #243
- Bump github.com/pelletier/go-toml from 1.2.0 to 1.9.5 by @dependabot in #240
- Bump golang.org/x/crypto from 0.26.0 to 0.31.0 by @dependabot in #248
- Fix for Helm Installation checking Snapshot CRD Only When Snapshot Enabled is True by @WilsonRadadia20 in #253
- Update go version to 1.23 by @csm-release in #246
- Bump the golang group across 1 directory with 39 updates by @dependabot in #255
- Added driver release automation by @harishp8889 in #250
- bump versions for csm 1.13.0 by @lukeatdell in #258
- Add preflight required labels. by @donatwork in #260
- Bump the golang group across 1 directory with 22 updates by @dependabot in #261
- Bump the golang group across 1 directory with 9 updates by @dependabot in #264
- Bump the golang group across 1 directory with 2 updates by @dependabot in #266
New Contributors
- @harishp8889 made their first contribution in #250
- @lukeatdell made their first contribution in #258
Full Changelog: v2.12.0...v2.13.0
Contributors
harishp8889, donatwork, and 4 other contributors
Assets 2
Release v2.12.0
v2.12.0
This tag was signed with the committer’s verified signature.
suryagupta4
Surya Gupta
What's Changed
- gobrick module update by @suryagupta4 in #225
- Update basicsystem info usage for probe to reduce authentication calls by @sharmilarama in #224
- Enable unit test actions by @donatwork in #226
- Update offline installer to ignore comments in the manifests. by @rodrigobassil in #227
- Driver version bump up for CSM 1.12 by @WilsonRadadia20 in #228
- K8s and OCP version update by @WilsonRadadia20 in #230
- Added no cache buildAdded make target to build without cache by @francis-nijay in #229
- Call reusable action for go version updates by @shaynafinocchiaro in #231
- Update gobrick to latest commit by @AkshaySainiDell in #232
- Update go version to 1.23 by @csm-release in #234
- Update image references to quay.io by @suryagupta4 in #235
- Updated go.mod by @rishabhatdell in #236
New Contributors
- @donatwork made their first contribution in #226
- @rodrigobassil made their first contribution in #227
- @WilsonRadadia20 made their first contribution in #228
- @csm-release made their first contribution in #234
Full Changelog: v2.11.0...v2.12.0
Contributors
donatwork, shaynafinocchiaro, and 7 other contributors
Assets 2
Release v2.11.1
832b9da
This commit was signed with the committer’s verified signature.
The key has expired.
adarsh-dell
Adarsh Kumar Yadav
Full Changelog: v2.11.0...v2.11.1
Fixed Issues:
- Unity consistency update to reduce the number of authentication API calls. (#1415)
Release v2.11.0
Release Notes - CSI Unity XT v2.11.0
New Features/Changes
Fixed Issues
- #1198 - [BUG]: Topology-related node labels are not added automatically
- #1206 - [BUG]: Snapshot ingestion procedure for CSI Unity Driver misising
- #1209 - [BUG]: Doc hyper links in driver Readme is broken
- #1218 - [BUG]: Add the helm-charts-version parameter to the install command for all drivers in csm-docs
- #1222 - [BUG]: Cannot configure export IP for CSI-Unity
- #1239 - [BUG]: Changes in new release of google.golang.org/protobuf is causing compilation issues
- #1270 - [BUG]: Missing entries for Resiliency in installation wizard template
- #1279 - [BUG]: unable to install the UNITY driver in NAT Env
Known Issues
| Issue | Workaround |
|---|---|
| Nodes not getting registered on Unity XT. | Creating wrapper around hostname command inside the node pod's driver container, that fails when -I flag is used. This will triggrer fallback behaviour in driver and should fix the issue. |
| Topology-related node labels are not removed automatically. | Currently, when the driver is uninstalled, topology-related node labels are not getting removed automatically. There is an open issue in the Kubernetes to fix this. Until the fix is released, remove the labels manually after the driver un-installation using command kubectl label node <node_name> - - ... Example: kubectl label node csi-unity.dellemc.com/array123-iscsi- Note: there must be - at the end of each label to remove it. |
| NFS Clone - Resize of the snapshot is not supported by Unity XT Platform, however, the user should never try to resize the cloned NFS volume. | Currently, when the driver takes a clone of NFS volume, it succeeds but if the user tries to resize the NFS volumesnapshot, the driver will throw an error. |
| 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 |
| 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. |
A CSI ephemeral pod may not get created in OpenShift 4.13 and fail with the error "error when creating pod: the pod uses an inline volume provided by CSIDriver csi-unity.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. Therefore, an additional label security.openshift.io/csi-ephemeral-volume-profile in csidriver.yaml file with the required security profile value should be provided. Follow OpenShift 4.13 documentation for CSI Ephemeral Volumes for more information. |
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 Kubernetes at kubernetes/kubernetes#95911 with the same behavior. |
| fsGroupPolicy may not work as expected without root privileges for NFS only kubernetes/examples#260 | To get the desired behavior set “RootClientEnabled” = “true” in the storage class parameter |
| Controller publish is taking too long to complete/ Health monitoring is causing Unity array to panic by opening multiple sessions | Disable Volume health monitoring on the node and keep it only at the controller level. |
Note:
- Support for Kubernetes alpha features like Volume Health Monitoring will not be available in Openshift environment as Openshift doesn't support enabling of alpha features for Production Grade clusters.
Documentation
Release Notes
General Documentation
Change Log
See the CHANGELOG for more details.
Release v2.10.1
v2.10.1
This tag was signed with the committer’s verified signature.
suryagupta4
Surya Gupta
Release Notes - CSI Unity XT v2.10.1
New Features/Changes
- #1284 - [FEATURE]: Support for Openshift 4.15
- #1285 - [FEATURE]: Remove checks in code for non-supported installs of CSM
- #926 - [FEATURE]: Fixing the linting, formatting and vetting issues
Fixed Issues
- #1081 - [BUG]: CSM driver repositories reference CSI Operator
- #1140 - [BUG]: Cert-csi tests are not reporting the passed testcases in K8S E2E tests
- #1174 - [BUG]: Kubelet Configuration Directory setting should not have a comment about default value being None
Known Issues
| Issue | Workaround |
|---|---|
| Nodes not getting registered on Unity XT. | Creating wrapper around hostname command inside the node pod's driver container, that fails when -I flag is used. This will triggrer fallback behaviour in driver and should fix the issue. |
| Topology-related node labels are not removed automatically. | Currently, when the driver is uninstalled, topology-related node labels are not getting removed automatically. There is an open issue in the Kubernetes to fix this. Until the fix is released, remove the labels manually after the driver un-installation using command kubectl label node <node_name> - - ... Example: kubectl label node csi-unity.dellemc.com/array123-iscsi- Note: there must be - at the end of each label to remove it. |
| NFS Clone - Resize of the snapshot is not supported by Unity XT Platform, however the user should never try to resize the cloned NFS volume. | Currently, when the driver takes a clone of NFS volume, it succeeds but if the user tries to resize the NFS volumesnapshot, the driver will throw an error. |
| 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 |
| 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. |
A CSI ephemeral pod may not get created in OpenShift 4.13 and fail with the error "error when creating pod: the pod uses an inline volume provided by CSIDriver csi-unity.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. Therefore, an additional label security.openshift.io/csi-ephemeral-volume-profile in csidriver.yaml file with the required security profile value should be provided. Follow OpenShift 4.13 documentation for CSI Ephemeral Volumes for more information. |
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. |
| fsGroupPolicy may not work as expected without root privileges for NFS only kubernetes/examples#260 | To get the desired behavior set “RootClientEnabled” = “true” in the storage class parameter |
Note:
- Support for Kubernetes alpha features like Volume Health Monitoring and RWOP (ReadWriteOncePod) access mode will not be available in Openshift environment as Openshift doesn't support enabling of alpha features for Production Grade clusters.
Documentation
Release Notes
General Documentation
Change Log
See the CHANGELOG for more details.
Release v2.10.0
Release Notes - CSI Unity XT v2.10.0
New Features/Changes
Fixed Issues
Known Issues
| Issue | Workaround |
|---|---|
| Topology-related node labels are not removed automatically. | Currently, when the driver is uninstalled, topology-related node labels are not getting removed automatically. There is an open issue in the Kubernetes to fix this. Until the fix is released, remove the labels manually after the driver un-installation using command kubectl label node <node_name> - - ... Example: kubectl label node csi-unity.dellemc.com/array123-iscsi- Note: there must be - at the end of each label to remove it. |
| NFS Clone - Resize of the snapshot is not supported by Unity XT Platform, however the user should never try to resize the cloned NFS volume. | Currently, when the driver takes a clone of NFS volume, it succeeds but if the user tries to resize the NFS volumesnapshot, the driver will throw an error. |
| 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 |
| 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. |
A CSI ephemeral pod may not get created in OpenShift 4.13 and fail with the error "error when creating pod: the pod uses an inline volume provided by CSIDriver csi-unity.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. Therefore, an additional label security.openshift.io/csi-ephemeral-volume-profile in csidriver.yaml file with the required security profile value should be provided. Follow OpenShift 4.13 documentation for CSI Ephemeral Volumes for more information. |
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. |
Note:
- Support for Kubernetes alpha features like Volume Health Monitoring and RWOP (ReadWriteOncePod) access mode will not be available in Openshift environment as Openshift doesn't support enabling of alpha features for Production Grade clusters.
Documentation
Release Notes
General Documentation
Change Log
See the CHANGELOG for more details.
Release v2.9.1
Package update
Release v2.9.0
New Feature
- CSI 1.6 spec support (dell/csm#905)
- Support for Openshift 4.14. (dell/csm#1066)
- Support for Kubernetes 1.28. (dell/csm#947)
- Update to the latest UBI Micro image for CSM. (dell/csm#1031)
- Helm Chart Enhancement - Container Images Configurable in values.yaml. (dell/csm#851)
Documentation
Change Log
See the CHANGELOG for more details.
Release v2.8.0
New Features/Changes
- CSM support for Openshift 4.13
- CSI 1.5 spec support -StorageCapacityTracking
- Make standalone helm chart available from helm repository : https://dell.github.io/dell/helm-charts
- Enhancing Unity XT driver to handle API requests after the sessionIdleTimeOut in STIG mode
Fixed Issues
- CSI driver does not verify iSCSI initiators on the array correctly
- Remove references to deprecated io/ioutil package
Documentation
Change Log
See the CHANGELOG for more details.
Release v2.7.0
New Features/Changes
- Migrated image registry from k8s.gcr.io to registry.k8s.io
- Added support for OpenShift 4.12
- Added support for Kubernetes 1.27
- Added support for K3s on Debian OS
- Added support for Unisphere 5.3.0 array
Fixed Issues
There are no fixed issues in this release.
Documentation
Change Log
See the CHANGELOG for more details.