Release v2.12.0

What's Changed

• update k8s version in e2e go.mod by @kumarkgosa in #323
• Codeowners update 20240821 by @donatwork in #324
• Update offline installer to ignore comments in the manifests. by @rodrigobassil in #326
• Reusable workflows by @eric-young in #325
• Driver version bump up for CSM 1.12 by @adarsh-dell in #327
• Added no cache buildAdded make target to build without cache by @francis-nijay in #329
• Bump github.com/opencontainers/runc from 1.1.12 to 1.1.14 in /test/e2e-fsgroup by @dependabot in #328
• K8s and OCP version update by @WilsonRadadia20 in #331
• Call reusable action for go version updates by @shaynafinocchiaro in #333
• Disabling SDC dependency for NFS Volume Provisioning by @harshitap26 in #330
• Integration tests for NFS Volume Provisioning without SDC by @harshitap26 in #334
• Refactor code for updating config map by @sakshi-garg1 in #335
• E2E FSGroup Test Fix by @rishabhatdell in #336
• Update go version to 1.23.2 by @csm-release in #337
• Update go version to 1.23 by @csm-release in #338
• Bump go.opentelemetry.io/contrib/instrumentation/github.com/emicklei/go-restful/otelrestful from 0.42.0 to 0.44.0 in /test/e2e-fsgroup by @dependabot in #339
• Update image references to quay.io by @suryagupta4 in #340
• Fix private target unmount issue in NodeUnpublishVolume by @AkshaySainiDell in #342
• Bump github.com/opencontainers/runc from 1.1.13 to 1.1.14 in /test/e2e-fsgroup by @dependabot in #341
• Updated go.mod by @rishabhatdell in #343

New Contributors

• @kumarkgosa made their first contribution in #323
• @donatwork made their first contribution in #324
• @rodrigobassil made their first contribution in #326
• @francis-nijay made their first contribution in #329
• @WilsonRadadia20 made their first contribution in #331
• @harshitap26 made their first contribution in #330
• @sakshi-garg1 made their first contribution in #335
• @csm-release made their first contribution in #337

Full Changelog: v2.11.0...v2.12.0

Release v2.11.0

Release Notes - CSI PowerFlex v2.11.0

New Features/Changes

• #1359 - [FEATURE]: Add Support for OpenShift Container Platform (OCP) 4.16
• #1400 - [FEATURE]: Support for Kubernetes 1.30
• #1358 - [FEATURE]: Support for PowerFlex 4.6
• #1397 - [FEATURE]: Observability upgrade is supported in CSM Operator

Fixed Issues

• #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
• #1237 - [BUG]: Error handling not good in node.go:nodeProbe() and other similar functions
• #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
• #1310 - [BUG]: CSI node pod crash after replacing OCP ingress certificate or restarting kubectl service
• #1350 - [BUG]: Document update : PowerFlex expecting secret CR as -config in operator
• #1355 - [BUG]: Indentation of secret.yaml mentioned on the csm-doc portal for powerflex driver is incorrect.
• #1364 - [BUG]: mkfsFormatOption not working for powerflex
• #1366 - [BUG]: Support Minimum 3GB Volume Size for NFS in CSI-PowerFlex

Known Issues

Issue	Workaround
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.
sdc:3.6.0.6 is causing issues while installing the csi-powerflex driver on ubuntu,RHEL8.3	Workaround: Change the powerflexSdc to sdc:3.6 in values.yaml https://github.com/dell/csi-powerflex/blob/72b27acee7553006cc09df97f85405f58478d2e4/helm/csi-vxflexos/values.yaml#L13
sdc:3.6.1 is causing issues while installing the csi-powerflex driver on ubuntu.	Workaround: Change the powerflexSdc to sdc:3.6 in values.yaml https://github.com/dell/csi-powerflex/blob/72b27acee7553006cc09df97f85405f58478d2e4/helm/csi-vxflexos/values.yaml#L13
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-vxflexos.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.
The PowerFlex Dockerfile is incorrectly labeling the version as 2.7.0 for the 2.8.0 version.	Describe the driver pod using kubectl describe pod $podname -n vxflexos to ensure v2.8.0 is installed.
Resource quotas may not work properly with the CSI PowerFlex driver. PowerFlex is only able to assign storage in 8Gi chunks, so if a create volume call is made with a size not divisible by 8Gi, CSI-PowerFlex will round up to the next 8Gi boundary when it provisions storage -- however, the resource quota will not record this size but rather the original size in the create request. This means that, for example, if a 10Gi resource quota is set, and a user provisions 10 1Gi PVCs, 80Gi of storage will actually be allocated, which is well over the amount specified in the resource quota.	For now, users should only provision volumes in 8Gi-divisible chunks if they want to use resource quotas.
Helm install of CSM for PowerFlex v1.10.0 is failing due to a duplicate mountPath: /host_opt_emc_path being added to volumeMounts charts/csi-vxflexos/templates/node.yaml. Error message is Error: INSTALLATION FAILED: 1 error occurred: DaemonSet.apps "vxflexos-node" is invalid: spec.template.spec.initContainers[0].volumeMounts[4].mountPath: Invalid value: "/host_opt_emc_path": must be unique	The issue can be resolved by removing the duplicate entry in https://github.com/dell/helm-charts/blob/main/charts/csi-vxflexos/templates/node.yaml

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.
• For fixing #1210 - [BUG]: Helm deployment of PowerFlex driver is failing, a new helm-chart has been released. In order to install this helm chart, we need to pass the flag --helm-charts-version during helm installation and flag -v during offline bundle installation with value csi-vxflexos-2.11.0.

Documentation

Release Notes
General Documentation

Change Log

See the CHANGELOG for more details.

Release v2.10.1

Release Notes - CSI PowerFlex 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
• #1086 - [BUG]: PowerFlex driver fails to start on RKE
• #1101 - [BUG]: the nasName parameter in the powerflex secret is now mandatory
• #1140 - [BUG]: Cert-csi tests are not reporting the passed testcases in K8S E2E tests
• #1163 - [BUG]: Resource quota bypass
• #1174 - [BUG]: Kubelet Configuration Directory setting should not have a comment about default value being None
• #1210 - [BUG]: Helm deployment of PowerFlex driver is failing

Known Issues

Issue	Workaround
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.
sdc:3.6.0.6 is causing issues while installing the csi-powerflex driver on ubuntu,RHEL8.3	Workaround: Change the powerflexSdc to sdc:3.6 in values.yaml https://github.com/dell/csi-powerflex/blob/72b27acee7553006cc09df97f85405f58478d2e4/helm/csi-vxflexos/values.yaml#L13
sdc:3.6.1 is causing issues while installing the csi-powerflex driver on ubuntu.	Workaround: Change the powerflexSdc to sdc:3.6 in values.yaml https://github.com/dell/csi-powerflex/blob/72b27acee7553006cc09df97f85405f58478d2e4/helm/csi-vxflexos/values.yaml#L13
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-vxflexos.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.
The PowerFlex Dockerfile is incorrectly labeling the version as 2.7.0 for the 2.8.0 version.	Describe the driver pod using kubectl describe pod $podname -n vxflexos to ensure v2.8.0 is installed.
Resource quotas may not work properly with the CSI PowerFlex driver. PowerFlex is only able to assign storage in 8Gi chunks, so if a create volume call is made with a size not divisible by 8Gi, CSI-PowerFlex will round up to the next 8Gi boundary when it provisions storage -- however, the resource quota will not record this size but rather the original size in the create request. This means that, for example, if a 10Gi resource quota is set, and a user provisions 10 1Gi PVCs, 80Gi of storage will actually be allocated, which is well over the amount specified in the resource quota.	For now, users should only provision volumes in 8Gi-divisible chunks if they want to use resource quotas.
Helm install of CSM for PowerFlex v1.10.0 is failing due to a duplicate mountPath: /host_opt_emc_path being added to volumeMounts charts/csi-vxflexos/templates/node.yaml. Error message is Error: INSTALLATION FAILED: 1 error occurred: DaemonSet.apps "vxflexos-node" is invalid: spec.template.spec.initContainers[0].volumeMounts[4].mountPath: Invalid value: "/host_opt_emc_path": must be unique	The issue can be resolved by removing the duplicate entry in https://github.com/dell/helm-charts/blob/main/charts/csi-vxflexos/templates/node.yaml

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.
• For fixing #1210 - [BUG]: Helm deployment of PowerFlex driver is failing, a new helm-chart has been released. In order to install this helm chart, we need to pass the flag --helm-charts-version during helm installation and flag -v during offline bundle installation with value csi-vxflexos-2.10.1.

Documentation

Release Notes
General Documentation

Change Log

See the CHANGELOG for more details.

Release v2.10.0

Release Notes - CSI PowerFlex v2.10.0

New Features/Changes

• #926 - [FEATURE]: Fixing the linting, formatting and vetting issues

Fixed Issues

• #1081 - [BUG]: CSM driver repositories reference CSI Operator
• #1086 - [BUG]: PowerFlex driver fails to start on RKE
• #1101 - [BUG]: the nasName parameter in the powerflex secret is now mandatory
• #1103 - [BUG]: CSM Operator doesn't apply fSGroupPolicy value to CSIDriver Object
• #1138 - [BUG]: nasName setting is said optional but is mandatory from the driver

Known Issues

Issue	Workaround
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.
sdc:3.6.0.6 is causing issues while installing the csi-powerflex driver on ubuntu,RHEL8.3	Workaround: Change the powerflexSdc to sdc:3.6 in values.yaml https://github.com/dell/csi-powerflex/blob/72b27acee7553006cc09df97f85405f58478d2e4/helm/csi-vxflexos/values.yaml#L13
sdc:3.6.1 is causing issues while installing the csi-powerflex driver on ubuntu.	Workaround: Change the powerflexSdc to sdc:3.6 in values.yaml https://github.com/dell/csi-powerflex/blob/72b27acee7553006cc09df97f85405f58478d2e4/helm/csi-vxflexos/values.yaml#L13
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-vxflexos.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.
The PowerFlex Dockerfile is incorrectly labeling the version as 2.7.0 for the 2.8.0 version.	Describe the driver pod using kubectl describe pod $podname -n vxflexos to ensure v2.8.0 is installed.
Resource quotas may not work properly with the CSI PowerFlex driver. PowerFlex is only able to assign storage in 8Gi chunks, so if a create volume call is made with a size not divisible by 8Gi, CSI-PowerFlex will round up to the next 8Gi boundary when it provisions storage -- however, the resource quota will not record this size but rather the original size in the create request. This means that, for example, if a 10Gi resource quota is set, and a user provisions 10 1Gi PVCs, 80Gi of storage will actually be allocated, which is well over the amount specified in the resource quota.	For now, users should only provision volumes in 8Gi-divisible chunks if they want to use resource quotas.

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.2

Release Notes - CSI PowerFlex v2.9.2

New Features/Changes

Fixed Issues

• #1152 - [BUG]: CSI driver changes to facilitate SDC brownfield deployments)

Known Issues

Issue	Workaround
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.
sdc:3.6.0.6 is causing issues while installing the csi-powerflex driver on ubuntu,RHEL8.3	Workaround: Change the powerflexSdc to sdc:3.6 in values.yaml https://github.com/dell/csi-powerflex/blob/72b27acee7553006cc09df97f85405f58478d2e4/helm/csi-vxflexos/values.yaml#L13
sdc:3.6.1 is causing issues while installing the csi-powerflex driver on ubuntu.	Workaround: Change the powerflexSdc to sdc:3.6 in values.yaml https://github.com/dell/csi-powerflex/blob/72b27acee7553006cc09df97f85405f58478d2e4/helm/csi-vxflexos/values.yaml#L13
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-vxflexos.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.
The PowerFlex Dockerfile is incorrectly labeling the version as 2.7.0 for the 2.8.0 version.	Describe the driver pod using kubectl describe pod $podname -n vxflexos to ensure v2.8.0 is installed.

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

Release Notes - CSI PowerFlex v2.9.1

New Features/Changes

Fixed Issues

• #1110 - [BUG]: Multi Controller defect - sidecars timeout

Known Issues

Issue	Workaround
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.
sdc:3.6.0.6 is causing issues while installing the csi-powerflex driver on ubuntu,RHEL8.3	Workaround: Change the powerflexSdc to sdc:3.6 in values.yaml https://github.com/dell/csi-powerflex/blob/72b27acee7553006cc09df97f85405f58478d2e4/helm/csi-vxflexos/values.yaml#L13
sdc:3.6.1 is causing issues while installing the csi-powerflex driver on ubuntu.	Workaround: Change the powerflexSdc to sdc:3.6 in values.yaml https://github.com/dell/csi-powerflex/blob/72b27acee7553006cc09df97f85405f58478d2e4/helm/csi-vxflexos/values.yaml#L13
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-vxflexos.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.
The PowerFlex Dockerfile is incorrectly labeling the version as 2.7.0 for the 2.8.0 version.	Describe the driver pod using kubectl describe pod $podname -n vxflexos to ensure v2.8.0 is installed.

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.0

Release Notes - CSI PowerFlex v2.9.0

New Features/Changes

• #851 - [FEATURE]: Helm Chart Enhancement - Container Images Configurable in values.yaml
• #947 - [FEATURE]: K8s 1.28 support
• #1066 - [FEATURE]: Support for Openshift 4.14
• #905 - [FEATURE]: Add support for CSI Spec 1.6
• #996 - [FEATURE]: Dell CSI to Dell CSM Operator Migration Process

Fixed Issues

• #1011 - [BUG]: PowerFlex RWX volume no option to configure the nfs export host access ip address.
• #1014 - [BUG]: Missing error check for os.Stat call during volume publish
• #1020 - [BUG]: CSI-PowerFlex: SDC Rename fails when configuring multiple arrays in the secret
• #1030 - [BUG]: Comment out duplicate entries in the sample secret.yaml file
• #1050 - [BUG]: NFS Export gets deleted when one pod is deleted from the multiple pods consuming the same PowerFlex RWX NFS volume
• #1054 - [BUG]: The PowerFlex Dockerfile is incorrectly labeling the version as 2.7.0 for the 2.8.0 version.
• #1058 - [BUG]: CSI Health monitor for Node missing for CSM PowerFlex in Operator samples
• #1061 - [BUG]: Golint is not installing with go get command

Known Issues

Issue	Workaround
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.
sdc:3.6.0.6 is causing issues while installing the csi-powerflex driver on ubuntu,RHEL8.3	Workaround: Change the powerflexSdc to sdc:3.6 in values.yaml https://github.com/dell/csi-powerflex/blob/72b27acee7553006cc09df97f85405f58478d2e4/helm/csi-vxflexos/values.yaml#L13
sdc:3.6.1 is causing issues while installing the csi-powerflex driver on ubuntu.	Workaround: Change the powerflexSdc to sdc:3.6 in values.yaml https://github.com/dell/csi-powerflex/blob/72b27acee7553006cc09df97f85405f58478d2e4/helm/csi-vxflexos/values.yaml#L13
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-vxflexos.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.8.0

Release Notes - CSI PowerFlex v2.8.0

New Features/Changes

• #724 - [FEATURE]: CSM support for Openshift 4.13
• #763 - [FEATURE]: CSI-PowerFlex 4.0 NFS support
• #876 - [FEATURE]: CSI 1.5 spec support -StorageCapacityTracking
• #878 - [FEATURE]: CSI 1.5 spec support: Implement Volume Limits
• #885 - [FEATURE]: SDC 3.6.1 support

Fixed Issues

• #916 - [BUG]: Remove references to deprecated io/ioutil package

Known Issues

Issue	Workaround
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.
sdc:3.6.0.6 is causing issues while installing the csi-powerflex driver on ubuntu,RHEL8.3	Workaround: Change the powerflexSdc to sdc:3.6 in values.yaml https://github.com/dell/csi-powerflex/blob/72b27acee7553006cc09df97f85405f58478d2e4/helm/csi-vxflexos/values.yaml#L13
sdc:3.6.1 is causing issues while installing the csi-powerflex driver on ubuntu.	Workaround: Change the powerflexSdc to sdc:3.6 in values.yaml https://github.com/dell/csi-powerflex/blob/72b27acee7553006cc09df97f85405f58478d2e4/helm/csi-vxflexos/values.yaml#L13
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.7.1

Release Notes - CSI PowerFlex v2.7.1

New Features/Changes

Posting the image with latest go version.

Fixed Issues

There are no fixed issues in this release.

Known Issues

Issue	Workaround
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.
sdc:3.6.0.6 is causing issues while installing the csi-powerflex driver on ubuntu,RHEL8.3	Workaround: Change the powerflexSdc to sdc:3.6 in values.yaml https://github.com/dell/csi-powerflex/blob/72b27acee7553006cc09df97f85405f58478d2e4/helm/csi-vxflexos/values.yaml#L13

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.

• The CSI-PowerFlex v2.7.1 is applicable only for helm based installations.

Documentation

Release Notes
General Documentation

Change Log

See the CHANGELOG for more details.

Release v2.7.0

Release Notes - CSI PowerFlex v2.7.0

New Features/Changes

• K8 1.27 support added.
• OCP 4.12 support added

Fixed Issues

• Fix the offline installation failure

Known Issues

Issue	Workaround
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.
sdc:3.6.0.6 is causing issues while installing the csi-powerflex driver on ubuntu,RHEL8.3	Workaround: Change the powerflexSdc to sdc:3.6 in values.yaml https://github.com/dell/csi-powerflex/blob/72b27acee7553006cc09df97f85405f58478d2e4/helm/csi-vxflexos/values.yaml#L13

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.