v1.4.3

Release Notes - Dell Container Storage Modules Operator 1.4.3

Features

• Automatically create certificates when deploying observability with csm-operator

Fixed Issues

• CSM object stays in success state when all CSI Powerflex pods are failing due to bad secret credentials
• If Authorization Proxy Server is installed in an alternate namespace by CSM Operator, the deployment fails
• CSM status is not always accurate when Observability is deployed by CSM Operator without all components enabled
• CSM object occasionally stays in failed state when app-mobility is successfully deployed with csm-operator

Known Issues

• The status field of a csm object as deployed by CSM Operator may, in limited cases, display an incorrect status for a deployment. As a workaround, the health of the deployment can be determined by checking the health of the pods.
• When CSM Operator creates a deployment that includes secrets (e.g., application-mobility, observability, cert-manager, velero), these secrets are not deleted on uninstall and will be left behind. For example, the karavi-topology-tls, otel-collector-tls, and cert-manager-webhook-ca secrets will not be deleted. This should not cause any issues on the system, but all secrets present on the cluster can be found with kubectl get secrets -A, and any unwanted secrets can be deleted with kubectl delete secret -n <secret-namespace> <secret-name>

Documentation

• Container Storage Modules Operator Documentation
• General Documentation

Change Log

See the CHANGELOG for more details.