Release v1.7.0

What's Changed

• Fix yaml linter errors by @lukeatdell in #661
• update k8s version in e2e by @kumarkgosa in #662
• Support multiple vaults for authorization v2 by @shaynafinocchiaro in #656
• Bump openpolicyagent/kube-mgmt and redis images for Authorization by @shaynafinocchiaro in #663
• [feature-1281]: Merge Powerscale support to main for Authorization v2 by @atye in #664
• [feature-1281]: Update base CSM CRD and all CRDs with multiple Vault configuration by @atye in #666
• E2e brownfield fix by @francis-nijay in #657
• Authorization v2 update storage crd to have isiPath for PowerScale support by @alikdell in #665
• Use common workflows by @eric-young in #668
• Remove leftover files of old patch driver version by @chimanjain in #667
• Update released manifest by @shefali-malhotra in #671
• Added missing file for the Operator e2e tests by @OliverChen557 in #672
• Added OCP samples to reflect redhat registry and sha ids used for certification by @rajendraindukuri in #674
• Added make target to build without cache by @francis-nijay in #675
• Update CRD version from v1alpha1 to v1 by @harshitap26 in #670
• Added a --no-module flag to the Operator e2e tests by @arunbalaji-dell in #677
• operator version bump up by @nitesh3108 in #676
• Fixed k8s client unit test panic by @alexemc in #678
• Added support for minimal manifests by @harishp8889 in #685
• Add unity test e2e automation by @JacobGros in #684
• Update driver versions for 1.7.0 by @ashleyvjoy in #683
• Enabled reverse proxy by default by @harishp8889 in #686
• Minimal CR for resiliency by @adarsh-dell in #691
• Minimal manifest changes for the authorization module by @meggm in #687
• Fix --no-modules on e2e tests by @JacobGros in #689
• Add e2e for PowerStore minimal sample by @suryagupta4 in #690
• Add OTEL Collector configuration to Authorization storage-service by @atye in #692
• Use correct image in deploy/operator.yaml by @atye in #694
• storage capacity update by @nitesh3108 in #693
• Added support for resiliency module with minimal manifest by @harishp8889 in #695
• Enables resiliency module for powerscale in the minimal manifest file by @meggm in #696
• Updated kube-rbac-proxy image to the one packaged by Redhat by @rajendraindukuri in #697
• Enables resiliency module for powerflex driver in the minimal manifes… by @meggm in #700
• Minimal manifest changes for Drivers by @mgandharva in #711
• Minimal manifest changes for powermax with authorization module by @mgandharva in #710
• Support auth module in pflex minimal CR by @ashleyvjoy in #702
• Add PowerScale Auth 2.0 E2E Test by @falfaroc in #698
• Adding E2E tests for Powermax Authorization 2.0 by @harshitap26 in #701
• Make SDC optional for powerflex deployment by @xuluna in #703
• Update Controller Runtime, SDK and k8s modules by @HarishH-DELL in #707
• SystemID Changes for Authorization E2E by @harshitap26 in #712
• [KRV-28207] Add csm-auth clusterrole prefix by @EvgenyUglov in #714
• Call reusable action for go version updates by @shaynafinocchiaro in #715
• E2E for CSI-Unity driver with minimal CR by @adarsh-dell in #713
• Minimal manifest for Powermax with authorization 2.0 by @mgandharva in #720
• Added support for replication with minimal manifest by @harishp8889 in #723
• Add Resileincy Tolerations by @satyakonduri in #726
• Add support for Observability with minimal manifest by @AkshaySainiDell in #725
• Readme change pmax + pstore by @arnavmohan0201 in #730
• Adding Interfaces for disabling SDC dependency on Powerflex NFS Volumes by @xuluna in #727
• [bug-1502]: Add csi-ephemeral-volume-profile label to CSIDriver by @atye in #731
• Module and Sidecar version update for CSM-Operator by @mgandharva in #724
• E2E tests for powerflex driver in the minimal manifest file by @meggm in #719
• Added support for replication with minimal manifest by @WilsonRadadia20 in #732
• E2E tests for powerflex driver in the minimal manifest file by @meggm in #736
• CSI powermax reverseproxy version update by @mgandharva in #734
• Added deployAsSidecar for reversproxy as default for minimal manifests by @harishp8889 in #735
• E2E for Pscale driver with modules by @adarsh-dell in #729
• Fix the powerflex driver deployment issue by @ashleyvjoy in #737
• E2E tests for powerflex driver in the minimal manifest file by @meggm in #739
• Updating published images to OCP 1.6.1 samples by @rajendraindukuri in #738
• E2E Fixes + ACC Removal by @ChristianAtDell in #744
• E2E tests fix for Pflex driver in minimal manifest file by @meggm in #748
• Add support of observability in minimal manifest for powermax by @AkshaySainiDell in #733
• Fix PowerMax E2E by @ChristianAtDell in #746
• E2E for CSI-PowerMax driver with minimal CR by @suryagupta4 in #749
• Add UT for utils pkg by @AkshaySainiDell in #751
• Bugfix/reverseproxy by @harishp8889 in #752
• Add coordination.k8s.io apiGroups access for observability and update nginx image by @chimanjain in #747
• Updating latest image references to quay.io by @ashleyvjoy in #750
• E2E tests for PMax driver in minimal manifest file Auth v1 and Auth v2 by @meggm in #753
• Update go version to 1.23 by @csm-release in #756
• Add toolchain version to tests/e2e/go.mod by @enestvedto-dell in #758
• Fix CSM Operator Continually Adding Components to Observability by @JacobGros in #757
• Add Auth module default values to minimal sample files by @meggm in #761
• Operator E2E script fix by @meggm in #763
• Fix dell-replication-controller-config reconcile reset issue by @ChristianAtDell in #760
• update image path to quay by @ashleyvjoy in #762
• Version updated to nightly by @mgandharva in #759
• Am e2e fixes by @anathoodell in #764
• app mobility version bump up changes by @gilltaran in #765
• Add private mount for PowerFlex /disks path. by @donatwork in #766
• Update bundle.Dockerfile file for the supported openshift lower bound(n-3) version by @ashleyvjoy in #767
• Updated nightly versions to CSM 1.12 image tags by @rajendraindukuri in #768

New Contributors

• @lukeatdell made their first contribution in #661
• @eric-young made their first contribution in #668
• @OliverChen557 made their first contribution in #672
• @arunbalaji-dell made their first contribution in #677
• @alexemc made their first contribution in https://github.com/dell/csm-operator/p...

Release v1.6.1

What's Changed

• 1415 - [FEATURE]: Unity consistency update to reduce the number of authentication API calls

Fixed Issues

• 1469 - [BUG]: Mounts using NVMe on PowerStore fails in v2.11 of the driver
• 1482 - [BUG]: SDC 4.5.2.1 fails to load when deployed on OCP 4.16.x using csm-operator
  Note: To get the latest 4.5.2.1 SDC image, ImagePullPolicy for the dellemc/sdc:4.5.2.1 image will have to be set to Always.

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

v1.6.0

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

v1.5.1

What's Changed

• Initial patch-v1.10.2 updates by @nitesh3108 in #552
• Update Driver Sample Files and modules for Patch 1.10.2 by @chimanjain in #558
• Cherry picking security fixes and other commits that needs to be part of patch release by @rajendraindukuri in #562
• metadata retriever sidecar update by @nitesh3108 in #566
• Updated final manifests by @rajendraindukuri in #574

Full Changelog: v1.5.0...v1.5.1

v1.5.0

Release Notes - Container Storage Modules Operator v1.5.0

New Features/Changes

• #926 - [FEATURE]: Fixing the linting, formatting and vetting issues
• #1088 - [FEATURE]:Support for Kubernetes 1.29

Fixed Issues

• #1094 - [BUG]: CSM Operator offline install powerflex csi driver sidecar trying to pull from registry.k8s.io

Known Issues

• 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>

v1.4.4

Release Notes - Dell Container Storage Modules Operator 1.4.4

Fixed Issues

• Change the Apex Connectivity Client access to the kube-proxy port to only connections within the client pod. (#1189)
• Change Apex Connectivity Client access to secrets to only the secrets it needs to manage. (#1190)

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.

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.

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.

Release v1.4.1

Release Notes - Dell Container Storage Modules Operator 1.4.1

New Features/Changes

Fixed Issues

• Allow volume prefix to be set via CSM operator
• X_CSI_AUTH_TYPE cannot be set in CSM Operator
• Multi Controller defect - sidecars timeout
• Operator crashes when deployed from OpenShift with OLM
• Skip Certificate Validation is not propagated to Authorization module in CSM Operator
• CSM Operator does not calculate status correctly when module is deployed with driver

Known Issues

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 registry.k8s.io.

Documentation

• Container Storage Modules Operator Documentation
• General Documentation

Change Log

See the CHANGELOG for more details.

Release v1.4.0

Release Notes - Dell Container Storage Modules Operator 1.4.0

New Features/Changes

• K8s 1.28 support
• Support for Openshift 4.14
• Dell CSI to Dell CSM Operator Migration Process
• CSM PowerMax: Support PowerMax v10.1

Fixed Issues

• CSM Operator fails to install CSM Replication on the remote cluster
• Allow volume prefix to be set via CSM operator
• X_CSI_AUTH_TYPE cannot be set in CSM Operator
• Not able to take volumesnapshots
• Update resources limits for controller-manager to fix OOMKilled error

Known Issues

There are no known issues in this release.