v1.6.0
·
98 commits
to main
since this release
What's Changed
- 1359 - [FEATURE]: Add Support for OpenShift Container Platform (OCP) 4.16
- 1277 - [FEATURE]: Add Authorization upgrade is supported in CSM Operator
- 1396 - [FEATURE]: DCM and DN client upgrade is supported in CSM operator
- 1397 - [FEATURE]: Observability upgrade is supported in CSM Operator
Fixed Issues
- 1200 - [BUG]: CrashLoopBackOff and OOMKilled issue in pod : Dell CSM Operator Manager POD
- 1205 - [BUG]: Operator doesn't support non-authorization namespace
- 1220 - [BUG]: Issue while Configuring Authorization module with Powermax CSI Driver using Operator
- 1238 - [BUG]: Missing mountPropagation param for Powermax node template in CSM-Operator
- 1291 - [BUG]: Fix linter errors in csm-operator
Known Issues
| Issue | Workaround |
|---|---|
| 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 |
| In certain environments, users have encountered difficulties in installing drivers using the CSM Operator due to the 'OOM Killed' issue. This issue is attributed to the default resource requests and limits configured in the CSM Operator, which fail to meet the resource requirements of the user environments. OOM error occurs when a process in the container tries to consume more memory than the limit specified in resource configuration. | Before deploying the CSM Operator, it is crucial to adjust the memory and CPU requests and limits in the files config/manager.yaml, deploy/operator.yaml to align with the user's environment requirements. If the containers running on the pod exceed the specified CPU and memory limits, the pod may get evicted. Currently CSM Operator do not support updating this configuration dynamically. CSM Operator needs to be redeployed for these updates to take effect in case it is already installed. Steps to manually update the resource configuration and then redeploy CSM Operator are available here |