PowerMax
Release Notes - CSI PowerMax v2.7.0
Linked Proxy mode for CSI reverse proxy is no longer actively maintained or supported. It will be deprecated in CSM 1.9. It is highly recommended that you use stand alone mode going forward.
Note: Starting from CSI v2.4.0, Only Unisphere 10.0 REST endpoints are supported. It is mandatory that Unisphere should be updated to 10.0. Please find the instructions here.
New Features/Changes
- Added support for OpenShift 4.12
- Added support for PowerMax v10.0.1 array
- Migrated image registry from k8s.gcr.io to registry.k8s.io
- Added support for Amazon EKS Anywhere
- Added support for Kubernetes 1.27
- Added support for read only mount option for block volumes
- Added support for host groups for vSphere environment
- Added support to delete volumes on target array when it is set to Delete in storage class
- Added support for setting up QoS parameters for throttling performance and bandwidth at Storage Group level
- Added support for CSM Operator for PowerMax Driver
- Added support to create reverseproxy certs automatically
Fixed Issues
There are no fixed issues in this release.
Known Issues
| Issue | Workaround |
|---|---|
| Unable to update Host: A problem occurred modifying the host resource | This issue occurs when the nodes do not have unique hostnames or when an IP address/FQDN with same sub-domains are used as hostnames. The workaround is to use unique hostnames or FQDN with unique sub-domains |
| 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 https://github.com/kubernetes-csi/external-attacher/issues/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 the driver is installed using CSM Operator , few times, pods created using block volume are getting stuck in containercreating/terminating state or devices are not available inside the pod. | Update the daemonset with parameter mountPropagation: "Bidirectional" for volumedevices-path under volumeMounts section. |
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.