- With CSI PowerStore, when a PV/PVC is deleted in Kubernetes, it triggers the deletion of the underlying volume and snapshot on the array as a default behaviour. This results in a situation where the VolumeSnapshot and VolumeSnapshotContent will still show "readyToUse: true", but leaves them unusable as it is no longer backed by underlying storage snapshot. This will not allow the creation of a PVC from snapshot and this could also lead to a data loss situations. The workaround is use of retain policy on the various PV, VolumeSnapshot and VolumeSnapshotContent that you wish to use for cloning.
- 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.
- CSM Operator does not support dynamic namespaces for Authorization. Despite successful installation in a namespace other than "authorization", errors may arise during volume creation. Use the default namespace “authorization” for installing Authorization using CSM Operator.
- With CSI PowerStore, when a PV/PVC is deleted in Kubernetes, it triggers the deletion of the underlying volume and snapshot on the array as a default behaviour. This results in a situation where the VolumeSnapshot and VolumeSnapshotContent will still show "readyToUse: true", but leaves them unusable as it is no longer backed by underlying storage snapshot. This will not allow the creation of a PVC from snapshot and this could also lead to a data loss situations. The workaround is use of retain policy on the various PV, VolumeSnapshot and VolumeSnapshotContent that you wish to use for cloning.
- Helm deployment of PowerFlex driver is failing (#1210)
- 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.
- CSM Operator does not support dynamic namespaces for Authorization. Despite successful installation in a namespace other than "authorization", errors may arise during volume creation. Use the default namespace “authorization” for installing Authorization using CSM Operator.
- Helm install of CSM for PowerFlex v1.10.0 is failing due to a duplicate
mountPath: /host_opt_emc_pathbeing added to volumeMounts charts/csi-vxflexos/templates/node.yaml. Error message isError: 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. - With CSI PowerStore, when a PV/PVC is deleted in Kubernetes, it triggers the deletion of the underlying volume and snapshot on the array as a default behaviour. This results in a situation where the VolumeSnapshot and VolumeSnapshotContent will still show "readyToUse: true", but leaves them unusable as it is no longer backed by underlying storage snapshot. This will not allow the creation of a PVC from snapshot and this could also lead to a data loss situations. The workaround is use of retain policy on the various PV, VolumeSnapshot and VolumeSnapshotContent that you wish to use for cloning.
- CSM 1.10 release specific changes. (#1091)
- Fixing the linting, formatting and vetting issues. (#926)
- Support PowerStore v3.6. (#1129)
- Sample YAML for storage class creation missing in CSM Operator documentation. (#1105)
- Driver install should not be part of Operator installation. (#1186)
- Resource quota bypass. (#1163)
- Operator known issue for offline bundle sidecar images should have examples for all platforms. (#1180)
- PowerMax : Metro: Failed to find Remote Symm WWN. (#1175)
- Kubelet Configuration Directory setting should not have a comment about default value being None. (#1174)
- Documentation : Multipath related instructions are missing in Powerstore prerequisites. (#1142)
- Cert-csi tests are not reporting the passed testcases in K8S E2E tests. (#1140)
- PowerScale : Driver failing to re-authenticate if session cookies are expired. (#1134)
- Inactive Tutorials button. (#1121)
- CSI Powermax: Driver fails to restore snapshot to Metro Volumes. (#1115)
- The csm-isilon-controller keeps getting panic and is restarting. (#1104)
- the
nasNameparameter in the powerflex secret is now mandatory. (#1101) - Powerstore sanity tests are not working. (#1097)
- CSM Operator offline install powerflex csi driver sidecar trying to pull from registry.k8s.io. (#1094)
- PowerFlex driver fails to start on RKE. (#1086)
- Gopowerstore - Multiple issues in mockfile. (#1084)
- CSM driver repositories reference CSI Operator. (#1081)