Release v1.4.2

Release Notes - Dell Container Storage Modules Operator 1.4.2

Fixed Issues

• CSM Operator does not calculate status correctly when application-mobility is deployed by itself
• CSM Operator intermittently does not calculate status correctly when deploying a driver
• CSM Operator labels csm objects with CSMVersion 1.8.0, an old version
• CSM Operator doesn't apply fSGroupPolicy value to CSIDriver Object.
• CSM Operator does not calculate status correctly when a driver is deployed by itself.
• CSM Operator does not calculate status correctly when deploying the authorization proxy server.
• CSM Operator does not calculate status correctly when deploying observability with csi-powerscale.

Known Issues

• The status field of a csm object as deployed by CSM Operator may, in limited cases, display a "Failed" status for a successful deployment. As a workaround, the deployment is still usable as long as all pods are running/healthy.
• The status calculation done for the csm object associated with the Authorization Proxy Server when deployed with CSM Operator assumes that the proxy server will be deployed in the "authorization" namespace. If a different namespace is used, the status will stay in the failed state, even though the deployment is healthy. As a workaround, we recommend using the "authorization" namespace for the proxy server. If this is not possible, the health of the deployment can be verified by checking the status of all the pods rather than by checking the status field.

Documentation

• Container Storage Modules Operator Documentation
• General Documentation

Change Log

See the CHANGELOG for more details.