Release notes

Release Notes - Container Storage Modules Operator v1.4.2

New Features/Changes

Fixed Issues

Known Issues

Issue Workaround
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. 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.
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 images of sideCars are currently missing in the sample YAMLs in the offline bundle. As a consequence, the csm-operator is pulling them from We recommend manually updating the images of sideCars in the sample YAML file, for example, storage_csm_powerflex_v291.yaml, before proceeding with the driver installation. Here is an example snippet for the sideCars section in the YAML file:
  # 'k8s' represents a string prepended to each volume created by the CSI driver
  - name: provisioner
    image: <localregistry>/csi-provisioner:v3.6.2
    args: ["--volume-name-prefix=k8s"]
  - name: attacher
    image: <localregistry>/csi-attacher:v4.4.2
  - name: registrar
    image: <localregistry>/csi-node-driver-registrar:v2.9.1
  - name: resizer
    image: <localregistry>/csi-resizer:v1.9.2
  - name: snapshotter
    image: <localregistry>/csi-snapshotter:v6.3.2

  # sdc-monitor is disabled by default, due to high CPU usage
  - name: sdc-monitor
    enabled: false
    image: <localregistry>/sdc:4.5
      - name: HOST_PID
        value: "1"
      - name: MDM
        value: "10.xx.xx.xx,10.xx.xx.xx" # Do not add mdm value here if it is present in secret

  # health monitor is disabled by default, refer to driver documentation before enabling it
  # Also set the env variable controller.envs.X_CSI_HEALTH_MONITOR_ENABLED to "true".
  - name: csi-external-health-monitor-controller
    enabled: false
    image: <localregistry>/csi-external-health-monitor-controller:v0.10.0
    args: ["--monitor-interval=60s"]