Dell Technologies on

Authorization v1.x

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.
As of Container Storage Modules v1.15, Authorization v1.x will not be supported. Please migrate to Authorization v2.0 using the following guide.

Install CSM Authorization via Container Storage Modules Operator

Prerequisite

Execute kubectl create namespace authorization to create the authorization namespace (if not already present). Note that the namespace can be any user-defined name, in this example, we assume that the namespace is ‘authorization’.

Authorization v1.x

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.
As of Container Storage Modules v1.15, Authorization v1.x will not be supported. Please migrate to Authorization v2.0 using the following guide.

Container Storage Modules Authorization can be installed by using the provided Helm v3 charts on Kubernetes platforms.

The following Container Storage Modules Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v1.x

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.
As of Container Storage Modules v1.15, Authorization v1.x will not be supported. Please migrate to Authorization v2.0 using the following guide.

Install CSM Authorization via Container Storage Modules Operator

Prerequisite

Execute kubectl create namespace authorization to create the authorization namespace (if not already present). Note that the namespace can be any user-defined name, in this example, we assume that the namespace is ‘authorization’.

Authorization v1.x

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.
As of Container Storage Modules v1.15, Authorization v1.x will not be supported. Please migrate to Authorization v2.0 using the following guide.

Container Storage Modules Authorization can be installed by using the provided Helm v3 charts on Kubernetes platforms.

The following Container Storage Modules Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v1.x

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.
As of Container Storage Modules v1.15, Authorization v1.x will not be supported. Please migrate to Authorization v2.0 using the following guide.

Install CSM Authorization via Container Storage Modules Operator

Prerequisite

Execute kubectl create namespace authorization to create the authorization namespace (if not already present). Note that the namespace can be any user-defined name, in this example, we assume that the namespace is ‘authorization’.

Authorization v1.x

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.
As of Container Storage Modules v1.15, Authorization v1.x will not be supported. Please migrate to Authorization v2.0 using the following guide.

Container Storage Modules Authorization can be installed by using the provided Helm v3 charts on Kubernetes platforms.

The following Container Storage Modules Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v1.x

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.
As of Container Storage Modules v1.15, Authorization v1.x will not be supported. Please migrate to Authorization v2.0 using the following guide.

Install CSM Authorization via Container Storage Modules Operator

Prerequisite

Execute kubectl create namespace authorization to create the authorization namespace (if not already present). Note that the namespace can be any user-defined name, in this example, we assume that the namespace is ‘authorization’.

Authorization v1.x

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.
As of Container Storage Modules v1.15, Authorization v1.x will not be supported. Please migrate to Authorization v2.0 using the following guide.

Install CSM Authorization via Container Storage Modules Operator

Prerequisite

Execute kubectl create namespace authorization to create the authorization namespace (if not already present). Note that the namespace can be any user-defined name, in this example, we assume that the namespace is ‘authorization’.

Authorization v1.x

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.
As of Container Storage Modules v1.15, Authorization v1.x will not be supported. Please migrate to Authorization v2.0 using the following guide.

Install CSM Authorization via Container Storage Modules Operator

Prerequisite

Execute kubectl create namespace authorization to create the authorization namespace (if not already present). Note that the namespace can be any user-defined name, in this example, we assume that the namespace is ‘authorization’.

Between Storage Arrays

Mon, 01 Jan 0001 00:00:00 +0000

User can migrate existing pre-provisioned volumes to another storage array by using the array migration feature.

NOTE: Currently only migration of standalone block volumes is supported.

Prerequisites

This feature needs to be planned in a controlled host environment.

Between Storage Arrays

Mon, 01 Jan 0001 00:00:00 +0000

User can migrate existing pre-provisioned volumes to another storage array by using the array migration feature.

NOTE: Currently only migration of standalone block volumes is supported.

Prerequisites

This feature needs to be planned in a controlled host environment.

Between Storage Arrays

Mon, 01 Jan 0001 00:00:00 +0000

User can migrate existing pre-provisioned volumes to another storage array by using the array migration feature.

NOTE: Currently only migration of standalone block volumes is supported.

Prerequisites

This feature needs to be planned in a controlled host environment.

Between Storage Arrays

Mon, 01 Jan 0001 00:00:00 +0000

User can migrate existing pre-provisioned volumes to another storage array by using the array migration feature.

NOTE: Currently only migration of standalone block volumes is supported.

Prerequisites

This feature needs to be planned in a controlled host environment.

Component and Image Details

Mon, 01 Jan 0001 00:00:00 +0000

Container Storage Modules Component Version

Component	Image Version
PowerFlex	2.16.1
PowerStore	2.16.0
PowerMax	2.16.2
PowerScale	2.16.0
Unity XT	2.16.0
Authorization v2.x	2.4.0
Observability	1.14.0
Replication	1.14.0
Resiliency	1.15.0
COSI	1.0.0

Container Storage Modules Certified Operator 1.11.3 Images

PowerStore

Version/Digest	Image
1.11.3	registry.connect.redhat.com/dell-emc/dell-container-storage-modules-operator@sha256:9547300ef7cca3a9e3f33ba43d01b3feb99a78c92bae0838b8f152fa90b80e45
2.16.0	registry.connect.redhat.com/dell-emc/dell-csm-powerstore@sha256:4be94a81d2bfdabacb686d3061ef9b71861f21efd6678b23c418c484dd10d2f9
1.14.0	registry.connect.redhat.com/dell-emc/dell-csm-metrics-powerstore@sha256:e02dbcb245797cbf6c6ad22803ff3c38f5be5690b18502d00af134a9c15531c9
6.1.0	registry.k8s.io/sig-storage/csi-provisioner@sha256:6b5a502366ecd4ed81bcdc768699fe431ab70437324f5a7883e9f49a5d640863
4.10.0	registry.k8s.io/sig-storage/csi-attacher@sha256:8a46d7ecbb798f19d7ccd7e510a2efec00ae7ba50fd82cc2f5ac45cedbab0bc1
2.15.0	registry.k8s.io/sig-storage/csi-node-driver-registrar@sha256:11f199f6bec47403b03cb49c79a41f445884b213b382582a60710b8c6fdc316a
2.0.0	registry.k8s.io/sig-storage/csi-resizer@sha256:25b17c4f84b0ab061da6397caf407c7251a571df5c4071e4917942684c61689a
8.4.0	registry.k8s.io/sig-storage/csi-snapshotter@sha256:c7e0a3718832b6197ce8b29fefb3fed3d84f4fbcdf08f4606140dbec2566501d
1.13.0	registry.connect.redhat.com/dell-emc/dell-csm-metadata-retriever@sha256:d54cefd22172c3ece3136ffab83bf988baa7669728bd3d4affae99232bfea8c3
0.15.0	registry.k8s.io/sig-storage/csi-external-health-monitor-controller@sha256:38082bf43b98f921de25924c4b9b9a0a3d1d27d8c912b9a8cbda8c316798e54b
2.4.0	registry.connect.redhat.com/dell-emc/dell-csm-authorization-sidecar@sha256:6ae8703e8e1bb3d1728ab58b2306d7f0adab4d1f3b1f1f0a7467c275590e4e13
1.15.0	registry.connect.redhat.com/dell-emc/dell-csm-podmon@sha256:4f910318b4591ced142ee83ae49706f477f29598bd98010bf09905a3b4edfa40
1.14.0	registry.connect.redhat.com/dell-emc/dell-csm-replicator@sha256:901004afd7968ecb58d9be9c40756b67e51dd3c0a60f041215872b0448839b5d
1.14.0	registry.connect.redhat.com/dell-emc/dell-csm-replication-controller-manager@sha256:7d7d9a19b46d0e06fa57af609be29a441d2be63a20cfddb764904c75c187fe5b
0.143.1	ghcr.io/open-telemetry/opentelemetry-collector-releases/opentelemetry-collector@sha256:7a838b2f7a221459a6593b42483c43e7c2a3f86640136c33a436c071c0a410f4
1.27	quay.io/nginx/nginx-unprivileged@sha256:620c21188bee45c4145dbf1716117994eda3b9426d3d214de37a9468377a15d1

Authorization Proxy Server

Component and Image Details

Mon, 01 Jan 0001 00:00:00 +0000

Container Storage Modules Component Version

Component	Image Version
PowerFlex	2.15.2
PowerStore	2.15.1
PowerMax	2.15.1
PowerScale	2.15.1
Unity XT	2.15.1
Authorization v2.x	2.3.0
Observability	1.13.0
Replication	1.13.0
Resiliency	1.14.0

Container Storage Modules Certified Operator 1.10.2 Images

PowerStore

Version/Digest	Image
1.10.2	registry.connect.redhat.com/dell-emc/dell-container-storage-modules-operator@sha256:3b44b9dd39a3831a54aac1bf9cbe8d72582e7b4612ba0b17daff1bfc0c244bdc
2.15.1	registry.connect.redhat.com/dell-emc/dell-csm-powerstore@sha256:0b4e3f64ec340bb16bda3719fb447c17ee09529cbcf1bb08354470aac10e93cc
1.13.0	registry.connect.redhat.com/dell-emc/dell-csm-metrics-powerstore@sha256:4d288473ab69dff348842d0a04c9c57aa7b76cc18c394e98906d09bfd08e0b60
5.3.0	registry.k8s.io/sig-storage/csi-provisioner@sha256:bb057f866177d5f4139a1527e594499cbe0feeb67b63aaca8679dfdf0a6016f9
4.9.0	registry.k8s.io/sig-storage/csi-attacher@sha256:5aaefc24f315b182233c8b6146077f8c32e274d864cb03c632206e78bd0302da
2.14.0	registry.k8s.io/sig-storage/csi-node-driver-registrar@sha256:5244abbe87e01b35adeb8bb13882a74785df0c0619f8325c9e950395c3f72a97
1.14.0	registry.k8s.io/sig-storage/csi-resizer@sha256:5e7cbb63fd497fa913caa21fee1a69f727c220c6fa83c5f8bb0995e2ad73a474
8.3.0	registry.k8s.io/sig-storage/csi-snapshotter@sha256:bc7be893ecc3ad524194aa6573b2f5c06cd469bdf21a500ab6c99c2ba1c4d64d
1.12.0	registry.connect.redhat.com/dell-emc/dell-csm-metadata-retriever@sha256:6de94d91a17a401b5f2e5cdf7bb50cd053521deaf1e189340d21c4249e8c4bf1
0.15.0	registry.k8s.io/sig-storage/csi-external-health-monitor-controller@sha256:ce054c6fade575e9d4dbd4c3d65b9c5d1b05160aacfb9cf8d8cac51d73f3ccea
2.3.0	registry.connect.redhat.com/dell-emc/dell-csm-authorization-sidecar@sha256:fadcba26fe3464925b7b8857d470204ba43a72e75edd32ffa83675c1db6530da
1.14.0	registry.connect.redhat.com/dell-emc/dell-csm-podmon@sha256:68780493ea9718faa399babd40cf09e1ace43e6a63a878d37612fec377067ebe
1.13.0	registry.connect.redhat.com/dell-emc/dell-csm-replicator@sha256:b427913a72121a261161cf2f81bb991dfd383fa1703d20f1f1ff4fb5743eba16
1.13.0	registry.connect.redhat.com/dell-emc/dell-csm-replication-controller-manager@sha256:8cad45a81bd05be95170944850dd1b8b5fb7c8c5ee0397420d04cd2155ba52fa
0.135.0	ghcr.io/open-telemetry/opentelemetry-collector-releases/opentelemetry-collector@sha256:6d260efde7406a1f7d731a5d9663cb6ce25fa634f3ef3ef4a69266aaae1680fd
1.27	quay.io/nginx/nginx-unprivileged@sha256:f9dfa9c20b2b0b7c5cc830374f22f23dee3f750b6c5291ca7e0330b5c88e6403

Authorization Proxy Server

Component and Image Details

Mon, 01 Jan 0001 00:00:00 +0000

Container Storage Modules Component Version

Component	Version
PowerFlex	2.14.2
PowerStore	2.14.1
PowerMax	2.14.1
PowerScale	2.14.0
Unity XT	2.14.0
Authorization v1.x	1.14.0
Authorization v2.x	2.2.0
Observability	1.12.0
Replication	1.12.0
Resiliency	1.13.0
Application Mobility	1.4.0

Container Storage Modules Certified Operator 1.9.1 Images

PowerStore

Version/Digest	Image
1.9.1	registry.connect.redhat.com/dell-emc/dell-container-storage-modules-operator@sha256:7f66f9a663aba48449f6ae385f951a32d4bb8f1a38b320c6eda32b3d2c438292
2.14.1	registry.connect.redhat.com/dell-emc/dell-csm-powerstore@sha256:c27df3c3161897235d33e978fbd3a563c39bdf21c0df6c21a75653b785932353
5.1.0	registry.k8s.io/sig-storage/csi-provisioner@sha256:672e45d6a55678abc1d102de665b5cbd63848e75dc7896f238c8eaaf3c7d322f
4.8.0	registry.k8s.io/sig-storage/csi-attacher@sha256:a399393ff5bd156277c56bae0c08389b1a1b95b7fd6ea44a316ce55e0dd559d7
2.13.0	registry.k8s.io/sig-storage/csi-node-driver-registrar@sha256:d7138bcc3aa5f267403d45ad4292c95397e421ea17a0035888850f424c7de25d
1.13.1	registry.k8s.io/sig-storage/csi-resizer@sha256:2a0b297cc7c4cd376ac7413df339ff2fdaa1ec9d099aed92b5ea1f031ef7f639
8.2.0	registry.k8s.io/sig-storage/csi-snapshotter@sha256:dd788d79cf4c1b8edee6d9b80b8a1ebfc51a38a365c5be656986b129be9ac784
1.10.0	registry.connect.redhat.com/dell-emc/dell-csm-metadata-retriever@sha256:a8412f649ffca3aa72f5c9f5f2c3eb5dac5d742dfa5d3f4e0ef4bd81d72f2956
0.14.0	registry.k8s.io/sig-storage/csi-external-health-monitor-controller@sha256:65d118e955cfa0827d0f727fe161a7469e0e1c6829c347a484130aeb6e45f377
1.13.0	registry.connect.redhat.com/dell-emc/dell-csm-podmon@sha256:5c3f5e473b9f3ce5797a61b2466d16d8b9c488e69ee35ac336c424bef8979abc

PowerScale

Version/Digest	Image
1.9.1	registry.connect.redhat.com/dell-emc/dell-container-storage-modules-operator@sha256:7f66f9a663aba48449f6ae385f951a32d4bb8f1a38b320c6eda32b3d2c438292
2.14.1	registry.connect.redhat.com/dell-emc/dell-csm-powerscale@sha256:10fd23e10bbd48f202e3a5db2e94568f01772687b0459384320fb60030743fc7
5.1.0	registry.k8s.io/sig-storage/csi-provisioner@sha256:672e45d6a55678abc1d102de665b5cbd63848e75dc7896f238c8eaaf3c7d322f
4.8.0	registry.k8s.io/sig-storage/csi-attacher@sha256:a399393ff5bd156277c56bae0c08389b1a1b95b7fd6ea44a316ce55e0dd559d7
2.13.0	registry.k8s.io/sig-storage/csi-node-driver-registrar@sha256:d7138bcc3aa5f267403d45ad4292c95397e421ea17a0035888850f424c7de25d
1.13.1	registry.k8s.io/sig-storage/csi-resizer@sha256:2a0b297cc7c4cd376ac7413df339ff2fdaa1ec9d099aed92b5ea1f031ef7f639
8.2.0	registry.k8s.io/sig-storage/csi-snapshotter@sha256:dd788d79cf4c1b8edee6d9b80b8a1ebfc51a38a365c5be656986b129be9ac784
1.10.0	registry.connect.redhat.com/dell-emc/dell-csm-metadata-retriever@sha256:a8412f649ffca3aa72f5c9f5f2c3eb5dac5d742dfa5d3f4e0ef4bd81d72f2956
0.14.0	registry.k8s.io/sig-storage/csi-external-health-monitor-controller@sha256:65d118e955cfa0827d0f727fe161a7469e0e1c6829c347a484130aeb6e45f377
1.12.0	registry.connect.redhat.com/dell-emc/dell-csm-topology@sha256:8c99287c7da6fd122d29cc7b2ae0dec147fd0c666b94a8a99a9b2003ffe68586
0.124.0	ghcr.io/open-telemetry/opentelemetry-collector-releases/opentelemetry-collector@sha256:9b8b6ef5f387429f5cb27267dfd3ca038b861a23cce40164a6c327efcceb7665
1.9.0	registry.connect.redhat.com/dell-emc/dell-csm-metrics-powerscale@sha256:78e1ed4b65c378d35e9cae76d7fb67fe0dfde6c2d111b5f3216fe376095148b6
1.12.0	registry.connect.redhat.com/dell-emc/dell-csm-replicator@sha256:3647b734da48dd44f4b8af9cd56eaba613d59201927420e877ed9eeefe573b32
1.12.0	registry.connect.redhat.com/dell-emc/dell-csm-replication-controller-manager@sha256:45ff6eb59f4ac87cd68d4405c07f20e7e34f5a2d33775f33d89b8a3437a06fab
1.13.0	registry.connect.redhat.com/dell-emc/dell-csm-podmon@sha256:5c3f5e473b9f3ce5797a61b2466d16d8b9c488e69ee35ac336c424bef8979abc
2.2.0	registry.connect.redhat.com/dell-emc/dell-csm-authorization-sidecar@sha256:dd8aac3380d1d0664f7bbeb63da36443a57da12f9a26e435f33b8a33bdea4cb9
1.27.5	docker.io/nginxinc/nginx-unprivileged@sha256:f9dfa9c20b2b0b7c5cc830374f22f23dee3f750b6c5291ca7e0330b5c88e6403

Authorization Proxy Server

Component Version

Mon, 01 Jan 0001 00:00:00 +0000

Component	Image Version
PowerFlex	v2.13.2
PowerStore	v2.13.0
PowerMax	v2.13.0
PowerScale	v2.13.0
Unity XT	v2.13.0
Authorization v1.x	v1.13.0
Authorization v2.x	v2.1.0
Observability	v1.11.0
Replication	v1.11.0
Resiliency	v1.12.0
Application Mobility	v1.3.0

Configuration

Mon, 01 Jan 0001 00:00:00 +0000

Dell COSI Driver Configuration Schema

This configuration file is used to specify the settings for the Dell COSI Driver, which is responsible for managing connections to the Dell ObjectScale platform. The configuration file is written in YAML format and based on the JSON schema and adheres to its specification.

Configuration File

Mon, 01 Jan 0001 00:00:00 +0000

Dell COSI Driver Configuration Schema

Configuration File

Mon, 01 Jan 0001 00:00:00 +0000

Dell COSI Driver Configuration Schema

Configuration File

Mon, 01 Jan 0001 00:00:00 +0000

Dell COSI Driver Configuration Schema

CSM Operator Compatibility Matrix

Mon, 01 Jan 0001 00:00:00 +0000

The table below lists the driver and modules versions installable with the Container Storage Modules Operator:

CSI Driver	Version	CSM Authorization 2.x.x	CSM Replication	CSM Observability	CSM Resiliency
CSI PowerScale	v2.16.0	✔ v2.4.0	✔ v1.14.0	✔ v1.14.0	✔ v1.15.0
CSI PowerFlex	v2.16.1	✔ v1.14.0 , v2.4.0	✔ v1.14.0	✔ v1.14.0	✔ v1.15.0
CSI PowerStore	v2.16.0	❌ , ❌	✔ v1.14.0	✔ v1.14.0	✔ v1.15.0
CSI PowerMax	v2.16.2	✔ v2.4.0	✔ v1.14.0	✔ v1.14.0	✔ v1.15.0
CSI Unity XT	v2.16.0	❌ , ❌	❌	❌	❌

CSM Operator Compatibility Matrix

Mon, 01 Jan 0001 00:00:00 +0000

The table below lists the driver and modules versions installable with the Container Storage Modules Operator:

CSI Driver	Version	CSM Authorization 2.x.x	CSM Replication	CSM Observability	CSM Resiliency
CSI PowerScale	v2.15.1	✔ v2.3.0	✔ v1.13.0	✔ v1.13.0	✔ v1.14.0
CSI PowerFlex	v2.15.2	✔ v1.14.0 , v2.3.0	✔ v1.13.0	✔ v1.13.0	✔ v1.14.0
CSI PowerStore	v2.15.1	❌ , ❌	✔ v1.13.0	✔ v1.13.0	✔ v1.14.0
CSI PowerMax	v2.15.1	✔ v2.3.0	✔ v1.13.0	✔ v1.13.0	✔ v1.14.0
CSI Unity XT	v2.15.0	❌ , ❌	❌	❌	❌

CSM Operator Compatibility Matrix

Mon, 01 Jan 0001 00:00:00 +0000

The table below lists the driver and modules versions installable with the Container Storage Modules Operator:

CSI Driver	Version	CSM Authorization 1.x.x , 2.x.x	CSM Replication	CSM Observability	CSM Resiliency
CSI PowerScale	v2.14.0	✔ v1.14.0 , v2.2.0	✔ v1.12.0	✔ v1.12.0	✔ v1.13.0
CSI PowerFlex	v2.14.2	✔ v1.14.0 , v2.2.0	✔ v1.12.0	✔ v1.12.0	✔ v1.13.0
CSI PowerStore	v2.14.1	❌ , ❌	❌	❌	✔ v1.13.0
CSI PowerMax	v2.14.1	✔ v1.14.0 , v2.2.0	✔ v1.12.0	✔ v1.12.0	✔ v1.13.0
CSI Unity XT	v2.14.0	❌ , ❌	❌	❌	❌

CSM Operator Compatibility Matrix

Mon, 01 Jan 0001 00:00:00 +0000

The table below lists the driver and modules versions installable with the Container Storage Modules Operator:

CSI Driver	Version	CSM Authorization 1.x.x , 2.x.x	CSM Replication	CSM Observability	CSM Resiliency
CSI PowerScale	2.13.0	✔ 1.13.0 , 2.1.0	✔ 1.11.0	✔ 1.11.0	✔ 1.12.0
CSI PowerFlex	2.13.1	✔ 1.13.0 , 2.1.0	✔ 1.11.0	✔ 1.11.0	✔ 1.12.0
CSI PowerStore	2.13.0	❌ , ❌	❌	❌	✔ 1.12.0
CSI PowerMax	2.13.0	✔ 1.13.0 , 2.1.0	✔ 1.11.0	✔ 1.11.0	✔ 1.12.0
CSI Unity XT	2.13.0	❌ , ❌	❌	❌	❌

Design

Mon, 01 Jan 0001 00:00:00 +0000

This section covers Container Storage Modules for Resiliency’s design. The detail is sufficient that you should be able to understand what Container Storage Modules for Resiliency is designed to do in various situations and how it works. Resiliency is deployed as a sidecar named podmon with a CSI driver in both the controller pods and node pods. These are referred to as controller-podmon and node-podmon respectively.

Generally controller-podmon and the driver controller pods are deployed using a Deployment. The Deployments support one or multiple replicas for High Availability and use a standard K8S leader election protocol so that only one controller is active at a time (as does the driver and all the controller sidecars.) The controller deployment also supports a Node Selector that allows the controllers to be placed on K8S Manager (non Worker) nodes.

Design

Mon, 01 Jan 0001 00:00:00 +0000

Design

Mon, 01 Jan 0001 00:00:00 +0000

Container Storage Modules for Authorization is designed as a service mesh solution and consists of many internal components that work together in concert to achieve its overall functionality.

Note:Ensure Helm 3.x, namespace, and secrets are set up before installing the Helm chart.

Installation Wizard Helm

Mon, 01 Jan 0001 00:00:00 +0000

Note:Ensure Helm 3.x, namespace, and secrets are set up before installing the Helm chart.

Installation Wizard Helm

Mon, 01 Jan 0001 00:00:00 +0000

Note:Ensure Helm 3.x, namespace, and secrets are set up before installing the Helm chart.

Installation Wizard Operator

Mon, 01 Jan 0001 00:00:00 +0000

Installation Wizard Overview

The Container Storage Modules Installation Wizard is a webpage that helps you create a manifest file to install Dell CSI Drivers and CSM Modules. Users can enable or disable modules through the UI, and it generates a single manifest file, eliminating the need to download individual Helm charts for drivers and modules.

Installation Wizard Operator

Mon, 01 Jan 0001 00:00:00 +0000

CSM Installation Wizard Support Matrix Click Here

Generate Manifest File

Open the Installation Wizard.
Select the Installation Type as Helm/Operator.
Select the Array.
Enter the Image Repository. The default value is dellemc.
Select the CSM Version.
Select the modules for installation. If there are module specific inputs, enter their values.
If needed, modify the Controller Pods Count.
If needed, select Install Controller Pods on Control Plane and/or Install Node Pods on Control Plane.
Enter the Namespace. The default value is csi-<array>.
Click on Generate YAML.
A manifest file, values.yaml will be generated and downloaded.
A section Run the following commands to install will be displayed.
Run the commands displayed to install Dell CSI Driver and Modules using the generated manifest file.

Installation Using Operator

Steps

Installation Wizard Operator

Mon, 01 Jan 0001 00:00:00 +0000

CSM Installation Wizard Support Matrix Click Here

Generate Manifest File

Open the Installation Wizard.
Select the Installation Type as Helm/Operator.
Select the Array.
Enter the Image Repository. The default value is dellemc.
Select the CSM Version.
Select the modules for installation. If there are module specific inputs, enter their values.
If needed, modify the Controller Pods Count.
If needed, select Install Controller Pods on Control Plane and/or Install Node Pods on Control Plane.
Enter the Namespace. The default value is csi-<array>.
Click on Generate YAML.
A manifest file, values.yaml will be generated and downloaded.
A section Run the following commands to install will be displayed.
Run the commands displayed to install Dell CSI Driver and Modules using the generated manifest file.

Installation Using Operator

Steps

ObjectScale

Mon, 01 Jan 0001 00:00:00 +0000

Kubernetes Objects

Bucket Class

Installation of ObjectScale COSI driver does not create BucketClass resource. BucketClass represents a class of Bucket resources with similar characteristics. Dell COSI Driver is a multi-backend driver, meaning that for every platform the specific BucketClass should be created. The BucketClass resource should contain the name of multi-backend driver and parameters.id for specific Object Storage Platform.

ObjectScale

Mon, 01 Jan 0001 00:00:00 +0000

Fields are specified by their path. Consider the following examples:

Field specified by the following path spec.authenticationType=IAM is reflected in their resources YAML as the following:

spec:
  authenticationType: IAM

field specified by path spec.protocols=[Azure,GCS] is reflected in their resources YAML as the following:

spec:
  protocols:
    - Azure
    - GCS

Prerequisites

To use the COSI Driver on the ObjectScale platform, you must deploy the following components to your cluster:

ObjectScale

Mon, 01 Jan 0001 00:00:00 +0000

Fields are specified by their path. Consider the following examples:

Field specified by the following path spec.authenticationType=IAM is reflected in their resources YAML as the following:

spec:
  authenticationType: IAM

field specified by path spec.protocols=[Azure,GCS] is reflected in their resources YAML as the following:

spec:
  protocols:
    - Azure
    - GCS

Prerequisites

To use the COSI Driver on the ObjectScale platform, you must deploy the following components to your cluster:

ObjectScale

Mon, 01 Jan 0001 00:00:00 +0000

Fields are specified by their path. Consider the following examples:

Field specified by the following path spec.authenticationType=IAM is reflected in their resources YAML as the following:

spec:
  authenticationType: IAM

field specified by path spec.protocols=[Azure,GCS] is reflected in their resources YAML as the following:

spec:
  protocols:
    - Azure
    - GCS

Prerequisites

The CSI PowerFlex driver versions 2.0 and higher support v1 snapshots.

In order to use Volume Snapshots, ensure the following components are deployed to your cluster:

Kubernetes Volume Snapshot CRDs
Volume Snapshot Controller

Volume Snapshot Class

PowerFlex

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

You can upgrade the CSI Driver for Dell PowerFlex using Helm or Dell CSM Operator.

Update Driver from v2.14.0 to v2.15.2 using Helm

Steps

PowerFlex

Mon, 01 Jan 0001 00:00:00 +0000

Volume Snapshot Feature

The CSI PowerFlex driver versions 2.0 and higher support v1 snapshots.

In order to use Volume Snapshots, ensure the following components are deployed to your cluster:

Kubernetes Volume Snapshot CRDs
Volume Snapshot Controller

Volume Snapshot Class

PowerFlex

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

You can upgrade the CSI Driver for Dell PowerFlex using Helm or Dell CSM Operator.

Update Driver from v2.13.2 to v2.14.2 using Helm

Steps

PowerFlex

Mon, 01 Jan 0001 00:00:00 +0000

Volume Snapshot Feature

The CSI PowerFlex driver versions 2.0 and higher support v1 snapshots.

In order to use Volume Snapshots, ensure the following components are deployed to your cluster:

Kubernetes Volume Snapshot CRDs
Volume Snapshot Controller

Volume Snapshot Class

PowerFlex

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

You can upgrade the CSI Driver for Dell PowerFlex using Helm or Dell CSM Operator.

Update Driver from v2.12.0 to v2.13.2 using Helm

Steps

PowerFlex Metrics

Mon, 01 Jan 0001 00:00:00 +0000

Mon, 01 Jan 0001 00:00:00 +0000

This section outlines the metrics collected by the Container Storage Modules (CSM) Observability module for PowerFlex. The Grafana reference dashboards for PowerFlex metrics can be uploaded to your Grafana instance.

I/O Performance Metrics

Storage system I/O performance metrics (IOPS, bandwidth, latency) are available by default and broken down by export node and volume.

PowerMax

Mon, 01 Jan 0001 00:00:00 +0000

Multi Unisphere Support

Starting with v1.7, the CSI PowerMax driver can communicate with multiple Unisphere for PowerMax servers to manage multiple PowerMax arrays.For more details on how to configure the driver and ReverseProxy, see the relevant section here

PowerMax

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

Upgrades to the CSI Driver for Dell PowerMax can be made using Helm or Dell CSM Operator.

Note: CSI Driver for PowerMax v2.4.0 and later requires Unisphere version 10.0, or later.

Updating the CSI Driver to use 10.0 Unisphere

Upgrade the Unisphere to have 10.0 endpoint support. Please find the instructions here.
Update the powermax-creds secret to specify endpoints with Unisphere version 10.0 support.

Update Driver from v2.15.1 to v2.16.2 using Helm

Steps

PowerMax

Mon, 01 Jan 0001 00:00:00 +0000

Multi Unisphere Support

PowerMax

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

Upgrades to the CSI Driver for Dell PowerMax can be made using Helm or Dell CSM Operator.

Note: CSI Driver for PowerMax v2.4.0 and later requires Unisphere version 10.0, or later.

Updating the CSI Driver to use 10.0 Unisphere

Upgrade the Unisphere to have 10.0 endpoint support. Please find the instructions here.
Update the powermax-creds secret to specify endpoints with Unisphere version 10.0 support.

Update Driver from v2.14.0 to v2.15.1 using Helm

Steps

PowerMax

Mon, 01 Jan 0001 00:00:00 +0000

Multi Unisphere Support

PowerMax

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

Upgrades to the CSI Driver for Dell PowerMax can be made using Helm or Dell CSM Operator.

Note: CSI Driver for PowerMax v2.4.0 and later requires Unisphere version 10.0, or later.

Updating the CSI Driver to use 10.0 Unisphere

Upgrade the Unisphere to have 10.0 endpoint support. Please find the instructions here.
Update the powermax-creds secret to specify endpoints with Unisphere version 10.0 support.

Update Driver from v2.13.0 to v2.14.1 using Helm

Steps

PowerMax

Mon, 01 Jan 0001 00:00:00 +0000

Multi Unisphere Support

PowerMax

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

You can upgrade CSI Driver for Dell PowerMax using Helm or Dell CSM Operator.

Note: CSI Driver for PowerMax v2.4.0 requires 10.0 REST endpoint support of Unisphere.

Updating the CSI Driver to use 10.0 Unisphere

Upgrade the Unisphere to have 10.0 endpoint support.Please find the instructions here.
Update the my-powermax-settings.yaml to have endpoint with 10.0 support.

Update Driver from v2.12.0 to v2.13.0 using Helm

Steps

PowerMax Metrics

Mon, 01 Jan 0001 00:00:00 +0000

This section outlines the metrics collected by the Container Storage Modules Observability module for PowerMax. The Grafana reference dashboards for PowerMax metrics can be uploaded to your Grafana instance.

Prerequisites

Unisphere user credentials must have PERF_MONITOR permissions.
Ensure time synchronization for Kubernetes cluster and PowerMax Unisphere by using Network Time Protocol (NTP).

I/O Performance Metrics

Storage system I/O performance metrics (IOPS, bandwidth, latency) are available by default and broken down by storage group and volume.

PowerMax Metrics

Mon, 01 Jan 0001 00:00:00 +0000

Prerequisites

Unisphere user credentials must have PERF_MONITOR permissions.
Ensure time synchronization for Kubernetes cluster and PowerMax Unisphere by using Network Time Protocol (NTP).

I/O Performance Metrics

Storage system I/O performance metrics (IOPS, bandwidth, latency) are available by default and broken down by storage group and volume.

PowerMax Metrics

Mon, 01 Jan 0001 00:00:00 +0000

Prerequisites

Unisphere user credentials must have PERF_MONITOR permissions.
Ensure time synchronization for Kubernetes cluster and PowerMax Unisphere by using Network Time Protocol (NTP).

I/O Performance Metrics

Storage system I/O performance metrics (IOPS, bandwidth, latency) are available by default and broken down by storage group and volume.

PowerMax Metrics

Mon, 01 Jan 0001 00:00:00 +0000

This section outlines the metrics collected by the Container Storage Modules (CSM) Observability module for PowerMax. The Grafana reference dashboards for PowerMax metrics can be uploaded to your Grafana instance.

Prerequisites

Unisphere user credentials must have PERF_MONITOR permissions.
Ensure time synchronization for Kubernetes cluster and PowerMax Unisphere by using Network Time Protocol (NTP).

I/O Performance Metrics

You can connect a single CSI-PowerScale driver with multiple PowerScale clusters.

Pre-Requisites:

Creation of secret.yaml with credentials related to one or more Clusters.
Creation of (at least) one Storage class for each cluster.
Creation of custom-volumesnapshot classes with proper isiPath matching corresponding storage classes.
Inclusion of cluster name in volume handle, if you want to provision existing static volumes.

Consuming existing volumes with static provisioning

To use existing volumes from the PowerScale array as Persistent Volumes in your Kubernetes, perform the following steps:

PowerScale

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

You can upgrade the CSI Driver for Dell PowerScale using Helm or Dell CSM Operator.

Upgrade Driver from version v2.14.0 to v2.15.1 using Helm

You can connect a single CSI-PowerScale driver with multiple PowerScale clusters.

Pre-Requisites:

Creation of secret.yaml with credentials related to one or more Clusters.
Creation of (at least) one Storage class for each cluster.
Creation of custom-volumesnapshot classes with proper isiPath matching corresponding storage classes.
Inclusion of cluster name in volume handle, if you want to provision existing static volumes.

Consuming existing volumes with static provisioning

You can use existing volumes from the PowerScale array as Persistent Volumes in your Kubernetes, perform the following steps:

PowerScale

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

You can upgrade the CSI Driver for Dell PowerScale using Helm or Dell CSM Operator.

Upgrade Driver from version v2.12.0 to v2.13.0 using Helm

Note: While upgrading the driver via helm, controllerCount variable in myvalues.yaml can be at most one less than the number of worker nodes.

PowerScale Metrics

Mon, 01 Jan 0001 00:00:00 +0000

Mon, 01 Jan 0001 00:00:00 +0000

This section outlines the metrics collected by the Container Storage Modules (CSM) Observability module for PowerScale. The Grafana reference dashboards for PowerScale metrics can be uploaded to your Grafana instance.

I/O Performance Metrics

Storage system I/O performance metrics (IOPS, bandwidth) are available by default and broken down by cluster and quota.

PowerStore

Mon, 01 Jan 0001 00:00:00 +0000

Creating volumes and consuming them

Create a file simple.yaml using sample yaml files located at tests/simple/

This command creates a statefulset that consumes three volumes of default storage classes

kubectl create -f tests/simple/simple.yaml

kubectl create -f tests/simple/simple.yaml

PowerStore

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

You can upgrade the CSI Driver for Dell PowerStore using Helm.

Update Driver from v2.12.0 to v2.13.0 using Helm

Note: While upgrading the driver via helm, controllerCount variable in myvalues.yaml can be at most one less than the number of worker nodes.

PowerStore Metrics

Mon, 01 Jan 0001 00:00:00 +0000

Mon, 01 Jan 0001 00:00:00 +0000

This section outlines the metrics collected by the Container Storage Modules (CSM) Observability module for PowerStore. The Grafana reference dashboards for PowerStore metrics can be uploaded to your Grafana instance.

I/O Performance Metrics

Storage system I/O performance metrics (IOPS, bandwidth, latency) are available by default and broken down by export node and volume.

Prerequisite

Mon, 01 Jan 0001 00:00:00 +0000

Make sure the nfs is enabled in the powerscale

ps01-1# isi nfs settings global view
NFS Service Enabled: Yes
    NFSv3 Enabled: Yes
    NFSv4 Enabled: Yes
            v4.0 Enabled: Yes
            v4.1 Enabled: Yes
            v4.2 Enabled: Yes
NFS RDMA Enabled: No
    Rquota Enabled: No

Create Group and User for CSM

isi auth group create csmadmins --zone system
isi auth user create csmadmin --password "P@ssw0rd123" --password-expires false --primary-group csmadmins --zone system

Create role and assign the required permission

Prerequisite

Mon, 01 Jan 0001 00:00:00 +0000

Make sure the nfs is enabled in the powerscale

ps01-1# isi nfs settings global view
NFS Service Enabled: Yes
    NFSv3 Enabled: Yes
    NFSv4 Enabled: Yes
            v4.0 Enabled: Yes
            v4.1 Enabled: Yes
            v4.2 Enabled: Yes
NFS RDMA Enabled: No
    Rquota Enabled: No

Create Group and User for CSM

isi auth group create csmadmins --zone system
isi auth user create csmadmin --password "P@ssw0rd123" --password-expires false --primary-group csmadmins --zone system

Create role and assign the required permission

Prerequisite

Mon, 01 Jan 0001 00:00:00 +0000

Make sure the nfs is enabled in the powerscale

ps01-1# isi nfs settings global view
NFS Service Enabled: Yes
    NFSv3 Enabled: Yes
    NFSv4 Enabled: Yes
            v4.0 Enabled: Yes
            v4.1 Enabled: Yes
            v4.2 Enabled: Yes
NFS RDMA Enabled: No
    Rquota Enabled: No

Create Group and User for CSM

isi auth group create csmadmins --zone system
isi auth user create csmadmin --password "P@ssw0rd123" --password-expires false --primary-group csmadmins --zone system

Create role and assign the required permission

Support Policy

Mon, 01 Jan 0001 00:00:00 +0000

The following information is designed to help customers and partners effectively plan, deploy, and maintain timely upgrades for the latest functionality and fixes.

Each release is fully supported for 12 months. Refer to the matrix for General Availability (GA) and End-of-Life (EOL) dates of supported versions.
If running a version older than 12 months, upgrade to a newer version or submit cert-csi test results to Dell support.

Container Storage Modules Version	GA Date	EOL Date
1.16	01/29/2026	01/29/2027
1.15	09/30/2025	09/30/2026
1.14	05/30/2025	05/30/2026
1.13	01/31/2025	01/31/2026

Support Policy

Mon, 01 Jan 0001 00:00:00 +0000

The following information is designed to help customers and partners effectively plan, deploy, and maintain timely upgrades for the latest functionality and fixes.

Each release is fully supported for 12 months. Refer to the matrix for General Availability (GA) and End-of-Life (EOL) dates of supported versions.
If running a version older than 12 months, upgrade to a newer version or submit cert-csi test results to Dell support.

Container Storage Modules Version	GA Date	EOL Date
1.15	09/30/2025	09/30/2026
1.14	05/30/2025	05/30/2026
1.13	01/31/2025	01/31/2026
1.12	11/06/2024	10/31/2025

Support Policy

Mon, 01 Jan 0001 00:00:00 +0000

The following information is designed to help customers and partners effectively plan, deploy, and maintain timely upgrades for the latest functionality and fixes.

Each release is fully supported for 12 months. Refer to the matrix for General Availability (GA) and End-of-Life (EOL) dates of supported versions.
If running a version older than 12 months, upgrade to a newer version or submit cert-csi test results to Dell support.

Container Storage Modules Version	GA Date	EOL Date
1.14	05/30/2025	05/30/2026
1.13	01/31/2025	01/31/2026
1.12	11/06/2024	10/31/2025
1.11	06/30/2024	06/30/2025

Unity XT

Mon, 01 Jan 0001 00:00:00 +0000

Creating volumes and consuming them

Create a file sample.yaml using sample yaml files located at test/sample.yaml

The following command creates a statefulset that consumes three volumes of default storage classes:

kubectl create -f test/sample.yaml

After executing this command 3 PVC and statefulset are created in the unity namespace. You can check created PVCs by running kubectl get pvc -n unity and check statefulset’s pods by running kubectl get pods -n unity command. The pod should be Ready and Running.

Unity XT

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

You can upgrade the CSI Driver for Dell Unity XT using Helm or Dell CSM Operator.

Note:

User has to re-create existing custom-storage classes (if any) according to the latest format.
User has to create Volumesnapshotclass after upgrade for taking Snapshots.
Secret.yaml files can be updated according to Multiarray normalization parameters only after upgrading the driver.

Using Helm

Note: While upgrading the driver via helm, controllerCount variable in myvalues.yaml can be at most one less than the number of worker nodes.

Unity XT

Mon, 01 Jan 0001 00:00:00 +0000

Creating volumes and consuming them

Create a file sample.yaml using sample yaml files located at test/sample.yaml

The following command creates a statefulset that consumes three volumes of default storage classes:

kubectl create -f test/sample.yaml

Unity XT

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

You can upgrade the CSI Driver for Dell Unity XT using Helm or Dell CSM Operator.

Note:

User has to re-create existing custom-storage classes (if any) according to the latest format.
User has to create Volumesnapshotclass after upgrade for taking Snapshots.
Secret.yaml files can be updated according to Multiarray normalization parameters only after upgrading the driver.

Using Helm

Note: While upgrading the driver via helm, controllerCount variable in myvalues.yaml can be at most one less than the number of worker nodes.

Unity XT

Mon, 01 Jan 0001 00:00:00 +0000

Creating volumes and consuming them

Create a file sample.yaml using sample yaml files located at test/sample.yaml

The following command creates a statefulset that consumes three volumes of default storage classes:

kubectl create -f test/sample.yaml

Unity XT

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

You can upgrade the CSI Driver for Dell Unity XT using Helm or Dell CSM Operator.

Note:

User has to re-create existing custom-storage classes (if any) according to the latest format.
User has to create Volumesnapshotclass after upgrade for taking Snapshots.
Secret.yaml files can be updated according to Multiarray normalization parameters only after upgrading the driver.

Using Helm

Note: While upgrading the driver via helm, controllerCount variable in myvalues.yaml can be at most one less than the number of worker nodes.

Unity XT

Mon, 01 Jan 0001 00:00:00 +0000

Creating volumes and consuming them

Create a file sample.yaml using sample yaml files located at test/sample.yaml

The following command creates a statefulset that consumes three volumes of default storage classes:

kubectl create -f test/sample.yaml

Unity XT

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

You can upgrade the CSI Driver for Dell Unity XT using Helm or Dell CSM Operator.

Note:

User has to re-create existing custom-storage classes (if any) according to the latest format.
User has to create Volumesnapshotclass after upgrade for taking Snapshots.
Secret.yaml files can be updated according to Multiarray normalization parameters only after upgrading the driver.

Using Helm

Note: While upgrading the driver via helm, controllerCount variable in myvalues.yaml can be at most one less than the number of worker nodes.

Application mobility

Mon, 01 Jan 0001 00:00:00 +0000

This section outlines the uninstallation steps for Application Mobility.

Uninstall the Application Mobility Helm Chart

This command removes all the Kubernetes components associated with the chart.


helm delete [APPLICATION_MOBILITY_NAME] --namespace [APPLICATION_MOBILITY_NAMESPACE]

Authorization

Mon, 01 Jan 0001 00:00:00 +0000

As of Container Storage Modules v1.15, Authorization v1.x will not be supported. Please migrate to Authorization v2.0 using the following guide.

This section outlines the uninstallation steps for Container Storage Modules (CSM) for Authorization.

Uninstalling the RPM

To uninstall the rpm package on the system, you must first uninstall the K3s SELinux package if SELinux is enabled. To uninstall the K3s SELinux package, run:

Authorization v1.x

Mon, 01 Jan 0001 00:00:00 +0000

This section outlines the uninstallation steps for Container Storage Modules (CSM) for Authorization.

Uninstall the CSM for Authorization Helm Chart

The command below removes all the Kubernetes components associated with the chart.

helm uninstall authorization --namespace authorization

You may also want to delete the karavi-config-secret secret.

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Authorization can be installed by using the provided Helm v3 charts on Kubernetes platforms.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Authorization can be installed by using the provided Helm v3 charts on Kubernetes platforms.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Authorization can be installed by using the provided Helm v3 charts on Kubernetes platforms.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Authorization can be installed by using the provided Helm v3 charts on Kubernetes platforms.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Authorization can be installed by using the provided Helm v3 charts on Kubernetes platforms.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Authorization can be installed by using the provided Helm v3 charts on Kubernetes platforms.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Authorization can be installed by using the provided Helm v3 charts on Kubernetes platforms.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Authorization can be installed by using the provided Helm v3 charts on Kubernetes platforms.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Install Container Storage Modules Authorization via Container Storage Modules Operator

Prerequisite

Install Vault or configure an existing Vault.

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Authorization can be installed by using the provided Helm v3 charts on Kubernetes platforms.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Install Container Storage Modules Authorization via Container Storage Modules Operator

Prerequisite

Install Vault or configure an existing Vault.

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Authorization can be installed by using the provided Helm v3 charts on Kubernetes platforms.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Install Container Storage Modules Authorization via Container Storage Modules Operator

Prerequisite

Install Vault or configure an existing Vault.

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Authorization can be installed by using the provided Helm v3 charts on Kubernetes platforms.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

Install Vault or configure an existing Vault.

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

This section outlines the uninstallation steps for Container Storage Modules (CSM) for Authorization v2.

Delete all Authorization Custom Resources(CRs)

The commands below will delete a Tenant, Role, and Storage system. All CRs must be deleted before Authorization is uninstalled.

Between Storage classes

Mon, 01 Jan 0001 00:00:00 +0000

You can migrate existing pre-provisioned volumes to another storage class by using volume migration feature.

Currently two versions of migration are supported:

To replicated storage class from NON replicated one.
To NON replicated storage class from replicated one.

Prerequisites

Original volume is from the one of currently supported CSI drivers (see Support Matrix)
Migrated sidecar is installed alongside with the driver, you can enable it in your myvalues.yaml file

migration:
  enabled: true

Support Matrix

Migration Type	PowerStore	PowerScale	PowerFlex	PowerMax	Unity
NON_REPL_TO_REPL	No	No	No	Yes	No
REPL_TO_NON_REPL	No	No	No	Yes	No

Basic Usage

To trigger migration procedure, you need to patch existing PersistentVolume with migration annotation (by default migration.storage.dell.com/migrate-to) and in value of said annotation specify StorageClass name you want to migrate to.

Between Storage classes

Mon, 01 Jan 0001 00:00:00 +0000

You can migrate existing pre-provisioned volumes to another storage class by using volume migration feature.

Currently two versions of migration are supported:

To replicated storage class from NON replicated one.
To NON replicated storage class from replicated one.

Prerequisites

Original volume is from the one of currently supported CSI drivers (see Support Matrix)
Migrated sidecar is installed alongside with the driver, you can enable it in your myvalues.yaml file

migration:
  enabled: true

Support Matrix

Migration Type	PowerStore	PowerScale	PowerFlex	PowerMax	Unity
NON_REPL_TO_REPL	❌	❌	❌	✅	❌
REPL_TO_NON_REPL	❌	❌	❌	✅	❌

Basic Usage

Between Storage classes

Mon, 01 Jan 0001 00:00:00 +0000

You can migrate existing pre-provisioned volumes to another storage class by using volume migration feature.

Currently two versions of migration are supported:

To replicated storage class from NON replicated one.
To NON replicated storage class from replicated one.

Prerequisites

Original volume is from the one of currently supported CSI drivers (see Support Matrix)
Migrated sidecar is installed alongside with the driver, you can enable it in your myvalues.yaml file

migration:
  enabled: true

Support Matrix

Migration Type	PowerMax	PowerStore	PowerScale	PowerFlex	Unity
NON_REPL_TO_REPL	Yes	No	No	No	No
REPL_TO_NON_REPL	Yes	No	No	No	No

Basic Usage

Between Storage classes

Mon, 01 Jan 0001 00:00:00 +0000

You can migrate existing pre-provisioned volumes to another storage class by using volume migration feature.

Currently two versions of migration are supported:

To replicated storage class from NON replicated one.
To NON replicated storage class from replicated one.

Prerequisites

Original volume is from the one of currently supported CSI drivers (see Support Matrix)
Migrated sidecar is installed alongside with the driver, you can enable it in your myvalues.yaml file

migration:
  enabled: true

Support Matrix

Migration Type	PowerMax	PowerStore	PowerScale	PowerFlex	Unity
NON_REPL_TO_REPL	Yes	No	No	No	No
REPL_TO_NON_REPL	Yes	No	No	No	No

Basic Usage

ConfigMap And CustomRegistry Configuration

Mon, 01 Jan 0001 00:00:00 +0000

NOTE: Starting from CSM version 1.16, users can utilize the spec.version parameter for automatic image management. No ConfigMap or custom registry configuration needed.

Advanced Configuration

Use these options only if you need to override standard behavior:

Installation

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The installation process consists of two steps:

Install Container Storage Modules (CSM) for Replication Controller
Install CSI driver after enabling replication

Before you begin

Please read this document before proceeding with the installation. It provides detailed steps on how to set up communication between multiple clusters which will be required during or after the installation.

Installation

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The installation process consists of two steps:

Install Container Storage Modules (CSM) for Replication Controller
Install CSI driver after enabling replication

Before you begin

Installation

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The installation process consists of two steps:

Install Container Storage Modules (CSM) for Replication Controller
Install CSI driver after enabling replication

Before you begin

Installation

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The installation process consists of two steps:

Install Container Storage Modules (CSM) for Replication Controller
Install CSI driver after enabling replication

You can update CSI Drivers installed by the Dell CSM Operator like any Kubernetes resource:

Get the driver-object details using kubectl command:

kubectl get csm -n powerstore

kubectl get csm -n isilon

kubectl get csm -n vxflexos

kubectl get csm -n powermax

kubectl get csm -n unity

As of CSI PowerMax v2.14.0, the csi reverse proxy configuration and connectivity information has been migrated from a ConfigMap to a Secret. If the powermax-creds secret format was not previously updated, reference Step 2 in CSI Driver installation steps.

Operator Upgrade

Mon, 01 Jan 0001 00:00:00 +0000

Operator can be upgraded in 2 ways:

Using Operator Lifecycle Manager (OLM)
Using script (for non-OLM based installation)

Using OLM

The upgrade of the Operator is done via Operator Lifecycle Manager.

The Update approval (InstallPlan in OLM terms) strategy plays a role while upgrading dell-csm-operator on OpenShift. This option can be set during installation of dell-csm-operator on OpenShift via the console and can be either set to Manual or Automatic.

Operator Upgrade

Mon, 01 Jan 0001 00:00:00 +0000

Upgrading Drivers with Dell CSM Operator

You can update CSI Drivers installed by the Dell CSM Operator like any Kubernetes resource:

Get the driver-object details using kubectl command:

kubectl get csm -n powerstore

kubectl get csm -n isilon

kubectl get csm -n vxflexos

kubectl get csm -n powermax

kubectl get csm -n unity

Operator Upgrade

Mon, 01 Jan 0001 00:00:00 +0000

Operator can be upgraded in 2 ways:

Using Operator Lifecycle Manager (OLM)
Using script (for non-OLM based installation)

Using OLM

The upgrade of the Operator is done via Operator Lifecycle Manager.

Operator Upgrade

Mon, 01 Jan 0001 00:00:00 +0000

Upgrading Drivers with Dell CSM Operator

You can update CSI Drivers installed by the Dell CSM Operator like any Kubernetes resource:

Get the driver-object details using kubectl command:

kubectl get csm -n powerstore

kubectl get csm -n isilon

kubectl get csm -n vxflexos

kubectl get csm -n powermax

kubectl get csm -n unity

Operator Upgrade

Mon, 01 Jan 0001 00:00:00 +0000

Operator can be upgraded in 2 ways:

Using Operator Lifecycle Manager (OLM)
Using script (for non-OLM based installation)

Using OLM

The upgrade of the Operator is done via Operator Lifecycle Manager.

PowerMax Metro

Mon, 01 Jan 0001 00:00:00 +0000

SRDF Metro Architecture

In SRDF metro configurations:

R2 devices are Read/Write accessible to application hosts.
The application host can write to both the R1 and R2 sides of the device pair.
R2 devices assume the same external device identity(geometry, device WWN) as the R1 devices. All the above characteristic makes SRDF metro best suited for the scenarios in which high availability of data is desired.

With respect to Kubernetes, the SRDF metro mode works in single cluster scenarios. In the metro, both the arrays—arrays with SRDF metro link setup between them—involved in the replication are managed by the same csi-powermax driver. The replication is triggered by creating a volume using a StorageClass with metro-related parameters. The driver on receiving the metro-related parameters in the CreateVolume call creates a metro replicated volume and the details about both the volumes are returned in the volume context to the Kubernetes cluster. The Persistent Volume (PV) created in the process represents a pair of metro replicated volumes. When a PV, representing a pair of metro replicated volumes, is claimed by a pod, the host treats each of the volumes represented by the single PV as a separate data path. The switching between the paths, to read and write the data, is managed by the multipath driver. The switching happens automatically, as configured by the user—in round-robin fashion or otherwise—or when one of the paths goes down. For details on Linux multipath driver setup, click here.

PowerMax Metro

Mon, 01 Jan 0001 00:00:00 +0000

SRDF Metro Architecture

In SRDF metro configurations:

R2 devices are Read/Write accessible to application hosts.
The application host can write to both the R1 and R2 sides of the device pair.
R2 devices assume the same external device identity(geometry, device WWN) as the R1 devices. All the above characteristic makes SRDF metro best suited for the scenarios in which high availability of data is desired.

PowerMax Metro

Mon, 01 Jan 0001 00:00:00 +0000

SRDF Metro Architecture

In SRDF metro configurations:

R2 devices are Read/Write accessible to application hosts.
The application host can write to both the R1 and R2 sides of the device pair.
R2 devices assume the same external device identity(geometry, device WWN) as the R1 devices. All the above characteristic makes SRDF metro best suited for the scenarios in which high availability of data is desired.

PowerMax Metro

Mon, 01 Jan 0001 00:00:00 +0000

SRDF Metro Architecture

In SRDF metro configurations:

R2 devices are Read/Write accessible to application hosts.
The application host can write to both the R1 and R2 sides of the device pair.
R2 devices assume the same external device identity(geometry, device WWN) as the R1 devices. All the above characteristic makes SRDF metro best suited for the scenarios in which high availability of data is desired.

PowerScale

Mon, 01 Jan 0001 00:00:00 +0000

Mon, 01 Jan 0001 00:00:00 +0000

PowerStore Metro Architecture

In PowerStore Metro configurations:

The application host can write data to both sides of the Metro volume.
The devices in the Metro volume are configured with the same external device identity, including the geometry and device WWN.
When Metro is configured on the volume, the PowerStore system from which the metro source is configured is automatically set as preferred and the other is configured as non-preferred.

With respect to Kubernetes, the PowerStore Metro mode works in single cluster scenarios. When utilizing Metro, both the arrays—arrays with metro link setup between them—involved in the replication are managed by the same csi-powerstore driver. The replication is triggered by creating a volume using a StorageClass with metro-related parameters. The driver on receiving the metro-related parameters in the CreateVolume call creates a metro replicated volume and the details about both the volumes are returned in the volume context to the Kubernetes cluster. The Persistent Volume (PV) created in the process represents a pair of metro replicated volumes. When a PV, representing a pair of metro replicated volumes, is claimed by a pod, the host treats each of the volumes represented by the single PV as a separate data path. The switching between the paths, to read and write the data, is managed by the multipath driver. The switching happens automatically, as configured by the user—in round-robin fashion or otherwise—or when one of the paths goes down. For details on Linux multipath driver setup, click here.

PowerStore Metro

Mon, 01 Jan 0001 00:00:00 +0000

PowerStore Metro Architecture

In PowerStore Metro configurations:

The application host can write data to both sides of the Metro volume.
The devices in the Metro volume are configured with the same external device identity, including the geometry and device WWN.
When Metro is configured on the volume, the PowerStore system from which the metro source is configured is automatically set as preferred and the other is configured as non-preferred.

PowerStore Metro

Mon, 01 Jan 0001 00:00:00 +0000

PowerStore Metro Architecture

In PowerStore Metro configurations:

The application host can write data to both sides of the Metro volume.
The devices in the Metro volume are configured with the same external device identity, including the geometry and device WWN.
When Metro is configured on the volume, the PowerStore system from which the metro source is configured is automatically set as preferred and the other is configured as non-preferred.

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

This section outlines the uninstallation steps for Container Storage Modules (CSM) for Resiliency.

Uninstalling the sidecar in the CSI Driver

To uninstall the sidecar in the CSI Driver, the following steps are required.

Steps

NOTE: If you do not wish to uninstall the driver, please follow the steps below for Resiliency uninstallation through driver upgrade.

Use Cases

Mon, 01 Jan 0001 00:00:00 +0000

Container Storage Modules for Resiliency is primarily designed to detect pod failures due to some kind of node failure or node communication failure. The diagram below shows the hardware environment that is assumed in the design.

The Helm chart installs the following components in a Deployment in the specified namespace:

COSI Driver for ObjectScale

Dependencies

Installing any of the CSI Driver components using Helm requires a few utilities to be installed on the system running the installation.

COSI Driver installation using Helm

Mon, 01 Jan 0001 00:00:00 +0000

The COSI Driver for Dell ObjectScale can be deployed by using the provided Helm v3 charts on Kubernetes platform.

The Helm chart installs the following components in a Deployment in the specified namespace:

COSI Driver for ObjectScale

Dependencies

Installing any of the CSI Driver components using Helm requires a few utilities to be installed on the system running the installation.

COSI Driver installation using Helm

Mon, 01 Jan 0001 00:00:00 +0000

The COSI Driver for Dell ObjectScale can be deployed by using the provided Helm v3 charts on Kubernetes platform.

The Helm chart installs the following components in a Deployment in the specified namespace:

COSI Driver for ObjectScale

Dependencies

Installing any of the CSI Driver components using Helm requires a few utilities to be installed on the system running the installation.

Authorization

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization is handled in 2 parts:

Helm Chart Upgrade
Upgrading the Dell CSI drivers with CSM for Authorization enabled

Upgrade Notices:

CSM v1.16

Authorization

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

Upgrade CSM Authorization

This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization is handled in 2 parts:

Authorization

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization is handled in 2 parts:

Helm Chart Upgrade
Upgrading the Dell CSI drivers with CSM for Authorization enabled

Upgrade Notice: CSM v1.14 → CSM v1.15 (Authorization v2.2.0 → v2.3.0)

Starting with CSM 1.15, CSM Authorization (v2.3.0) requires users to configure storage credentials prior to deployment. This is a mandatory step to ensure proper access to external storage systems.

Authorization

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

Upgrade CSM Authorization

This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization is handled in 2 parts:

Authorization

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.
As of Container Storage Modules v1.15, Authorization v1.x will not be supported. Please migrate to Authorization v2.0 using the following guide.

This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization is handled in 2 parts:

Authorization

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.
As of Container Storage Modules v1.15, Authorization v1.x will not be supported. Please migrate to Authorization v2.0 using the following guide.

This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization is handled in 2 parts:

Authorization

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.
As of Container Storage Modules v1.15, Authorization v1.x will not be supported. Please migrate to Authorization v2.0 using the following guide.

This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization is handled in 2 parts:

Authorization

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.
As of Container Storage Modules v1.15, Authorization v1.x will not be supported. Please migrate to Authorization v2.0 using the following guide.

This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization is handled in 2 parts:

Authorization

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.
As of Container Storage Modules v1.15, Authorization v1.x will not be supported. Please migrate to Authorization v2.0 using the following guide.

This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization is handled in 2 parts:

Authorization

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io . Please note that from CSM 1.14 (May 2025), upgrading will fail if it attempts to use images from Docker Hub.
As of Container Storage Modules v1.15, Authorization v1.x will not be supported. Please migrate to Authorization v2.0 using the following guide.

This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization RPM is handled in 2 parts:

Authorization v1.x

Mon, 01 Jan 0001 00:00:00 +0000

This section outlines the uninstallation steps for Container Storage Modules (CSM) for Authorization.

Uninstall the CSM for Authorization Helm Chart

The command below removes all the Kubernetes components associated with the chart.

helm uninstall authorization --namespace authorization

You may also want to delete the karavi-config-secret secret.

Authorization v1.x

Mon, 01 Jan 0001 00:00:00 +0000

This section outlines the uninstallation steps for Container Storage Modules (CSM) for Authorization.

Uninstall the CSM for Authorization Helm Chart

The command below removes all the Kubernetes components associated with the chart.

helm uninstall authorization --namespace authorization

You may also want to delete the karavi-config-secret secret.

Authorization v1.x

Mon, 01 Jan 0001 00:00:00 +0000

This section outlines the uninstallation steps for Container Storage Modules (CSM) for Authorization.

Uninstall the CSM for Authorization Helm Chart

The command below removes all the Kubernetes components associated with the chart.

helm uninstall authorization --namespace authorization

This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization is handled in 2 parts:

Helm Chart Upgrade
Upgrading the Dell CSI drivers with CSM for Authorization enabled

Upgrade Notice: CSM v1.14 → CSM v1.15 (Authorization v2.2.0 → v2.3.0)

Starting with CSM 1.15, CSM Authorization (v2.3.0) requires users to configure storage credentials prior to deployment. This is a mandatory step to ensure proper access to external storage systems.

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization is handled in 2 parts:

Helm Chart Upgrade
Upgrading the Dell CSI drivers with CSM for Authorization enabled

Upgrade Notice: CSM v1.14 → CSM v1.15 (Authorization v2.2.0 → v2.3.0)

Starting with CSM 1.15, CSM Authorization (v2.3.0) requires users to configure storage credentials prior to deployment. This is a mandatory step to ensure proper access to external storage systems.

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization is handled in 2 parts:

Helm Chart Upgrade
Upgrading the Dell CSI drivers with CSM for Authorization enabled

Upgrade Notice: CSM v1.14 → CSM v1.15 (Authorization v2.2.0 → v2.3.0)

Starting with CSM 1.15, CSM Authorization (v2.3.0) requires users to configure storage credentials prior to deployment. This is a mandatory step to ensure proper access to external storage systems.

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization is handled in 2 parts:

Helm Chart Upgrade
Upgrading the Dell CSI drivers with CSM for Authorization enabled

Upgrade Notice: CSM v1.14 → CSM v1.15 (Authorization v2.2.0 → v2.3.0)

Starting with CSM 1.15, CSM Authorization (v2.3.0) requires users to configure storage credentials prior to deployment. This is a mandatory step to ensure proper access to external storage systems.

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

This section outlines the uninstallation steps for Container Storage Modules (CSM) for Authorization v2.

Delete all Authorization Custom Resources(CRs)

The commands below will delete a Tenant, Role, and Storage system. All CRs must be deleted before Authorization is uninstalled.

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

This section outlines the uninstallation steps for Container Storage Modules (CSM) for Authorization v2.

Delete all Authorization Custom Resources(CRs)

The commands below will delete a Tenant, Role, and Storage system. All CRs must be deleted before Authorization is uninstalled.

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

This section outlines the uninstallation steps for Container Storage Modules (CSM) for Authorization v2.

Delete all Authorization Custom Resources(CRs)

The commands below will delete a Tenant, Role, and Storage system. All CRs must be deleted before Authorization is uninstalled.

Cluster Topologies

Mon, 01 Jan 0001 00:00:00 +0000

Replication Cluster Topologies

Container Storage Modules for Replication project supports the replication of volumes within a single Kubernetes cluster or between two different Kubernetes clusters. The replication controller can support multiple clusters at once, but a single volume can be replicated to a maximum of two clusters.

Cluster Topologies

Mon, 01 Jan 0001 00:00:00 +0000

Replication Cluster Topologies

Cluster Topologies

Mon, 01 Jan 0001 00:00:00 +0000

Replication Cluster Topologies

Cluster Topologies

Mon, 01 Jan 0001 00:00:00 +0000

Replication Cluster Topologies

Container Storage Modules (CSM) for Replication project supports the replication of volumes within a single Kubernetes cluster or between two different Kubernetes clusters. The replication controller can support multiple clusters at once, but a single volume can be replicated to a maximum of two clusters.

ConfigMap & Secrets

Mon, 01 Jan 0001 00:00:00 +0000

Communication between clusters

Container Storage Modules (CSM) for Replication Controller requires access to remote clusters for replicating various objects. There are two ways to set up this communication:

Using Normal Kubernetes users
Using ServiceAccount token

Using Normal Kubernetes users
Using ServiceAccount token

Helm

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules for Observability Helm chart bootstraps an Observability deployment on a Kubernetes cluster using the Helm package manager.

Prerequisites

Helm 3.x
The deployment of one or more supported Dell CSI drivers

Install the Container Storage Modules for Observability Helm Chart

Steps

Helm

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules for Observability Helm chart bootstraps an Observability deployment on a Kubernetes cluster using the Helm package manager.

Prerequisites

Helm 3.x
The deployment of one or more supported Dell CSI drivers

Install the Container Storage Modules for Observability Helm Chart

Steps

Helm

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules for Observability Helm chart bootstraps an Observability deployment on a Kubernetes cluster using the Helm package manager.

Prerequisites

Helm 3.x
The deployment of one or more supported Dell CSI drivers

Install the Container Storage Modules for Observability Helm Chart

Steps

Helm

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules (CSM) for Observability Helm chart bootstraps an Observability deployment on a Kubernetes cluster using the Helm package manager.

Prerequisites

Helm 3.x
The deployment of one or more supported Dell CSI drivers

Mon, 01 Jan 0001 00:00:00 +0000

Verify the Cert-Manager is deployed and configured on the OpenShift Cluster. Please review the Red Hat documentation for the procedure.
Verify the user workload monitoring is enabled and configured on the OpenShift Cluster. Please review Red Hat documentation for the procedure to configure user workload monitoring on the OpenShift Cluster.
Enable Observability module in the CSM

Use this command to create the ContainerStorageModule custom resource with Observability enabled.
```
oc create -f csm-vxflexos.yaml
```
Example:

Observability

Mon, 01 Jan 0001 00:00:00 +0000

Verify the Cert-Manager is deployed and configured on the OpenShift Cluster. Please review the Red Hat documentation for the procedure.
Verify the user workload monitoring is enabled and configured on the OpenShift Cluster. Please review Red Hat documentation for the procedure to configure user workload monitoring on the OpenShift Cluster.
Enable Observability module in the CSM

Use this command to create the ContainerStorageModule custom resource with Observability enabled.
```
oc create -f csm-powermax.yaml
```
Example:

Observability

Mon, 01 Jan 0001 00:00:00 +0000

Verify the Cert-Manager is deployed and configured on the OpenShift Cluster. Please review the Red Hat documentation for the procedure.
Verify the user workload monitoring is enabled and configured on the OpenShift Cluster. Please review Red Hat documentation for the procedure to configure user workload monitoring on the OpenShift Cluster.
Enable Observability module in the CSM

Use this command to create the ContainerStorageModule custom resource with Observability enabled.
```
oc create -f csm-isilon.yaml
```
Example:

Observability

Mon, 01 Jan 0001 00:00:00 +0000

Verify the Cert-Manager is deployed and configured on the OpenShift Cluster. Please review the Red Hat documentation for the procedure.
Verify the user workload monitoring is enabled and configured on the OpenShift Cluster. Please review Red Hat documentation for the procedure to configure user workload monitoring on the OpenShift Cluster.
Enable Observability module in the CSM

Use this command to create the ContainerStorageModule custom resource with Observability enabled.
```
oc create -f csm-powerstore.yaml
```
Example:

Observability

Mon, 01 Jan 0001 00:00:00 +0000

Uninstall the CSM for Observability Helm Chart

The command below removes all the Kubernetes components associated with the chart.

helm delete karavi-observability --namespace [CSM_NAMESPACE]

You may also want to uninstall the CRDs created for cert-manager.

Observability

Mon, 01 Jan 0001 00:00:00 +0000

Uninstall the CSM for Observability Helm Chart

The command below removes all the Kubernetes components associated with the chart.

helm delete karavi-observability --namespace [CSM_NAMESPACE]

You may also want to uninstall the CRDs created for cert-manager.

Observability

Mon, 01 Jan 0001 00:00:00 +0000

Uninstall the CSM for Observability Helm Chart

The command below removes all the Kubernetes components associated with the chart.

helm delete karavi-observability --namespace [CSM_NAMESPACE]

You may also want to uninstall the CRDs created for cert-manager.

Observability

Mon, 01 Jan 0001 00:00:00 +0000

Uninstall the CSM for Observability Helm Chart

The command below removes all the Kubernetes components associated with the chart.

helm delete karavi-observability --namespace [CSM_NAMESPACE]

Enable the Observability module with the following configuration:

Offline Installer for Observability

Mon, 01 Jan 0001 00:00:00 +0000

Observability

Mon, 01 Jan 0001 00:00:00 +0000

Verify the Cert-Manager is deployed and configured on the OpenShift Cluster. Please review the Red Hat documentation for the procedure.
Verify the user workload monitoring is enabled and configured on the OpenShift Cluster. Please review Red Hat documentation for the procedure to configure user workload monitoring on the OpenShift Cluster.
Enable Observability module in the CSM

Use this command to create the ContainerStorageModule custom resource with Observability enabled.
```
oc create -f csm-vxflexos.yaml
```
Example:

Observability

Mon, 01 Jan 0001 00:00:00 +0000

Verify the Cert-Manager is deployed and configured on the OpenShift Cluster. Please review the Red Hat documentation for the procedure.
Verify the user workload monitoring is enabled and configured on the OpenShift Cluster. Please review Red Hat documentation for the procedure to configure user workload monitoring on the OpenShift Cluster.
Enable Observability module in the CSM

Use this command to create the ContainerStorageModule custom resource with Observability enabled.
```
oc create -f csm-powermax.yaml
```
Example:

Observability

Mon, 01 Jan 0001 00:00:00 +0000

Verify the Cert-Manager is deployed and configured on the OpenShift Cluster. Please review the Red Hat documentation for the procedure.
Verify the user workload monitoring is enabled and configured on the OpenShift Cluster. Please review Red Hat documentation for the procedure to configure user workload monitoring on the OpenShift Cluster.
Enable Observability module in the CSM

Use this command to create the ContainerStorageModule custom resource with Observability enabled.
```
oc create -f csm-isilon.yaml
```
Example:

Observability

Mon, 01 Jan 0001 00:00:00 +0000

Verify the Cert-Manager is deployed and configured on the OpenShift Cluster. Please review the Red Hat documentation for the procedure.
Verify the user workload monitoring is enabled and configured on the OpenShift Cluster. Please review Red Hat documentation for the procedure to configure user workload monitoring on the OpenShift Cluster.
Enable Observability module in the CSM

Use this command to create the ContainerStorageModule custom resource with Observability enabled.
```
oc create -f csm-powerstore.yaml
```
Example:

Observability

Mon, 01 Jan 0001 00:00:00 +0000

Uninstall the CSM for Observability Helm Chart

The command below removes all the Kubernetes components associated with the chart.

helm delete karavi-observability --namespace [CSM_NAMESPACE]

You may also want to uninstall the CRDs created for cert-manager.

Observability

Mon, 01 Jan 0001 00:00:00 +0000

Uninstall the CSM for Observability Helm Chart

The command below removes all the Kubernetes components associated with the chart.

helm delete karavi-observability --namespace [CSM_NAMESPACE]

You may also want to uninstall the CRDs created for cert-manager.

Observability

Mon, 01 Jan 0001 00:00:00 +0000

Uninstall the CSM for Observability Helm Chart

The command below removes all the Kubernetes components associated with the chart.

helm delete karavi-observability --namespace [CSM_NAMESPACE]

You may also want to uninstall the CRDs created for cert-manager.

Observability

Mon, 01 Jan 0001 00:00:00 +0000

Uninstall the CSM for Observability Helm Chart

The command below removes all the Kubernetes components associated with the chart.

helm delete karavi-observability --namespace [CSM_NAMESPACE]

Create a namespace karavi

Offline Installer for Observability

Mon, 01 Jan 0001 00:00:00 +0000

Observability

Mon, 01 Jan 0001 00:00:00 +0000

Verify the Cert-Manager is deployed and configured on the OpenShift Cluster. Please review the Red Hat documentation for the procedure.
Verify the user workload monitoring is enabled and configured on the OpenShift Cluster. Please review Red Hat documentation for the procedure to configure user workload monitoring on the OpenShift Cluster.
Create a Project for deploying Observability Module

Use this command to create new project. You must use the project name as karavi

Observability

Mon, 01 Jan 0001 00:00:00 +0000

Verify the Cert-Manager is deployed and configured on the OpenShift Cluster. Please review the Red Hat documentation for the procedure.
Verify the user workload monitoring is enabled and configured on the OpenShift Cluster. Please review Red Hat documentation for the procedure to configure user workload monitoring on the OpenShift Cluster.
Create a Project for deploying Observability Module

Use this command to create new project. You must use the project name as karavi

Observability

Mon, 01 Jan 0001 00:00:00 +0000

Verify the Cert-Manager is deployed and configured on the OpenShift Cluster. Please review the Red Hat documentation for the procedure.
Verify the user workload monitoring is enabled and configured on the OpenShift Cluster. Please review Red Hat documentation for the procedure to configure user workload monitoring on the OpenShift Cluster.
Create a Project for deploying Observability Module

Use this command to create new project. You must use the project name as karavi

Observability

Mon, 01 Jan 0001 00:00:00 +0000

Uninstall the CSM for Observability Helm Chart

The command below removes all the Kubernetes components associated with the chart.

helm delete karavi-observability --namespace [CSM_NAMESPACE]

You may also want to uninstall the CRDs created for cert-manager.

Observability

Mon, 01 Jan 0001 00:00:00 +0000

Uninstall the CSM for Observability Helm Chart

The command below removes all the Kubernetes components associated with the chart.

helm delete karavi-observability --namespace [CSM_NAMESPACE]

You may also want to uninstall the CRDs created for cert-manager.

Observability

Mon, 01 Jan 0001 00:00:00 +0000

Uninstall the CSM for Observability Helm Chart

The command below removes all the Kubernetes components associated with the chart.

helm delete karavi-observability --namespace [CSM_NAMESPACE]

You may also want to uninstall the CRDs created for cert-manager.

Observability

Mon, 01 Jan 0001 00:00:00 +0000

Uninstall the CSM for Observability Helm Chart

The command below removes all the Kubernetes components associated with the chart.

helm delete karavi-observability --namespace [CSM_NAMESPACE]

To upgrade an existing Helm installation of CSM for Observability to the latest release, download the latest Helm charts.

Observability

Mon, 01 Jan 0001 00:00:00 +0000

This section outlines the uninstallation steps for Container Storage Modules (CSM) for Observability.

Uninstall the CSM for Observability Helm Chart

The command below removes all the Kubernetes components associated with the chart.

helm delete karavi-observability --namespace [CSM_NAMESPACE]

You may also want to uninstall the CRDs created for cert-manager.

Observability

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

This section outlines the upgrade steps for Container Storage Modules (CSM) for Observability. CSM for Observability upgrade can be achieved in one of two ways:

Helm Chart Upgrade
Online Installer Upgrade

The following third-party components are required in the same Kubernetes cluster where Container Storage Modules Observability has been deployed:

There are various ways to deploy these components. We recommend following the Helm deployments according to the specifications defined below.

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Uninstallation through driver upgrade

Disable the podmon feature in your values file

podmon: 
  enabled: false

Upgrade the driver
- Helm

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Uninstallation through driver upgrade

Disable the podmon feature in your values file

podmon: 
  enabled: false

Upgrade the driver
- Helm

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Uninstallation through driver upgrade

Disable the podmon feature in your values file

podmon: 
  enabled: false

Upgrade the driver
- Helm

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Uninstallation through driver upgrade

Disable the podmon feature in your values file

podmon: 
  enabled: false

Upgrade the driver
- Helm

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Uninstallation through driver upgrade

Disable the podmon feature in your values file

podmon: 
  enabled: false

Upgrade the driver
- Helm

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Mon, 01 Jan 0001 00:00:00 +0000

Uninstallation through driver upgrade

Disable the podmon feature in your values file

podmon: 
  enabled: false

Upgrade the driver
- Helm

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Uninstallation through driver upgrade

Disable the podmon feature in your values file

podmon: 
  enabled: false

Upgrade the driver
- Helm

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Uninstallation through driver upgrade

Disable the podmon feature in your values file

podmon: 
  enabled: false

Upgrade the driver
- Helm

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Uninstallation through driver upgrade

Disable the podmon feature in your values file

podmon: 
  enabled: false

Upgrade the driver
- Helm

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Uninstallation through driver upgrade

Disable the podmon feature in your values file

podmon: 
  enabled: false

Upgrade the driver
- Helm

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Uninstallation through driver upgrade

Disable the podmon feature in your values file

podmon: 
  enabled: false

Upgrade the driver
- Helm

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Uninstallation through driver upgrade

Disable the podmon feature in your values file

podmon: 
  enabled: false

Upgrade the driver
- Helm

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Uninstallation through driver upgrade

Disable the podmon feature in your values file

podmon: 
  enabled: false

Upgrade the driver
- Helm

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Uninstallation through driver upgrade

Disable the podmon feature in your values file

podmon: 
  enabled: false

Upgrade the driver
- Helm

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Uninstallation through driver upgrade

Disable the podmon feature in your values file

podmon: 
  enabled: false

Upgrade the driver
- Helm

Backup and Restore an Application

This example details the steps when an application in namespace demo1 is being backed up and then later restored to either the same cluster or another cluster. In this sample, both Application Mobility and Velero are installed in the application-mobility namespace.

Use Cases

Mon, 01 Jan 0001 00:00:00 +0000

Backup and Restore an Application

CLI

Mon, 01 Jan 0001 00:00:00 +0000

As of Container Storage Modules v1.15, Authorization v1.x will not be supported. Please migrate to Authorization v2.0 using the following guide.

karavictl is a command-line interface (CLI) used to interact with and manage your Container Storage Modules (CSM) Authorization deployment. This document outlines all karavictl commands, their intended use, options that can be provided to alter their execution, and expected output from those commands.

If you feel that something is unclear or missing in this document, please open up an issue.

CLI

Mon, 01 Jan 0001 00:00:00 +0000

As of Container Storage Modules v1.15, Authorization v1.x will not be supported. Please migrate to Authorization v2.0 using the following guide.

If you feel that something is unclear or missing in this document, please open up an issue.

Disaster Recovery

Mon, 01 Jan 0001 00:00:00 +0000

Disaster Recovery Workflows

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Install Replication Walkthrough

NOTE: These steps should be repeated on all Kubernetes clusters where you want to configure replication.

git clone -b v1.14.0 https://github.com/dell/csm-replication.git
cd csm-replication
kubectl create ns dell-replication-controller
# Download and modify the default values.yaml file if you wish to customize your deployment in any way
wget -O myvalues.yaml https://raw.githubusercontent.com/dell/helm-charts/csm-replication-1.14.0/charts/csm-replication/values.yaml
bash scripts/install.sh --values ./myvalues.yaml

Note: Current installation method allows you to specify custom <FQDN>:<IP> entries to be appended to controller’s /etc/hosts file. It can be useful if controller is being deployed in private environment where DNS is not set up properly, but kubernetes clusters use FQDN as API server’s address. The feature can be enabled by modifying values.yaml.

Installation using script

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Install Replication Walkthrough

NOTE: These steps should be repeated on all Kubernetes clusters where you want to configure replication.

git clone -b v1.14.0 https://github.com/dell/csm-replication.git
cd csm-replication
kubectl create ns dell-replication-controller
# Download and modify the default values.yaml file if you wish to customize your deployment in any way
wget -O myvalues.yaml https://raw.githubusercontent.com/dell/helm-charts/csm-replication-1.14.0/charts/csm-replication/values.yaml
bash scripts/install.sh --values ./myvalues.yaml

Note: Current installation method allows you to specify custom <FQDN>:<IP> entries to be appended to controller’s /etc/hosts file. It can be useful if controller is being deployed in private environment where DNS is not set up properly, but kubernetes clusters use FQDN as API server’s address. The feature can be enabled by modifying values.yaml.

Installation using script

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Install Replication Walkthrough

NOTE: These steps should be repeated on all Kubernetes clusters where you want to configure replication.

git clone -b v1.14.0 https://github.com/dell/csm-replication.git
cd csm-replication
kubectl create ns dell-replication-controller
# Download and modify the default values.yaml file if you wish to customize your deployment in any way
wget -O myvalues.yaml https://raw.githubusercontent.com/dell/helm-charts/csm-replication-1.14.0/charts/csm-replication/values.yaml
bash scripts/install.sh --values ./myvalues.yaml

Note: Current installation method allows you to specify custom <FQDN>:<IP> entries to be appended to controller’s /etc/hosts file. It can be useful if controller is being deployed in private environment where DNS is not set up properly, but kubernetes clusters use FQDN as API server’s address. The feature can be enabled by modifying values.yaml.

Installation using script

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Install Replication Walkthrough

NOTE: These steps should be repeated on all Kubernetes clusters where you want to configure replication.

git clone -b v1.14.0 https://github.com/dell/csm-replication.git
cd csm-replication
kubectl create ns dell-replication-controller
# Download and modify the default values.yaml file if you wish to customize your deployment in any way
wget -O myvalues.yaml https://raw.githubusercontent.com/dell/helm-charts/csm-replication-1.14.0/charts/csm-replication/values.yaml
bash scripts/install.sh --values ./myvalues.yaml

Note: Current installation method allows you to specify custom <FQDN>:<IP> entries to be appended to controller’s /etc/hosts file. It can be useful if controller is being deployed in private environment where DNS is not set up properly, but kubernetes clusters use FQDN as API server’s address. The feature can be enabled by modifying values.yaml.

Installation using script

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Install Replication Walkthrough

NOTE: These steps should be repeated on all Kubernetes clusters where you want to configure replication.

git clone -b v1.14.0 https://github.com/dell/csm-replication.git
cd csm-replication
kubectl create ns dell-replication-controller
# Download and modify the default values.yaml file if you wish to customize your deployment in any way
wget -O myvalues.yaml https://raw.githubusercontent.com/dell/helm-charts/csm-replication-1.14.0/charts/csm-replication/values.yaml
bash scripts/install.sh --values ./myvalues.yaml

Note: Current installation method allows you to specify custom <FQDN>:<IP> entries to be appended to controller’s /etc/hosts file. It can be useful if controller is being deployed in private environment where DNS is not set up properly, but kubernetes clusters use FQDN as API server’s address. The feature can be enabled by modifying values.yaml.

Installation using script

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Install Replication Walkthrough

NOTE: These steps should be repeated on all Kubernetes clusters where you want to configure replication.

git clone -b v1.13.0 https://github.com/dell/csm-replication.git
cd csm-replication
kubectl create ns dell-replication-controller
# Download and modify the default values.yaml file if you wish to customize your deployment in any way
wget -O myvalues.yaml https://raw.githubusercontent.com/dell/helm-charts/csm-replication-1.13.0/charts/csm-replication/values.yaml
bash scripts/install.sh --values ./myvalues.yaml

Note: Current installation method allows you to specify custom <FQDN>:<IP> entries to be appended to controller’s /etc/hosts file. It can be useful if controller is being deployed in private environment where DNS is not set up properly, but kubernetes clusters use FQDN as API server’s address. The feature can be enabled by modifying values.yaml.

Installation using script

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Install Replication Walkthrough

NOTE: These steps should be repeated on all Kubernetes clusters where you want to configure replication.

git clone -b v1.13.0 https://github.com/dell/csm-replication.git
cd csm-replication
kubectl create ns dell-replication-controller
# Download and modify the default values.yaml file if you wish to customize your deployment in any way
wget -O myvalues.yaml https://raw.githubusercontent.com/dell/helm-charts/csm-replication-1.13.0/charts/csm-replication/values.yaml
bash scripts/install.sh --values ./myvalues.yaml

Note: Current installation method allows you to specify custom <FQDN>:<IP> entries to be appended to controller’s /etc/hosts file. It can be useful if controller is being deployed in private environment where DNS is not set up properly, but kubernetes clusters use FQDN as API server’s address. The feature can be enabled by modifying values.yaml.

Installation using script

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Install Replication Walkthrough

NOTE: These steps should be repeated on all Kubernetes clusters where you want to configure replication.

git clone -b v1.13.0 https://github.com/dell/csm-replication.git
cd csm-replication
kubectl create ns dell-replication-controller
# Download and modify the default values.yaml file if you wish to customize your deployment in any way
wget -O myvalues.yaml https://raw.githubusercontent.com/dell/helm-charts/csm-replication-1.13.0/charts/csm-replication/values.yaml
bash scripts/install.sh --values ./myvalues.yaml

Note: Current installation method allows you to specify custom <FQDN>:<IP> entries to be appended to controller’s /etc/hosts file. It can be useful if controller is being deployed in private environment where DNS is not set up properly, but kubernetes clusters use FQDN as API server’s address. The feature can be enabled by modifying values.yaml.

Installation using script

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Install Replication Walkthrough

NOTE: These steps should be repeated on all Kubernetes clusters where you want to configure replication.

git clone -b v1.13.0 https://github.com/dell/csm-replication.git
cd csm-replication
kubectl create ns dell-replication-controller
# Download and modify the default values.yaml file if you wish to customize your deployment in any way
wget -O myvalues.yaml https://raw.githubusercontent.com/dell/helm-charts/csm-replication-1.13.0/charts/csm-replication/values.yaml
bash scripts/install.sh --values ./myvalues.yaml

Note: Current installation method allows you to specify custom <FQDN>:<IP> entries to be appended to controller’s /etc/hosts file. It can be useful if controller is being deployed in private environment where DNS is not set up properly, but kubernetes clusters use FQDN as API server’s address. The feature can be enabled by modifying values.yaml.

Installation using script

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Install Replication Walkthrough

NOTE: These steps should be repeated on all Kubernetes clusters where you want to configure replication.

git clone -b v1.13.0 https://github.com/dell/csm-replication.git
cd csm-replication
kubectl create ns dell-replication-controller
# Download and modify the default values.yaml file if you wish to customize your deployment in any way
wget -O myvalues.yaml https://raw.githubusercontent.com/dell/helm-charts/csm-replication-1.13.0/charts/csm-replication/values.yaml
bash scripts/install.sh --values ./myvalues.yaml

Note: Current installation method allows you to specify custom <FQDN>:<IP> entries to be appended to controller’s /etc/hosts file. It can be useful if controller is being deployed in private environment where DNS is not set up properly, but kubernetes clusters use FQDN as API server’s address. The feature can be enabled by modifying values.yaml.

Installation using script

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Install Replication Walkthrough

NOTE: These steps should be repeated on all Kubernetes clusters where you want to configure replication.

git clone -b v1.12.0 https://github.com/dell/csm-replication.git
cd csm-replication
kubectl create ns dell-replication-controller
# Download and modify the default values.yaml file if you wish to customize your deployment in any way
wget -O myvalues.yaml https://raw.githubusercontent.com/dell/helm-charts/csm-replication-1.12.0/charts/csm-replication/values.yaml
bash scripts/install.sh --values ./myvalues.yaml

Note: Current installation method allows you to specify custom <FQDN>:<IP> entries to be appended to controller’s /etc/hosts file. It can be useful if controller is being deployed in private environment where DNS is not set up properly, but kubernetes clusters use FQDN as API server’s address. The feature can be enabled by modifying values.yaml.

Installation using script

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Install Replication Walkthrough

NOTE: These steps should be repeated on all Kubernetes clusters where you want to configure replication.

git clone -b v1.12.0 https://github.com/dell/csm-replication.git
cd csm-replication
kubectl create ns dell-replication-controller
# Download and modify the default values.yaml file if you wish to customize your deployment in any way
wget -O myvalues.yaml https://raw.githubusercontent.com/dell/helm-charts/csm-replication-1.12.0/charts/csm-replication/values.yaml
bash scripts/install.sh --values ./myvalues.yaml

Note: Current installation method allows you to specify custom <FQDN>:<IP> entries to be appended to controller’s /etc/hosts file. It can be useful if controller is being deployed in private environment where DNS is not set up properly, but kubernetes clusters use FQDN as API server’s address. The feature can be enabled by modifying values.yaml.

Installation using script

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Install Replication Walkthrough

NOTE: These steps should be repeated on all Kubernetes clusters where you want to configure replication.

git clone -b v1.12.0 https://github.com/dell/csm-replication.git
cd csm-replication
kubectl create ns dell-replication-controller
# Download and modify the default values.yaml file if you wish to customize your deployment in any way
wget -O myvalues.yaml https://raw.githubusercontent.com/dell/helm-charts/csm-replication-1.12.0/charts/csm-replication/values.yaml
bash scripts/install.sh --values ./myvalues.yaml

Note: Current installation method allows you to specify custom <FQDN>:<IP> entries to be appended to controller’s /etc/hosts file. It can be useful if controller is being deployed in private environment where DNS is not set up properly, but kubernetes clusters use FQDN as API server’s address. The feature can be enabled by modifying values.yaml.

Installation using script

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Install Replication Walkthrough

NOTE: These steps should be repeated on all Kubernetes clusters where you want to configure replication.

git clone -b v1.12.0 https://github.com/dell/csm-replication.git
cd csm-replication
kubectl create ns dell-replication-controller
# Download and modify the default values.yaml file if you wish to customize your deployment in any way
wget -O myvalues.yaml https://raw.githubusercontent.com/dell/helm-charts/csm-replication-1.12.0/charts/csm-replication/values.yaml
bash scripts/install.sh --values ./myvalues.yaml

Note: Current installation method allows you to specify custom <FQDN>:<IP> entries to be appended to controller’s /etc/hosts file. It can be useful if controller is being deployed in private environment where DNS is not set up properly, but kubernetes clusters use FQDN as API server’s address. The feature can be enabled by modifying values.yaml.

Installation using script

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Install Replication Walkthrough

NOTE: These steps should be repeated on all Kubernetes clusters where you want to configure replication.

git clone -b v1.12.0 https://github.com/dell/csm-replication.git
cd csm-replication
kubectl create ns dell-replication-controller
# Download and modify the default values.yaml file if you wish to customize your deployment in any way
wget -O myvalues.yaml https://raw.githubusercontent.com/dell/helm-charts/csm-replication-1.12.0/charts/csm-replication/values.yaml
bash scripts/install.sh --values ./myvalues.yaml

Note: Current installation method allows you to specify custom <FQDN>:<IP> entries to be appended to controller’s /etc/hosts file. It can be useful if controller is being deployed in private environment where DNS is not set up properly, but kubernetes clusters use FQDN as API server’s address. The feature can be enabled by modifying values.yaml.

Installation using script

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Install Replication Walkthrough

NOTE: These steps should be repeated on all Kubernetes clusters where you want to configure replication.

git clone -b v1.11.0 https://github.com/dell/csm-replication.git
cd csm-replication
kubectl create ns dell-replication-controller
# Download and modify the default values.yaml file if you wish to customize your deployment in any way
wget -O myvalues.yaml https://raw.githubusercontent.com/dell/helm-charts/csm-replication-1.11.0/charts/csm-replication/values.yaml
bash scripts/install.sh --values ./myvalues.yaml

Note: Current installation method allows you to specify custom <FQDN>:<IP> entries to be appended to controller’s /etc/hosts file. It can be useful if controller is being deployed in private environment where DNS is not set up properly, but kubernetes clusters use FQDN as API server’s address. The feature can be enabled by modifying values.yaml.

Offline Dependencies

Mon, 01 Jan 0001 00:00:00 +0000

The csi-offline-bundle.sh script creates a package for offline installation of Dell CSI Storage Providers using Helm or the Dell CSM Operator.

Dependencies

Multiple Linux systems may be needed.
- One system with Internet access to create the bundle:Clone a GitHub repository.
- Run a script using Docker or Podman to pull and save container images.
- One system with access to an image registry to : Run a script using Docker or Podman to restore and push images to the registry.
RedHat credentials to pull openshift4/ose-kube-rbac-proxy-rhel9 image from registry.redhat.io (no unauthenticated access).

If one system has both Internet access and registry access, it can be used for both steps.

Offline Dependencies

Mon, 01 Jan 0001 00:00:00 +0000

The csi-offline-bundle.sh script creates a package for offline installation of Dell CSI Storage Providers using Helm or the Dell CSM Operator.

Dependencies

Multiple Linux systems may be needed.
- One system with Internet access to create the bundle:Clone a GitHub repository.
- Run a script using Docker or Podman to pull and save container images.
- One system with access to an image registry to : Run a script using Docker or Podman to restore and push images to the registry.
RedHat credentials to pull openshift4/ose-kube-rbac-proxy-rhel9 image from registry.redhat.io (no unauthenticated access).

If one system has both Internet access and registry access, it can be used for both steps.

Offline Dependencies

Mon, 01 Jan 0001 00:00:00 +0000

The csi-offline-bundle.sh script creates a package for offline installation of Dell CSI Storage Providers using Helm or the Dell CSM Operator.

Dependencies

Multiple Linux systems may be needed.
- One system with Internet access to create the bundle:Clone a GitHub repository.
- Run a script using Docker or Podman to pull and save container images.
- One system with access to an image registry to : Run a script using Docker or Podman to restore and push images to the registry.
RedHat credentials to pull openshift4/ose-kube-rbac-proxy-rhel9 image from registry.redhat.io (no unauthenticated access).

If one system has both Internet access and registry access, it can be used for both steps.

Offline Helm Installation

Mon, 01 Jan 0001 00:00:00 +0000

Workflow

To perform an offline installation :

Build an offline bundle
Unpack the offline bundle and prepare for installation.
Install Container Storage Modules using the unpacked files.

NOTE: Use the same tool (docker or podman) for packing and unpacking images.

Offline Helm Installation

Mon, 01 Jan 0001 00:00:00 +0000

Workflow

To perform an offline installation :

Build an offline bundle
Unpack the offline bundle and prepare for installation.
Install Container Storage Modules using the unpacked files.

NOTE: Use the same tool (docker or podman) for packing and unpacking images.

Offline Helm Installation

Mon, 01 Jan 0001 00:00:00 +0000

Workflow

To perform an offline installation :

Build an offline bundle
Unpack the offline bundle and prepare for installation.
Install Container Storage Modules using the unpacked files.

NOTE: Use the same tool (docker or podman) for packing and unpacking images.

Offline Operator Installation

Mon, 01 Jan 0001 00:00:00 +0000

Workflow

To perform an offline installation :

Build an offline bundle
Unpack the offline bundle and prepare for installation.
Install operator using the unpacked files.
Install Container Storage Modules using the unpacked files.
Installing Dell CSM Operator on a disconnected OpenShift environment

NOTE: Use the same tool (docker or podman) for packing and unpacking images.

Offline Operator Installation

Mon, 01 Jan 0001 00:00:00 +0000

Workflow

To perform an offline installation :

Build an offline bundle
Unpack the offline bundle and prepare for installation.
Install operator using the unpacked files.
Install Container Storage Modules using the unpacked files.

NOTE: Use the same tool (docker or podman) for packing and unpacking images.

Offline Operator Installation

Mon, 01 Jan 0001 00:00:00 +0000

Workflow

To perform an offline installation :

Build an offline bundle
Unpack the offline bundle and prepare for installation.
Install operator using the unpacked files.
Install Container Storage Modules using the unpacked files.

NOTE: Use the same tool (docker or podman) for packing and unpacking images.

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules Operator installs the Replication module for supported Dell CSI Drivers, deploying the Replication sidecar and Controller Manage.

Note: In PowerFlex 5.0, the Replication feature is not supported.

Note: In PowerFlex 5.0, the Replication feature is not supported.

Mon, 01 Jan 0001 00:00:00 +0000

Troubleshooting

Mon, 01 Jan 0001 00:00:00 +0000

Troubleshooting

Mon, 01 Jan 0001 00:00:00 +0000

Some tools have been provided in the tools directory that will help you understand the system’s state and facilitate troubleshooting. If you experience a problem with CSM for Resiliency it is important you provide us with as much information as possible so that we can diagnose the issue and improve CSM for Resiliency. Some tools have been provided in the tools directory that will help you understand the system’s state and facilitate sending us the logs and other information needed to diagnose a problem.

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules Operator installs the Resiliency module for supported Dell CSI Drivers, deploying the Resiliency sidecar.

Prerequisite

The Resiliency module only acts on pods with a specific label. At startup, it logs the label key and value. Apply this label to the StatefulSet you want monitored

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

CSM for Resiliency is installed as part of the Dell CSI driver installation.

For information on the PowerFlex CSI driver, see PowerFlex CSI Driver.

Prerequisite

The CSM for Resiliency module only acts on pods with a specific label.
This label must match the key and value set in the module’s configuration.
On startup, CSM for Resiliency logs the label key and value it uses to monitor pods.
Apply this label to the Statefulset you want monitored by CSM for Resiliency.

labelSelector: {map[podmon.dellemc.com/driver:csi-<driver>]}

The above message indicates the key is: podmon.dellemc.com/driver and the label value is csi-<driver>. To search for the pods that would be monitored, try this:

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules Operator installs the Resiliency module for supported Dell CSI Drivers, deploying the Resiliency sidecar.

Prerequisite

The Resiliency module only acts on pods with a specific label. At startup, it logs the label key and value. Apply this label to the StatefulSet you want monitored

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

CSM for Resiliency is installed as part of the Dell CSI driver installation.

For information on the PowerStore CSI driver, see PowerMax CSI Driver.

Prerequisite

The CSM for Resiliency module only acts on pods with a specific label.
This label must match the key and value set in the module’s configuration.
On startup, CSM for Resiliency logs the label key and value it uses to monitor pods.
Apply this label to the Statefulset you want monitored by CSM for Resiliency.

labelSelector: {map[podmon.dellemc.com/driver:csi-<driver>]}

The above message indicates the key is: podmon.dellemc.com/driver and the label value is csi-<driver>. To search for the pods that would be monitored, try this:

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules Operator installs the Resiliency module for supported Dell CSI Drivers, deploying the Resiliency sidecar.

Prerequisite

The Resiliency module only acts on pods with a specific label. At startup, it logs the label key and value. Apply this label to the StatefulSet you want monitored

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

CSM for Resiliency is installed as part of the Dell CSI driver installation.

For information on the PowerScale CSI driver, see PowerScale CSI Driver.

Prerequisite

The CSM for Resiliency module only acts on pods with a specific label.
This label must match the key and value set in the module’s configuration.
On startup, CSM for Resiliency logs the label key and value it uses to monitor pods.
Apply this label to the Statefulset you want monitored by CSM for Resiliency.

labelSelector: {map[podmon.dellemc.com/driver:csi-<driver>]}

The above message indicates the key is: podmon.dellemc.com/driver and the label value is csi-<driver>. To search for the pods that would be monitored, try this:

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules Operator installs the Resiliency module for supported Dell CSI Drivers, deploying the Resiliency sidecar.

Prerequisite

The Resiliency module only acts on pods with a specific label. At startup, it logs the label key and value. Apply this label to the StatefulSet you want monitored

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

CSM for Resiliency is installed as part of the Dell CSI driver installation.

For information on the PowerStore CSI driver, see PowerStore CSI Driver.

Prerequisite

The CSM for Resiliency module only acts on pods with a specific label.
This label must match the key and value set in the module’s configuration.
On startup, CSM for Resiliency logs the label key and value it uses to monitor pods.
Apply this label to the Statefulset you want monitored by CSM for Resiliency.

labelSelector: {map[podmon.dellemc.com/driver:csi-<driver>]}

The above message indicates the key is: podmon.dellemc.com/driver and the label value is csi-<driver>. To search for the pods that would be monitored, try this:

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

CSM for Resiliency is installed as part of the Dell CSI driver installation.

For information on the Unity XT CSI driver, see Unity XT CSI Driver.

Prerequisite

The CSM for Resiliency module only acts on pods with a specific label.
This label must match the key and value set in the module’s configuration.
On startup, CSM for Resiliency logs the label key and value it uses to monitor pods.
Apply this label to the Statefulset you want monitored by CSM for Resiliency.

labelSelector: {map[podmon.dellemc.com/driver:csi-<driver>]}

The above message indicates the key is: podmon.dellemc.com/driver and the label value is csi-<driver>. To search for the pods that would be monitored, try this:

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Enable Resiliency Module

Use this command to create the ContainerStorageModule Custom Resource with Resiliency:

oc create -f csm-vxflexos.yaml

Example:

cat << EOF > csm-vxflexos.yaml
apiVersion: storage.dell.com/v1
kind: ContainerStorageModule
metadata:
  name: vxflexos
  namespace: vxflexos
spec:
  driver:
    csiDriverType: "powerflex"
    configVersion: Default text if no valid parameter is passed.
  modules:
  - name: resiliency
    enabled: true
EOF

Detailed Configuration: Use the sample file for detailed settings.

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules Operator installs the Resiliency module for supported Dell CSI Drivers, deploying the Resiliency sidecar.

Prerequisite

The Resiliency module only acts on pods with a specific label. At startup, it logs the label key and value. Apply this label to the StatefulSet you want monitored

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Enable Resiliency Module

Use this command to create the ContainerStorageModule Custom Resource with Resiliency:

oc create -f csm-isilon.yaml

Example:

cat << EOF > csm-isilon.yaml
apiVersion: storage.dell.com/v1
kind: ContainerStorageModule
metadata:
  name: isilon
  namespace: isilon
spec:
  driver:
    csiDriverType: "powerscale"
    configVersion: Default text if no valid parameter is passed.
  modules:
  - name: resiliency
    enabled: true
EOF

Detailed Configuration: Use the sample file for detailed settings.

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Enable Resiliency Module

Use this command to create the ContainerStorageModule Custom Resource with Resiliency:

oc create -f csm-powerstore.yaml

Example:

cat << EOF > csm-powerstore.yaml
apiVersion: storage.dell.com/v1
kind: ContainerStorageModule
metadata:
  name: powerstore
  namespace: powerstore
spec:
  driver:
    csiDriverType: "powerstore"
    configVersion: Default text if no valid parameter is passed.
  modules:
  - name: resiliency
    enabled: true
EOF

Detailed Configuration: Use the sample file for detailed settings.

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules Operator installs the Resiliency module for supported Dell CSI Drivers, deploying the Resiliency sidecar.

Prerequisite

The Resiliency module only acts on pods with a specific label. At startup, it logs the label key and value. Apply this label to the StatefulSet you want monitored

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

CSM for Resiliency is installed as part of the Dell CSI driver installation.

For information on the PowerFlex CSI driver, see PowerFlex CSI Driver.

Prerequisite

The CSM for Resiliency module only acts on pods with a specific label.
This label must match the key and value set in the module’s configuration.
On startup, CSM for Resiliency logs the label key and value it uses to monitor pods.
Apply this label to the Statefulset you want monitored by CSM for Resiliency.

labelSelector: {map[podmon.dellemc.com/driver:csi-<driver>]}

The above message indicates the key is: podmon.dellemc.com/driver and the label value is csi-<driver>. To search for the pods that would be monitored, try this:

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules Operator installs the Resiliency module for supported Dell CSI Drivers, deploying the Resiliency sidecar.

Prerequisite

The Resiliency module only acts on pods with a specific label. At startup, it logs the label key and value. Apply this label to the StatefulSet you want monitored

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

CSM for Resiliency is installed as part of the Dell CSI driver installation.

For information on the PowerStore CSI driver, see PowerMax CSI Driver.

Prerequisite

The CSM for Resiliency module only acts on pods with a specific label.
This label must match the key and value set in the module’s configuration.
On startup, CSM for Resiliency logs the label key and value it uses to monitor pods.
Apply this label to the Statefulset you want monitored by CSM for Resiliency.

labelSelector: {map[podmon.dellemc.com/driver:csi-<driver>]}

The above message indicates the key is: podmon.dellemc.com/driver and the label value is csi-<driver>. To search for the pods that would be monitored, try this:

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules Operator installs the Resiliency module for supported Dell CSI Drivers, deploying the Resiliency sidecar.

Prerequisite

The Resiliency module only acts on pods with a specific label. At startup, it logs the label key and value. Apply this label to the StatefulSet you want monitored

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

CSM for Resiliency is installed as part of the Dell CSI driver installation.

For information on the PowerScale CSI driver, see PowerScale CSI Driver.

Prerequisite

The CSM for Resiliency module only acts on pods with a specific label.
This label must match the key and value set in the module’s configuration.
On startup, CSM for Resiliency logs the label key and value it uses to monitor pods.
Apply this label to the Statefulset you want monitored by CSM for Resiliency.

labelSelector: {map[podmon.dellemc.com/driver:csi-<driver>]}

The above message indicates the key is: podmon.dellemc.com/driver and the label value is csi-<driver>. To search for the pods that would be monitored, try this:

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules Operator installs the Resiliency module for supported Dell CSI Drivers, deploying the Resiliency sidecar.

Prerequisite

The Resiliency module only acts on pods with a specific label. At startup, it logs the label key and value. Apply this label to the StatefulSet you want monitored

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

CSM for Resiliency is installed as part of the Dell CSI driver installation.

For information on the PowerStore CSI driver, see PowerStore CSI Driver.

Prerequisite

The CSM for Resiliency module only acts on pods with a specific label.
This label must match the key and value set in the module’s configuration.
On startup, CSM for Resiliency logs the label key and value it uses to monitor pods.
Apply this label to the Statefulset you want monitored by CSM for Resiliency.

labelSelector: {map[podmon.dellemc.com/driver:csi-<driver>]}

The above message indicates the key is: podmon.dellemc.com/driver and the label value is csi-<driver>. To search for the pods that would be monitored, try this:

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

CSM for Resiliency is installed as part of the Dell CSI driver installation.

For information on the Unity XT CSI driver, see Unity XT CSI Driver.

Prerequisite

The CSM for Resiliency module only acts on pods with a specific label.
This label must match the key and value set in the module’s configuration.
On startup, CSM for Resiliency logs the label key and value it uses to monitor pods.
Apply this label to the Statefulset you want monitored by CSM for Resiliency.

labelSelector: {map[podmon.dellemc.com/driver:csi-<driver>]}

The above message indicates the key is: podmon.dellemc.com/driver and the label value is csi-<driver>. To search for the pods that would be monitored, try this:

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Enable Resiliency Module

Use this command to create the ContainerStorageModule Custom Resource with Resiliency:

oc create -f csm-vxflexos.yaml

Example:

cat << EOF > csm-vxflexos.yaml
apiVersion: storage.dell.com/v1
kind: ContainerStorageModule
metadata:
  name: vxflexos
  namespace: vxflexos
spec:
  driver:
    csiDriverType: "powerflex"
    configVersion: Default text if no valid parameter is passed.
  modules:
  - name: resiliency
    enabled: true
EOF

Detailed Configuration: Use the sample file for detailed settings.

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules Operator installs the Resiliency module for supported Dell CSI Drivers, deploying the Resiliency sidecar.

Prerequisite

The Resiliency module only acts on pods with a specific label. At startup, it logs the label key and value. Apply this label to the StatefulSet you want monitored

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Enable Resiliency Module

Use this command to create the ContainerStorageModule Custom Resource with Resiliency:

oc create -f csm-isilon.yaml

Example:

cat << EOF > csm-isilon.yaml
apiVersion: storage.dell.com/v1
kind: ContainerStorageModule
metadata:
  name: isilon
  namespace: isilon
spec:
  driver:
    csiDriverType: "powerscale"
    configVersion: Default text if no valid parameter is passed.
  modules:
  - name: resiliency
    enabled: true
EOF

Detailed Configuration: Use the sample file for detailed settings.

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Enable Resiliency Module

Use this command to create the ContainerStorageModule Custom Resource with Resiliency:

oc create -f csm-powerstore.yaml

Example:

cat << EOF > csm-powerstore.yaml
apiVersion: storage.dell.com/v1
kind: ContainerStorageModule
metadata:
  name: powerstore
  namespace: powerstore
spec:
  driver:
    csiDriverType: "powerstore"
    configVersion: Default text if no valid parameter is passed.
  modules:
  - name: resiliency
    enabled: true
EOF

Detailed Configuration: Use the sample file for detailed settings.

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules Operator installs the Resiliency module for supported Dell CSI Drivers, deploying the Resiliency sidecar.

Prerequisite

The Resiliency module only acts on pods with a specific label. At startup, it logs the label key and value. Apply this label to the StatefulSet you want monitored

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

CSM for Resiliency is installed as part of the Dell CSI driver installation.

For information on the PowerFlex CSI driver, see PowerFlex CSI Driver.

Prerequisite

The CSM for Resiliency module only acts on pods with a specific label.
This label must match the key and value set in the module’s configuration.
On startup, CSM for Resiliency logs the label key and value it uses to monitor pods.
Apply this label to the Statefulset you want monitored by CSM for Resiliency.

labelSelector: {map[podmon.dellemc.com/driver:csi-<driver>]}

The above message indicates the key is: podmon.dellemc.com/driver and the label value is csi-<driver>. To search for the pods that would be monitored, try this:

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules Operator installs the Resiliency module for supported Dell CSI Drivers, deploying the Resiliency sidecar.

Prerequisite

The Resiliency module only acts on pods with a specific label. At startup, it logs the label key and value. Apply this label to the StatefulSet you want monitored

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

CSM for Resiliency is installed as part of the Dell CSI driver installation.

For information on the PowerStore CSI driver, see PowerMax CSI Driver.

Prerequisite

The CSM for Resiliency module only acts on pods with a specific label.
This label must match the key and value set in the module’s configuration.
On startup, CSM for Resiliency logs the label key and value it uses to monitor pods.
Apply this label to the Statefulset you want monitored by CSM for Resiliency.

labelSelector: {map[podmon.dellemc.com/driver:csi-<driver>]}

The above message indicates the key is: podmon.dellemc.com/driver and the label value is csi-<driver>. To search for the pods that would be monitored, try this:

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules Operator installs the Resiliency module for supported Dell CSI Drivers, deploying the Resiliency sidecar.

Prerequisite

The Resiliency module only acts on pods with a specific label. At startup, it logs the label key and value. Apply this label to the StatefulSet you want monitored

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

CSM for Resiliency is installed as part of the Dell CSI driver installation.

For information on the PowerScale CSI driver, see PowerScale CSI Driver.

Prerequisite

The CSM for Resiliency module only acts on pods with a specific label.
This label must match the key and value set in the module’s configuration.
On startup, CSM for Resiliency logs the label key and value it uses to monitor pods.
Apply this label to the Statefulset you want monitored by CSM for Resiliency.

labelSelector: {map[podmon.dellemc.com/driver:csi-<driver>]}

The above message indicates the key is: podmon.dellemc.com/driver and the label value is csi-<driver>. To search for the pods that would be monitored, try this:

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules Operator installs the Resiliency module for supported Dell CSI Drivers, deploying the Resiliency sidecar.

Prerequisite

The Resiliency module only acts on pods with a specific label. At startup, it logs the label key and value. Apply this label to the StatefulSet you want monitored

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

CSM for Resiliency is installed as part of the Dell CSI driver installation.

For information on the PowerStore CSI driver, see PowerStore CSI Driver.

Prerequisite

The CSM for Resiliency module only acts on pods with a specific label.
This label must match the key and value set in the module’s configuration.
On startup, CSM for Resiliency logs the label key and value it uses to monitor pods.
Apply this label to the Statefulset you want monitored by CSM for Resiliency.

labelSelector: {map[podmon.dellemc.com/driver:csi-<driver>]}

The above message indicates the key is: podmon.dellemc.com/driver and the label value is csi-<driver>. To search for the pods that would be monitored, try this:

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

CSM for Resiliency is installed as part of the Dell CSI driver installation.

For information on the Unity XT CSI driver, see Unity XT CSI Driver.

Prerequisite

The CSM for Resiliency module only acts on pods with a specific label.
This label must match the key and value set in the module’s configuration.
On startup, CSM for Resiliency logs the label key and value it uses to monitor pods.
Apply this label to the Statefulset you want monitored by CSM for Resiliency.

labelSelector: {map[podmon.dellemc.com/driver:csi-<driver>]}

The above message indicates the key is: podmon.dellemc.com/driver and the label value is csi-<driver>. To search for the pods that would be monitored, try this:

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Enable Resiliency Module

Use this command to create the ContainerStorageModule Custom Resource with Resiliency:

oc create -f csm-vxflexos.yaml

Example:

cat << EOF > csm-vxflexos.yaml
apiVersion: storage.dell.com/v1
kind: ContainerStorageModule
metadata:
  name: vxflexos
  namespace: vxflexos
spec:
  driver:
    csiDriverType: "powerflex"
    configVersion: Default text if no valid parameter is passed.
  modules:
  - name: resiliency
    enabled: true
EOF

Detailed Configuration: Use the sample file for detailed settings.

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules Operator installs the Resiliency module for supported Dell CSI Drivers, deploying the Resiliency sidecar.

Prerequisite

The Resiliency module only acts on pods with a specific label. At startup, it logs the label key and value. Apply this label to the StatefulSet you want monitored

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Enable Resiliency Module

Use this command to create the ContainerStorageModule Custom Resource with Resiliency:

oc create -f csm-isilon.yaml

Example:

cat << EOF > csm-isilon.yaml
apiVersion: storage.dell.com/v1
kind: ContainerStorageModule
metadata:
  name: isilon
  namespace: isilon
spec:
  driver:
    csiDriverType: "powerscale"
    configVersion: Default text if no valid parameter is passed.
  modules:
  - name: resiliency
    enabled: true
EOF

Detailed Configuration: Use the sample file for detailed settings.

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Enable Resiliency Module

Use this command to create the ContainerStorageModule Custom Resource with Resiliency:

oc create -f csm-powerstore.yaml

Example:

cat << EOF > csm-powerstore.yaml
apiVersion: storage.dell.com/v1
kind: ContainerStorageModule
metadata:
  name: powerstore
  namespace: powerstore
spec:
  driver:
    csiDriverType: "powerstore"
    configVersion: Default text if no valid parameter is passed.
  modules:
  - name: resiliency
    enabled: true
EOF

Detailed Configuration: Use the sample file for detailed settings.

Storage Class

Mon, 01 Jan 0001 00:00:00 +0000

Replication Enabled Storage Classes

In order to create replicated volumes & volume groups, you need to add some extra parameters to your storage class definition. These extra parameters generally carry the prefix replication.storage.dell.com to differentiate them from other provisioning parameters.

Storage Class

Mon, 01 Jan 0001 00:00:00 +0000

Replication Enabled Storage Classes

Storage Class

Mon, 01 Jan 0001 00:00:00 +0000

Replication Enabled Storage Classes

Storage Class

Mon, 01 Jan 0001 00:00:00 +0000

Replication Enabled Storage Classes

Troubleshooting

Mon, 01 Jan 0001 00:00:00 +0000

Helm Deployment

The CSI Driver for Dell PowerFlex is in an Error or CrashLoopBackoff state due to “request denied for path” errors

The vxflexos-controller pods will have logs similar to:

Mon, 01 Jan 0001 00:00:00 +0000

Enabled: It creates a corresponding PVC on target cluster same as source cluster. Applicable only on multi cluster scenarios.

Disabled: It updates claimRef on remote PV, so it cannot be claimed unless claimRef is removed or updated with expected claim details.

claimRef:                                       
  apiVersion: v1
  kind: PersistentVolumeClaim
  name: reserved
  namespace: reserved

Prerequisites

This feature is disabled by default.

Allow PVC creation on target cluster & claimRef update on remote PV

Mon, 01 Jan 0001 00:00:00 +0000

Enabled: It creates a corresponding PVC on target cluster same as source cluster. Applicable only on multi cluster scenarios.

Disabled: It updates claimRef on remote PV, so it cannot be claimed unless claimRef is removed or updated with expected claim details.

claimRef:                                       
  apiVersion: v1
  kind: PersistentVolumeClaim
  name: reserved
  namespace: reserved

Prerequisites

This feature is disabled by default.

Allow PVC creation on target cluster & claimRef update on remote PV

Mon, 01 Jan 0001 00:00:00 +0000

Enabled: It creates a corresponding PVC on target cluster same as source cluster. Applicable only on multi cluster scenarios.

Disabled: It updates claimRef on remote PV, so it cannot be claimed unless claimRef is removed or updated with expected claim details.

claimRef:                                       
  apiVersion: v1
  kind: PersistentVolumeClaim
  name: reserved
  namespace: reserved

Prerequisites

This feature is disabled by default.

Community Qualified Configurations

Mon, 01 Jan 0001 00:00:00 +0000

cert-csi results	OS	CO	Storage Platform	Protocol	CSM
1079	Debian 10	K3s v1.24.7+k3s1	Unity VSA 5.3.1.0.5.008	iSCSI	CSI v2.8.0
1177	Ubuntu OS 22.04	Amazon EKS (K8s 1.29)	PowerFlex	SCINI	CSI v2.9.2
1361	RHCOS 4.12	OpenShift 4.12	PowerStore	iSCSI	CSI v2.8.0
1362	RHCOS 4.12	OpenShift 4.12	PowerScale	NFS	CSI v2.8.0
1390	RHCOS 4.15	OpenShift 4.15	PowerStore	NVMeTCP	CSI v2.10.1
1441 1462	Ubuntu 20.04.x	MKE 3.6.13	PowerScale, PowerFlex	NFS	CSI v2.11.0
1442	RHCOS 4.14.92	OKE 4.14.31	PowerScale	NFS	CSI v2.11.0
1456	RHCOS 4.14.92	OKE 4.14.31	PowerFlex	NFS	CSI v2.11.0
1479	Ubuntu 18.04.x	OpenShift 4.17	PowerFlex	iSCSI	CSI v2.11.0
1500 1501	RHCOS 4.14	OpenShift 4.14.x	PowerStore	iSCSI	CSI 2.10.1
1513	RHCOS 4.14	OpenShift 4.14	PowerScale	NFS	CSI v2.6.1
1516	Ubuntu 20.04.x	MKE - 3.6.13	PowerFlex	iSCSI	CSI v2.11.0
1590	RHCOS 4.14	OpenShift 4.14	Unity 680F 5.4.0.0.5.094	NFS	CSI v2.12.0
1622	Ubuntu 20.04.6 LTS	MKE - 3.6.13	PowerScale v9.5.0.8	NFS	CSI v2.12.0
1623	Red Hat Enterprise Linux CoreOS	OKE 4.14.31	PowerScale v9.5.0.8	NFS	CSI v2.12.0
1624	Red Hat Enterprise Linux CoreOS	OKE 4.14.31	PowerFlex 3.6.4000	NFS	CSI v2.12.0
1625	Ubuntu 20.04.6 LTS	MKE - 3.6.13	PowerFlex 3.6.4000	NFS	CSI v2.12.0
1764	RHCOS 4.14	OKE 1.27	PowerScale 9.4.0.16	NFS	CSI v2.11.0
1767	RHEL 8.10 (Ootpa)	MKE 3.8.2	PowerScale 9.7	NFS	CSI v2.13.0
k8s-1323	RHEL 9.2	K8s 1.32.3	PowerFlex	ScaleIO	CSI v2.14.2
k8s-12613	RHEL 8.6	K8s 1.26.13	PowerFlex	ScaleIO	CSI v2.14.2
k8s-12210	RHEL 8.6	K8s 1.22.10	PowerFlex	ScaleIO	CSI v2.14.2

Community Qualified Configurations

Mon, 01 Jan 0001 00:00:00 +0000

cert-csi results	OS	CO	Storage Platform	Protocol	CSM
1079	Debian 10	K3s v1.24.7+k3s1	Unity VSA 5.3.1.0.5.008	iSCSI	CSI v2.8.0
1177	Ubuntu OS 22.04	Amazon EKS (K8s 1.29)	PowerFlex	SCINI	CSI v2.9.2
1361	RHCOS 4.12	OpenShift 4.12	PowerStore	iSCSI	CSI v2.8.0
1362	RHCOS 4.12	OpenShift 4.12	PowerScale	NFS	CSI v2.8.0
1390	RHCOS 4.15	OpenShift 4.15	PowerStore	NVMeTCP	CSI v2.10.1
1441 [1462]	Ubuntu 20.04.x	MKE 3.6.13	PowerScale, PowerFlex	NFS	CSI v2.11.0
1442	RHCOS 4.14.92	OKE 4.14.31	PowerScale	NFS	CSI v2.11.0
1456	RHCOS 4.14.92	OKE 4.14.31	PowerFlex	NFS	CSI v2.11.0
1479	Ubuntu 18.04.x	OpenShift 4.17	PowerFlex	iSCSI	CSI v2.11.0
1500 [1501]	RHCOS 4.14	OpenShift 4.14.x	PowerStore	iSCSI	CSI 2.10.1
1513	RHCOS 4.14	OpenShift 4.14	PowerScale	NFS	CSI v2.6.1
1516	Ubuntu 20.04.x	MKE - 3.6.13	PowerFlex	iSCSI	CSI v2.11.0
1590	RHCOS 4.14	OpenShift 4.14	Unity 680F 5.4.0.0.5.094	NFS	CSI v2.12.0
1622	Ubuntu 20.04.6 LTS	MKE - 3.6.13	PowerScale v9.5.0.8	NFS	CSI v2.12.0
1623	Red Hat Enterprise Linux CoreOS	OKE 4.14.31	PowerScale v9.5.0.8	NFS	CSI v2.12.0
1624	Red Hat Enterprise Linux CoreOS	OKE 4.14.31	PowerFlex 3.6.4000	NFS	CSI v2.12.0
1625	Ubuntu 20.04.6 LTS	MKE - 3.6.13	PowerFlex 3.6.4000	NFS	CSI v2.12.0
1764	RHCOS 4.14	OKE 1.27	PowerScale 9.4.0.16	NFS	CSI v2.11.0
1767	RHEL 8.10 (Ootpa)	MKE 3.8.2	PowerScale 9.7	NFS	CSI v2.13.0

Community Qualified Configurations

Mon, 01 Jan 0001 00:00:00 +0000

cert-csi results	OS	CO	Storage Platform	Protocol	CSM
1079	Debian 10	K3s v1.24.7+k3s1	Unity VSA 5.3.1.0.5.008	iSCSI	CSI v2.8.0
1177	Ubuntu OS 22.04	Amazon EKS (K8s 1.29)	PowerFlex	SCINI	CSI v2.9.2
1361	RHCOS 4.12	OpenShift 4.12	PowerStore	iSCSI	CSI v2.8.0
1362	RHCOS 4.12	OpenShift 4.12	PowerScale	NFS	CSI v2.8.0
1390	RHCOS 4.15	OpenShift 4.15	PowerStore	NVMeTCP	CSI v2.10.1
1441 1462	Ubuntu 20.04.x	MKE 3.6.13	PowerScale, PowerFlex	NFS	CSI v2.11.0
1442	RHCOS 4.14.92	OKE 4.14.31	PowerScale	NFS	CSI v2.11.0
1456	RHCOS 4.14.92	OKE 4.14.31	PowerFlex	NFS	CSI v2.11.0
1479	Ubuntu 18.04.x	OpenShift 4.17	PowerFlex	iSCSI	CSI v2.11.0
1500 1501	RHCOS 4.14	OpenShift 4.14.x	PowerStore	iSCSI	CSI 2.10.1
1513	RHCOS 4.14	OpenShift 4.14	PowerScale	NFS	CSI v2.6.1
1516	Ubuntu 20.04.x	MKE - 3.6.13	PowerFlex	iSCSI	CSI v2.11.0
1590	RHCOS 4.14	OpenShift 4.14	Unity 680F 5.4.0.0.5.094	NFS	CSI v2.12.0
1622	Ubuntu 20.04.6 LTS	MKE - 3.6.13	PowerScale v9.5.0.8	NFS	CSI v2.12.0
1623	Red Hat Enterprise Linux CoreOS	OKE 4.14.31	PowerScale v9.5.0.8	NFS	CSI v2.12.0
1624	Red Hat Enterprise Linux CoreOS	OKE 4.14.31	PowerFlex 3.6.4000	NFS	CSI v2.12.0
1625	Ubuntu 20.04.6 LTS	MKE - 3.6.13	PowerFlex 3.6.4000	NFS	CSI v2.12.0
1764	RHCOS 4.14	OKE 1.27	PowerScale 9.4.0.16	NFS	CSI v2.11.0
1767	RHEL 8.10 (Ootpa)	MKE 3.8.2	PowerScale 9.7	NFS	CSI v2.13.0

Container Storage Modules Operator Certification Policy

Mon, 01 Jan 0001 00:00:00 +0000

To ensure secure and certified solutions, Dell initiates the Red Hat OpenShift Operator Certification process immediately following the public release of Dell Container Storage Modules. This includes validation of the Operator bundle, container image compliance, and compatibility with OpenShift standards. Once certified, the Operator is published to the OpenShift Catalog for trusted deployment.

Container Storage Modules Operator Certification Policy

Mon, 01 Jan 0001 00:00:00 +0000

Metro Replication with OpenShift Virtualization

Mon, 01 Jan 0001 00:00:00 +0000

Starting in CSM 1.14, the Replication module supports the metro volume replication for Persistent Volumes (PVs) created via virtualized workloads (VMs).

OpenShift Virtualization:

OpenShift Virtualization allows virtual machines (VMs) to run alongside container workloads within Kubernetes clusters, addressing the coexistence of legacy VM workloads and modern containers.

OpenShift Virtualization support with Metro Replication

Install the OpenShift Virtualization operator from the RedHat UI on OpenShift Cluster.

Metro Replication with OpenShift Virtualization

Mon, 01 Jan 0001 00:00:00 +0000

Starting in CSM 1.14, the Replication module supports the metro volume replication for Persistent Volumes (PVs) created via virtualized workloads (VMs).

OpenShift Virtualization:

OpenShift Virtualization allows virtual machines (VMs) to run alongside container workloads within Kubernetes clusters, addressing the coexistence of legacy VM workloads and modern containers.

OpenShift Virtualization support with Metro Replication

Install the OpenShift Virtualization operator from the RedHat UI on OpenShift Cluster.

Metro Replication with OpenShift Virtualization

Mon, 01 Jan 0001 00:00:00 +0000

Starting in CSM 1.14, the Replication module supports the metro volume replication for Persistent Volumes (PVs) created via virtualized workloads (VMs).

OpenShift Virtualization:

OpenShift Virtualization allows virtual machines (VMs) to run alongside container workloads within Kubernetes clusters, addressing the coexistence of legacy VM workloads and modern containers.

OpenShift Virtualization support with Metro Replication

Install the OpenShift Virtualization operator from the RedHat UI on OpenShift Cluster.

Monitoring

Mon, 01 Jan 0001 00:00:00 +0000

The dell-csm-replicator supports monitoring of DellCSIReplicationGroup Custom Resources (CRs).

Each RG is polled at a pre-defined interval and for each RG, a gRPC call is made to the driver which returns the status of the protection group on the array.

If an RG doesn’t have any PVs associated with it, the driver will not receive any monitoring request for that RG.

This status can be obtained from the RG using a standard kubectl get call on the resource name:

Monitoring

Mon, 01 Jan 0001 00:00:00 +0000

The dell-csm-replicator supports monitoring of DellCSIReplicationGroup Custom Resources (CRs).

Each RG is polled at a pre-defined interval and for each RG, a gRPC call is made to the driver which returns the status of the protection group on the array.

If an RG doesn’t have any PVs associated with it, the driver will not receive any monitoring request for that RG.

This status can be obtained from the RG using a standard kubectl get call on the resource name:

Monitoring

Mon, 01 Jan 0001 00:00:00 +0000

The dell-csm-replicator supports monitoring of DellCSIReplicationGroup Custom Resources (CRs).

Each RG is polled at a pre-defined interval and for each RG, a gRPC call is made to the driver which returns the status of the protection group on the array.

If an RG doesn’t have any PVs associated with it, the driver will not receive any monitoring request for that RG.

This status can be obtained from the RG using a standard kubectl get call on the resource name:

Monitoring

Mon, 01 Jan 0001 00:00:00 +0000

The dell-csm-replicator supports monitoring of DellCSIReplicationGroup Custom Resources (CRs).

Each RG is polled at a pre-defined interval and for each RG, a gRPC call is made to the driver which returns the status of the protection group on the array.

If an RG doesn’t have any PVs associated with it, the driver will not receive any monitoring request for that RG.

This status can be obtained from the RG using a standard kubectl get call on the resource name:

PowerFlex

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Enabling Replication In CSI PowerFlex

Container Storage Modules (CSM) Replication sidecar is a helper container that is installed alongside a CSI driver to facilitate replication functionality. Such CSI drivers must implement dell-csi-extensions calls.

#1956 - [BUG]: Make probe-retry in Powerflex driver configurable - Applies to a limited use case on the PowerFlex platform when deployed via Helm. Full support for both Operator and Helm deployments will be available in the 1.14.1 release.

Release Notes - CSI PowerFlex v2.13.1

Fixed Issues

#1782 - [BUG]: Pods Stuck in Terminating State After PowerFlex CSI Node Pod Restart When Deployments Share Same Node

Release Notes - CSI PowerFlex v2.13.0

New Features/Changes

Fixed Issues

Known Issues

Issue	Workaround
Delete namespace that has PVCs and pods created with the driver. The External health monitor sidecar crashes as a result of this operation.	Deleting the namespace deletes the PVCs first and then removes the pods in the namespace. This brings a condition where pods exist without their PVCs and causes the external-health-monitor sidecar to crash. This is a known issue and has been reported at https://github.com/kubernetes-csi/external-health-monitor/issues/100
When a node goes down, the block volumes attached to the node cannot be attached to another node	This is a known issue and has been reported at https://github.com/kubernetes-csi/external-attacher/issues/215. Workaround: 1. Force delete the pod running on the node that went down 2. Delete the volumeattachment to the node that went down. Now the volume can be attached to the new node.
sdc:3.6.0.6 is causing issues while installing the csi-powerflex driver on ubuntu,RHEL8.3	Workaround: Change the powerflexSdc to sdc:3.6 in values.yaml https://github.com/dell/csi-powerflex/blob/72b27acee7553006cc09df97f85405f58478d2e4/helm/csi-vxflexos/values.yaml#L13
sdc:3.6.1 is causing issues while installing the csi-powerflex driver on ubuntu.	Workaround: Change the powerflexSdc to sdc:3.6 in values.yaml https://github.com/dell/csi-powerflex/blob/72b27acee7553006cc09df97f85405f58478d2e4/helm/csi-vxflexos/values.yaml#L13
A CSI ephemeral pod may not get created in OpenShift 4.13 and fail with the error `"error when creating pod: the pod uses an inline volume provided by CSIDriver csi-vxflexos.dellemc.com, and the namespace has a pod security enforcement level that is lower than privileged."`	This issue occurs because OpenShift 4.13 introduced the CSI Volume Admission plugin to restrict the use of a CSI driver capable of provisioning CSI ephemeral volumes during pod admission. Therefore, an additional label `security.openshift.io/csi-ephemeral-volume-profile` in csidriver.yaml file with the required security profile value should be provided. Follow OpenShift 4.13 documentation for CSI Ephemeral Volumes for more information.
If the volume limit is exhausted and there are pending pods and PVCs due to `exceed max volume count`, the pending PVCs will be bound to PVs and the pending pods will be scheduled to nodes when the driver pods are restarted.	It is advised not to have any pending pods or PVCs once the volume limit per node is exhausted on a CSI Driver. There is an open issue reported with kubernetes at https://github.com/kubernetes/kubernetes/issues/95911 with the same behavior.
Resource quotas may not work properly with the CSI PowerFlex driver. PowerFlex is only able to assign storage in 8Gi chunks, so if a create volume call is made with a size not divisible by 8Gi, CSI-PowerFlex will round up to the next 8Gi boundary when it provisions storage – however, the resource quota will not record this size but rather the original size in the create request. This means that, for example, if a 10Gi resource quota is set, and a user provisions 10 1Gi PVCs, 80Gi of storage will actually be allocated, which is well over the amount specified in the resource quota.	For now, users should only provision volumes in 8Gi-divisible chunks if they want to use resource quotas.
After restarting a PowerFlex CSI node pod, any deployment whose pods are scheduled on the same node as the restarted CSI node pod will experience pods stuck indefinitely in the Terminating state. This occurs when the deployment is restarted via a command such as ‘oc rollout restart’.	Upgrade CSM to v1.13.1 or later.
CSM Operator v1.13.1 may cause pod crashes when PowerFlex response times exceed one second due to premature communication timeout.	Upgrade CSM to v1.14.1 or later through CSM Operator.

Note:

Support for Kubernetes alpha features like Volume Health Monitoring will not be available in Openshift environment as Openshift doesn’t support enabling of alpha features for Production Grade clusters.
For fixing #1210 - [BUG]: Helm deployment of PowerFlex driver is failing, a new helm-chart has been released. In order to install this helm chart, we need to pass the flag --helm-charts-version during helm installation and flag -v during offline bundle installation with value csi-vxflexos-2.11.0.

PVC Remap

Mon, 01 Jan 0001 00:00:00 +0000

This feature automatically attaches the Persistent Volume Claim (PVC) to the active volume/Persistent Volume (PV) without requiring manual intervention for failover scenarios on a Kubernetes stretched cluster using CSM replication.

Prerequisites

This feature is enabled by default.

PVC Remap

Mon, 01 Jan 0001 00:00:00 +0000

Prerequisites

This feature is enabled by default.

PVC Remap

Mon, 01 Jan 0001 00:00:00 +0000

Prerequisites

This feature is enabled by default.

Replication Actions

Mon, 01 Jan 0001 00:00:00 +0000

You can exercise native replication control operations from Dell storage arrays by performing “Actions” on the replicated group of volumes using the DellCSIReplicationGroup (RG) object.

You can patch the DellCSIReplicationGroup Custom Resource (CR) and set the action field in the spec to one of the allowed values (refer to tables in this document).

When you set the action field in the Custom Resource object, the following happens:

State of the RG CR is set to action_in_progress. For e.g. if you set the action field to SYNC, then the state will change to SYNC_IN_PROGRESS, action field will reset to empty
dell-csi-replicator sidecar issues the command to the CSI driver to perform the appropriate action
Once the CSI driver has completed the operation, State of the RG CR goes back to Ready

While the action is in progress, you shouldn’t update the action field. Any attempt to change the action field will be rejected and it will be reset to empty. There are certain pre-requisites that have to be fulfilled before any action can be done on the RG CR. For example, you can’t perform a Reprotect without doing a Failover first. There are some “Workflows” defined in Disaster Recovery which provide a sequence of operations for some common use-cases. An important exception to these rules is the action UNPLANNED_FAILOVER, which can be run at any time.

Replication Actions

Mon, 01 Jan 0001 00:00:00 +0000

You can exercise native replication control operations from Dell storage arrays by performing “Actions” on the replicated group of volumes using the DellCSIReplicationGroup (RG) object.

You can patch the DellCSIReplicationGroup Custom Resource (CR) and set the action field in the spec to one of the allowed values (refer to tables in this document).

When you set the action field in the Custom Resource object, the following happens:

State of the RG CR is set to action_in_progress. For e.g. if you set the action field to SYNC, then the state will change to SYNC_IN_PROGRESS, action field will reset to empty
dell-csi-replicator sidecar issues the command to the CSI driver to perform the appropriate action
Once the CSI driver has completed the operation, State of the RG CR goes back to Ready

Replication Actions

Mon, 01 Jan 0001 00:00:00 +0000

You can exercise native replication control operations from Dell storage arrays by performing “Actions” on the replicated group of volumes using the DellCSIReplicationGroup (RG) object.

You can patch the DellCSIReplicationGroup Custom Resource (CR) and set the action field in the spec to one of the allowed values (refer to tables in this document).

When you set the action field in the Custom Resource object, the following happens:

State of the RG CR is set to action_in_progress. For e.g. if you set the action field to SYNC, then the state will change to SYNC_IN_PROGRESS, action field will reset to empty
dell-csi-replicator sidecar issues the command to the CSI driver to perform the appropriate action
Once the CSI driver has completed the operation, State of the RG CR goes back to Ready

Replication Actions

Mon, 01 Jan 0001 00:00:00 +0000

You can exercise native replication control operations from Dell storage arrays by performing “Actions” on the replicated group of volumes using the DellCSIReplicationGroup (RG) object.

You can patch the DellCSIReplicationGroup Custom Resource (CR) and set the action field in the spec to one of the allowed values (refer to tables in this document).

When you set the action field in the Custom Resource object, the following happens:

State of the RG CR is set to action_in_progress. For e.g. if you set the action field to SYNC, then the state will change to SYNC_IN_PROGRESS, action field will reset to empty
dell-csi-replicator sidecar issues the command to the CSI driver to perform the appropriate action
Once the CSI driver has completed the operation, State of the RG CR goes back to Ready

Troubleshooting

Mon, 01 Jan 0001 00:00:00 +0000

Volume Expansion

Mon, 01 Jan 0001 00:00:00 +0000

Starting in v2.4.0, the CSI PowerMax driver supports the expansion of Replicated Persistent Volumes (PVs). This expansion is done online, which is when the PVC is attached to any node.

Prerequisites

To use this feature, enable resizer in values.yaml:

resizer:
  enabled: true

To use this feature, the storage class that is used to create the PVC must have the attribute allowVolumeExpansion set to true.

Basic Usage

To resize a PVC, edit the existing PVC spec and set spec.resources.requests.storage to the intended size. For example, if you have a PVC pmax-pvc-demo of size 5 Gi, then you can resize it to 10 Gi by updating the PVC:

Volume Expansion

Mon, 01 Jan 0001 00:00:00 +0000

Starting in v2.4.0, the CSI PowerMax driver supports the expansion of Replicated Persistent Volumes (PVs). This expansion is done online, which is when the PVC is attached to any node.

Prerequisites

To use this feature, enable resizer in values.yaml:

resizer:
  enabled: true

To use this feature, the storage class that is used to create the PVC must have the attribute allowVolumeExpansion set to true.

Basic Usage

Volume Expansion

Mon, 01 Jan 0001 00:00:00 +0000

Starting in v2.4.0, the CSI PowerMax driver supports the expansion of Replicated Persistent Volumes (PVs). This expansion is done online, which is when the PVC is attached to any node.

Prerequisites

To use this feature, enable resizer in values.yaml:

resizer:
  enabled: true

To use this feature, the storage class that is used to create the PVC must have the attribute allowVolumeExpansion set to true.

Basic Usage

Volume Expansion

Mon, 01 Jan 0001 00:00:00 +0000

Starting in v2.4.0, the CSI PowerMax driver supports the expansion of Replicated Persistent Volumes (PVs). This expansion is done online, which is when the PVC is attached to any node.

Prerequisites

To use this feature, enable resizer in values.yaml:

resizer:
  enabled: true

To use this feature, the storage class that is used to create the PVC must have the attribute allowVolumeExpansion set to true.

To begin managing replication with repctl you need to add your Kubernetes clusters, you can do that using cluster add command:

Troubleshooting

Mon, 01 Jan 0001 00:00:00 +0000

Symptoms	Prevention, Resolution or Workaround
Persistent volumes don’t get created on the target cluster.	Run `kubectl describe` on one of the pods of replication controller and see if event says `Config update won't be applied because of invalid configmap/secrets. Please fix the invalid configuration`. If it does, then ensure you correctly populated replication ConfigMap. You can check the current status by running `kubectl describe cm -n dell-replication-controller dell-replication-controller-config`. If ConfigMap is empty, please edit it yourself or use `repctl cluster inject` command.
Persistent volumes don’t get created on the target cluster. You don’t see any events on the replication-controller pod.	Check logs of replication controller by running `kubectl logs -n dell-replication-controller dell-replication-controller-manager-<generated-symbols>`. If you see `clusterId - <clusterID> not found` errors then be sure to check if you specified the same clusterIDs in both your ConfigMap and replication enabled StorageClass.
You apply replication action by manually editing ReplicationGroup resource field `spec.action` and don’t see any change of ReplicationGroup state after a while.	Check events of the replication-controller pod, if it says `Cannot proceed with action <your-action>. [unsupported action]` then check spelling of your action and consult the Replication Actions page. Alternatively, you can use `repctl` instead of manually editing ReplicationGroup resources.
You execute failover action using `repctl failover` command and see `failover: error executing failover to source site`.	This means you tried to failover to a cluster that is already marked source. If you still want to execute failover for RG, just choose another cluster.
You’ve created PersistentVolumeClaim using replication enabled StorageClass but don’t see any RGs created in the source cluster.	Check annotations of created PersistentVolumeClaim. If it doesn’t have `annotations` that start with `replication.storage.dell.com` then please wait for a couple of minutes for them to be added and RG to be created.
When installing common replication controller using helm you see an error that states `invalid ownership metadata` and `missing key "app.kubernetes.io/managed-by": must be set to "Helm"`	This means that you haven’t fully deleted the previous release, you can fix it by either deleting entire manifest by using `kubectl delete -f deploy/controller.yaml` or manually deleting conflicting resources (ClusterRoles, ClusterRoleBinding, etc.)
PV and/or PVCs are not being created at the source/target cluster. If you check the controller’s logs you can see `no such host` errors	Make sure cluster-1’s API is pingable from cluster-2 and vice versa. If one of your clusters is OpenShift located in a private network and needs records in /etc/hosts, `exec` into controller pod and modify `/etc/hosts` manually.
After upgrading to Replication v1.4.0, if `kubectl get rg` returns an error `Unable to list "replication.storage.dell.com/v1alpha1, Resource=dellcsireplicationgroups"`	This means `kubectl` still doesn’t recognize the new version of CRD `dellcsireplicationgroups.replication.storage.dell.com` after upgrade. Running the command `kubectl get DellCSIReplicationGroup.v1.replication.storage.dell.com/<rg-id> -o yaml` will resolve the issue.
To add or delete PV s in the existing SYNC Replication Group in PowerStore, you may encounter the error `The operation is restricted as sync replication session for resource <Replication Group Name> is not paused`	To resolve this, you need to pause the replication group, add the PV, and then resume the replication group (RG). The commands for the pause and resume operations are: `repctl --rg <rg-id> exec -a suspend` `repctl --rg <rg-id> exec -a resume`
To delete the last volume from the existing SYNC Replication Group in Powerstore, you may encounter the error ‘failed to remove volume from volume group: The operation cannot be completed on metro or replicated volume group because volume group will become empty after last members are removed’	To resolve this, unassign the protection policy from the corresponding volume group on the PowerStore Manager UI. After that, you can successfully delete the last volume in that SYNC Replication Group.
When running CSI-PowerMax with Replication in a multi-cluster configuration, the driver on the target cluster fails and the following error is seen in logs: `error="CSI reverseproxy service host or port not found, CSI reverseproxy not installed properly"`	The reverseproxy service needs to be created manually on the target cluster. Follow the instructions here to create it.
When getting the following error for CSI-Powerscale with Replication with encryption enabled: `SyncIQ policy failed to establish an encrypted connection`, the Replication groups and PVC’s won’t be created at target cluster.	The `encryption required` flag in the SyncIQ settings was set to “yes” by default in OneFS 9.0+. To rectify this error, please follow the following article: https://www.dell.com/support/kbdoc/en-us/000215174/isilon-synciq-9-0-all-policies-fail-when-source-or-target-cluster-is-on-onefs-9-0-with-no-node-on-source-cluster-was-able-to-connect-to-target-cluster

Troubleshooting

Mon, 01 Jan 0001 00:00:00 +0000

Symptoms	Prevention, Resolution or Workaround
Persistent volumes don’t get created on the target cluster.	Run `kubectl describe` on one of the pods of replication controller and see if event says `Config update won't be applied because of invalid configmap/secrets. Please fix the invalid configuration`. If it does, then ensure you correctly populated replication ConfigMap. You can check the current status by running `kubectl describe cm -n dell-replication-controller dell-replication-controller-config`. If ConfigMap is empty, please edit it yourself or use `repctl cluster inject` command.
Persistent volumes don’t get created on the target cluster. You don’t see any events on the replication-controller pod.	Check logs of replication controller by running `kubectl logs -n dell-replication-controller dell-replication-controller-manager-<generated-symbols>`. If you see `clusterId - <clusterID> not found` errors then be sure to check if you specified the same clusterIDs in both your ConfigMap and replication enabled StorageClass.
You apply replication action by manually editing ReplicationGroup resource field `spec.action` and don’t see any change of ReplicationGroup state after a while.	Check events of the replication-controller pod, if it says `Cannot proceed with action <your-action>. [unsupported action]` then check spelling of your action and consult the Replication Actions page. Alternatively, you can use `repctl` instead of manually editing ReplicationGroup resources.
You execute failover action using `repctl failover` command and see `failover: error executing failover to source site`.	This means you tried to failover to a cluster that is already marked source. If you still want to execute failover for RG, just choose another cluster.
You’ve created PersistentVolumeClaim using replication enabled StorageClass but don’t see any RGs created in the source cluster.	Check annotations of created PersistentVolumeClaim. If it doesn’t have `annotations` that start with `replication.storage.dell.com` then please wait for a couple of minutes for them to be added and RG to be created.
When installing common replication controller using helm you see an error that states `invalid ownership metadata` and `missing key "app.kubernetes.io/managed-by": must be set to "Helm"`	This means that you haven’t fully deleted the previous release, you can fix it by either deleting entire manifest by using `kubectl delete -f deploy/controller.yaml` or manually deleting conflicting resources (ClusterRoles, ClusterRoleBinding, etc.)
PV and/or PVCs are not being created at the source/target cluster. If you check the controller’s logs you can see `no such host` errors	Make sure cluster-1’s API is pingable from cluster-2 and vice versa. If one of your clusters is OpenShift located in a private network and needs records in /etc/hosts, `exec` into controller pod and modify `/etc/hosts` manually.
After upgrading to Replication v1.4.0, if `kubectl get rg` returns an error `Unable to list "replication.storage.dell.com/v1alpha1, Resource=dellcsireplicationgroups"`	This means `kubectl` still doesn’t recognize the new version of CRD `dellcsireplicationgroups.replication.storage.dell.com` after upgrade. Running the command `kubectl get DellCSIReplicationGroup.v1.replication.storage.dell.com/<rg-id> -o yaml` will resolve the issue.
To add or delete PV s in the existing SYNC Replication Group in PowerStore, you may encounter the error `The operation is restricted as sync replication session for resource <Replication Group Name> is not paused`	To resolve this, you need to pause the replication group, add the PV, and then resume the replication group (RG). The commands for the pause and resume operations are: `repctl --rg <rg-id> exec -a suspend` `repctl --rg <rg-id> exec -a resume`
To delete the last volume from the existing SYNC Replication Group in Powerstore, you may encounter the error ‘failed to remove volume from volume group: The operation cannot be completed on metro or replicated volume group because volume group will become empty after last members are removed’	To resolve this, unassign the protection policy from the corresponding volume group on the PowerStore Manager UI. After that, you can successfully delete the last volume in that SYNC Replication Group.
When running CSI-PowerMax with Replication in a multi-cluster configuration, the driver on the target cluster fails and the following error is seen in logs: `error="CSI reverseproxy service host or port not found, CSI reverseproxy not installed properly"`	The reverseproxy service needs to be created manually on the target cluster. Follow the instructions here to create it.
When getting the following error for CSI-Powerscale with Replication with encryption enabled: `SyncIQ policy failed to establish an encrypted connection`, the Replication groups and PVC’s won’t be created at target cluster.	The `encryption required` flag in the SyncIQ settings was set to “yes” by default in OneFS 9.0+. To rectify this error, please follow the following article: https://www.dell.com/support/kbdoc/en-us/000215174/isilon-synciq-9-0-all-policies-fail-when-source-or-target-cluster-is-on-onefs-9-0-with-no-node-on-source-cluster-was-able-to-connect-to-target-cluster

Troubleshooting

Mon, 01 Jan 0001 00:00:00 +0000

Symptoms	Prevention, Resolution or Workaround
Persistent volumes don’t get created on the target cluster.	Run `kubectl describe` on one of the pods of replication controller and see if event says `Config update won't be applied because of invalid configmap/secrets. Please fix the invalid configuration`. If it does, then ensure you correctly populated replication ConfigMap. You can check the current status by running `kubectl describe cm -n dell-replication-controller dell-replication-controller-config`. If ConfigMap is empty, please edit it yourself or use `repctl cluster inject` command.
Persistent volumes don’t get created on the target cluster. You don’t see any events on the replication-controller pod.	Check logs of replication controller by running `kubectl logs -n dell-replication-controller dell-replication-controller-manager-<generated-symbols>`. If you see `clusterId - <clusterID> not found` errors then be sure to check if you specified the same clusterIDs in both your ConfigMap and replication enabled StorageClass.
You apply replication action by manually editing ReplicationGroup resource field `spec.action` and don’t see any change of ReplicationGroup state after a while.	Check events of the replication-controller pod, if it says `Cannot proceed with action <your-action>. [unsupported action]` then check spelling of your action and consult the Replication Actions page. Alternatively, you can use `repctl` instead of manually editing ReplicationGroup resources.
You execute failover action using `repctl failover` command and see `failover: error executing failover to source site`.	This means you tried to failover to a cluster that is already marked source. If you still want to execute failover for RG, just choose another cluster.
You’ve created PersistentVolumeClaim using replication enabled StorageClass but don’t see any RGs created in the source cluster.	Check annotations of created PersistentVolumeClaim. If it doesn’t have `annotations` that start with `replication.storage.dell.com` then please wait for a couple of minutes for them to be added and RG to be created.
When installing common replication controller using helm you see an error that states `invalid ownership metadata` and `missing key "app.kubernetes.io/managed-by": must be set to "Helm"`	This means that you haven’t fully deleted the previous release, you can fix it by either deleting entire manifest by using `kubectl delete -f deploy/controller.yaml` or manually deleting conflicting resources (ClusterRoles, ClusterRoleBinding, etc.)
PV and/or PVCs are not being created at the source/target cluster. If you check the controller’s logs you can see `no such host` errors	Make sure cluster-1’s API is pingable from cluster-2 and vice versa. If one of your clusters is OpenShift located in a private network and needs records in /etc/hosts, `exec` into controller pod and modify `/etc/hosts` manually.
After upgrading to Replication v1.4.0, if `kubectl get rg` returns an error `Unable to list "replication.storage.dell.com/v1alpha1, Resource=dellcsireplicationgroups"`	This means `kubectl` still doesn’t recognize the new version of CRD `dellcsireplicationgroups.replication.storage.dell.com` after upgrade. Running the command `kubectl get DellCSIReplicationGroup.v1.replication.storage.dell.com/<rg-id> -o yaml` will resolve the issue.
To add or delete PV s in the existing SYNC Replication Group in PowerStore, you may encounter the error `The operation is restricted as sync replication session for resource <Replication Group Name> is not paused`	To resolve this, you need to pause the replication group, add the PV, and then resume the replication group (RG). The commands for the pause and resume operations are: `repctl --rg <rg-id> exec -a suspend` `repctl --rg <rg-id> exec -a resume`
To delete the last volume from the existing SYNC Replication Group in Powerstore, you may encounter the error ‘failed to remove volume from volume group: The operation cannot be completed on metro or replicated volume group because volume group will become empty after last members are removed’	To resolve this, unassign the protection policy from the corresponding volume group on the PowerStore Manager UI. After that, you can successfully delete the last volume in that SYNC Replication Group.
When running CSI-PowerMax with Replication in a multi-cluster configuration, the driver on the target cluster fails and the following error is seen in logs: `error="CSI reverseproxy service host or port not found, CSI reverseproxy not installed properly"`	The reverseproxy service needs to be created manually on the target cluster. Follow the instructions here to create it.
When getting the following error for CSI-Powerscale with Replication with encryption enabled: `SyncIQ policy failed to establish an encrypted connection`, the Replication groups and PVC’s won’t be created at target cluster.	The `encryption required` flag in the SyncIQ settings was set to “yes” by default in OneFS 9.0+. To rectify this error, please follow the following article: https://www.dell.com/support/kbdoc/en-us/000215174/isilon-synciq-9-0-all-policies-fail-when-source-or-target-cluster-is-on-onefs-9-0-with-no-node-on-source-cluster-was-able-to-connect-to-target-cluster

Troubleshooting

Mon, 01 Jan 0001 00:00:00 +0000

Symptoms	Prevention, Resolution or Workaround
Persistent volumes don’t get created on the target cluster.	Run `kubectl describe` on one of the pods of replication controller and see if event says `Config update won't be applied because of invalid configmap/secrets. Please fix the invalid configuration`. If it does, then ensure you correctly populated replication ConfigMap. You can check the current status by running `kubectl describe cm -n dell-replication-controller dell-replication-controller-config`. If ConfigMap is empty, please edit it yourself or use `repctl cluster inject` command.
Persistent volumes don’t get created on the target cluster. You don’t see any events on the replication-controller pod.	Check logs of replication controller by running `kubectl logs -n dell-replication-controller dell-replication-controller-manager-<generated-symbols>`. If you see `clusterId - <clusterID> not found` errors then be sure to check if you specified the same clusterIDs in both your ConfigMap and replication enabled StorageClass.
You apply replication action by manually editing ReplicationGroup resource field `spec.action` and don’t see any change of ReplicationGroup state after a while.	Check events of the replication-controller pod, if it says `Cannot proceed with action <your-action>. [unsupported action]` then check spelling of your action and consult the Replication Actions page. Alternatively, you can use `repctl` instead of manually editing ReplicationGroup resources.
You execute failover action using `repctl failover` command and see `failover: error executing failover to source site`.	This means you tried to failover to a cluster that is already marked source. If you still want to execute failover for RG, just choose another cluster.
You’ve created PersistentVolumeClaim using replication enabled StorageClass but don’t see any RGs created in the source cluster.	Check annotations of created PersistentVolumeClaim. If it doesn’t have `annotations` that start with `replication.storage.dell.com` then please wait for a couple of minutes for them to be added and RG to be created.
When installing common replication controller using helm you see an error that states `invalid ownership metadata` and `missing key "app.kubernetes.io/managed-by": must be set to "Helm"`	This means that you haven’t fully deleted the previous release, you can fix it by either deleting entire manifest by using `kubectl delete -f deploy/controller.yaml` or manually deleting conflicting resources (ClusterRoles, ClusterRoleBinding, etc.)
PV and/or PVCs are not being created at the source/target cluster. If you check the controller’s logs you can see `no such host` errors	Make sure cluster-1’s API is pingable from cluster-2 and vice versa. If one of your clusters is OpenShift located in a private network and needs records in /etc/hosts, `exec` into controller pod and modify `/etc/hosts` manually.
After upgrading to Replication v1.4.0, if `kubectl get rg` returns an error `Unable to list "replication.storage.dell.com/v1alpha1, Resource=dellcsireplicationgroups"`	This means `kubectl` still doesn’t recognize the new version of CRD `dellcsireplicationgroups.replication.storage.dell.com` after upgrade. Running the command `kubectl get DellCSIReplicationGroup.v1.replication.storage.dell.com/<rg-id> -o yaml` will resolve the issue.
To add or delete PV s in the existing SYNC Replication Group in PowerStore, you may encounter the error `The operation is restricted as sync replication session for resource <Replication Group Name> is not paused`	To resolve this, you need to pause the replication group, add the PV, and then resume the replication group (RG). The commands for the pause and resume operations are: `repctl --rg <rg-id> exec -a suspend` `repctl --rg <rg-id> exec -a resume`
To delete the last volume from the existing SYNC Replication Group in Powerstore, you may encounter the error ‘failed to remove volume from volume group: The operation cannot be completed on metro or replicated volume group because volume group will become empty after last members are removed’	To resolve this, unassign the protection policy from the corresponding volume group on the PowerStore Manager UI. After that, you can successfully delete the last volume in that SYNC Replication Group.
When running CSI-PowerMax with Replication in a multi-cluster configuration, the driver on the target cluster fails and the following error is seen in logs: `error="CSI reverseproxy service host or port not found, CSI reverseproxy not installed properly"`	The reverseproxy service needs to be created manually on the target cluster. Follow the instructions here to create it.
When getting the following error for CSI-Powerscale with Replication with encryption enabled: `SyncIQ policy failed to establish an encrypted connection`, the Replication groups and PVC’s won’t be created at target cluster.	The `encryption required` flag in the SyncIQ settings was set to “yes” by default in OneFS 9.0+. To rectify this error, please follow the following article: https://www.dell.com/support/kbdoc/en-us/000215174/isilon-synciq-9-0-all-policies-fail-when-source-or-target-cluster-is-on-onefs-9-0-with-no-node-on-source-cluster-was-able-to-connect-to-target-cluster

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Uninstalling replication controller

To uninstall the replication controller, you can use the script uninstall.sh located in the scripts folder:

./uninstall.sh

This script will automatically detect how the current version was installed (repctl or Helm) and use the correct method to delete it.

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Uninstalling replication controller

To uninstall the replication controller, you can use the script uninstall.sh located in the scripts folder:

./uninstall.sh

This script will automatically detect how the current version was installed (repctl or Helm) and use the correct method to delete it.

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Uninstalling replication controller

To uninstall the replication controller, you can use the script uninstall.sh located in the scripts folder:

./uninstall.sh

This script will automatically detect how the current version was installed (repctl or Helm) and use the correct method to delete it.

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Uninstalling replication controller

To uninstall the replication controller, you can use the script uninstall.sh located in the scripts folder:

./uninstall.sh

This script will automatically detect how the current version was installed (repctl or Helm) and use the correct method to delete it.

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

CSM Replication module consists of two components:

CSM Replication sidecar (installed along with the driver)
CSM Replication controller

Those two components should be upgraded separately. When upgrading them ensure that you use the same versions for both sidecar and controller, because different versions could be incompatible with each other.

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

CSM Replication module consists of two components:

CSM Replication sidecar (installed along with the driver)
CSM Replication controller

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

CSM Replication module consists of two components:

CSM Replication sidecar (installed along with the driver)
CSM Replication controller

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

CSM Replication module consists of two components:

CSM Replication sidecar (installed along with the driver)
CSM Replication controller

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

CSM Replication module consists of two components:

CSM Replication sidecar (installed along with the driver)
CSM Replication controller

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Uninstalling replication controller

To uninstall the replication controller, you can use the script uninstall.sh located in the scripts folder:

./uninstall.sh

This script will automatically detect how the current version was installed (repctl or Helm) and use the correct method to delete it.

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Uninstalling replication controller

To uninstall the replication controller, you can use the script uninstall.sh located in the scripts folder:

./uninstall.sh

This script will automatically detect how the current version was installed (repctl or Helm) and use the correct method to delete it.

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Uninstalling replication controller

To uninstall the replication controller, you can use the script uninstall.sh located in the scripts folder:

./uninstall.sh

This script will automatically detect how the current version was installed (repctl or Helm) and use the correct method to delete it.

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Uninstalling replication controller

To uninstall the replication controller, you can use the script uninstall.sh located in the scripts folder:

./uninstall.sh

This script will automatically detect how the current version was installed (repctl or Helm) and use the correct method to delete it.

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

CSM Replication module consists of two components:

CSM Replication sidecar (installed along with the driver)
CSM Replication controller

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

CSM Replication module consists of two components:

CSM Replication sidecar (installed along with the driver)
CSM Replication controller

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

CSM Replication module consists of two components:

CSM Replication sidecar (installed along with the driver)
CSM Replication controller

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

CSM Replication module consists of two components:

CSM Replication sidecar (installed along with the driver)
CSM Replication controller

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

CSM Replication module consists of two components:

CSM Replication sidecar (installed along with the driver)
CSM Replication controller

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Uninstalling replication controller

To uninstall the replication controller, you can use the script uninstall.sh located in the scripts folder:

./uninstall.sh

This script will automatically detect how the current version was installed (repctl or Helm) and use the correct method to delete it.

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Uninstalling replication controller

To uninstall the replication controller, you can use the script uninstall.sh located in the scripts folder:

./uninstall.sh

This script will automatically detect how the current version was installed (repctl or Helm) and use the correct method to delete it.

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Uninstalling replication controller

To uninstall the replication controller, you can use the script uninstall.sh located in the scripts folder:

./uninstall.sh

This script will automatically detect how the current version was installed (repctl or Helm) and use the correct method to delete it.

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Uninstalling replication controller

To uninstall the replication controller, you can use the script uninstall.sh located in the scripts folder:

./uninstall.sh

This script will automatically detect how the current version was installed (repctl or Helm) and use the correct method to delete it.

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

CSM Replication module consists of two components:

CSM Replication sidecar (installed along with the driver)
CSM Replication controller

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

CSM Replication module consists of two components:

CSM Replication sidecar (installed along with the driver)
CSM Replication controller

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

CSM Replication module consists of two components:

CSM Replication sidecar (installed along with the driver)
CSM Replication controller

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

CSM Replication module consists of two components:

CSM Replication sidecar (installed along with the driver)
CSM Replication controller

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

CSM Replication module consists of two components:

CSM Replication sidecar (installed along with the driver)
CSM Replication controller

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Starting with CSM 1.12, all deployments will need to use images from quay.io. Please note that from CSM 1.14 (May 2025), upgrading with helm will fail if it attempts to use images from Docker Hub.

CSM Replication module consists of two components:

CSM Replication sidecar (installed along with the driver)
CSM Replication controller

Replication

Mon, 01 Jan 0001 00:00:00 +0000

This section outlines the uninstallation steps for Container Storage Modules (CSM) for Replication.

Uninstalling replication controller

To uninstall the replication controller, you can use the script uninstall.sh located in the scripts folder:

./uninstall.sh

This script will automatically detect how the current version was installed (repctl or Helm) and use the correct method to delete it.

Mon, 01 Jan 0001 00:00:00 +0000

Configure the parameters and install the CSM for Observability Helm Chart

A default values.yaml file is located here that can be used for installation. This can be copied into a file named myvalues.yaml and either used as is or modified accordingly.

Note:
- For CSI PowerFlex with Authorization, configure karaviMetricsPowerflex.authorization in myvalues.yaml.
- For CSI PowerScale with Authorization, configure karaviMetricsPowerscale.authorization in myvalues.yaml.
- For CSI PowerMax with Authorization, configure karaviMetricsPowerMax.authorization in myvalues.yaml

Mon, 01 Jan 0001 00:00:00 +0000

Copy only the deployed CSI driver entities to the Observability namespace

PowerMax
1. Copy the configmap powermax-reverseproxy-config from the CSI Driver for PowerMax namespace to the CSM namespace.
```
kubectl get configmap powermax-reverseproxy-config -n [CSI_DRIVER_NAMESPACE] -o yaml | sed 's/namespace: [CSI_DRIVER_NAMESPACE]/namespace: [CSM_NAMESPACE]/' | kubectl create -f -
```
  If the CSI driver configmap name is not the default powermax-reverseproxy-config, please use the following command to copy configmap:

Mon, 01 Jan 0001 00:00:00 +0000

Copy only the deployed CSI driver entities to the Observability namespace

PowerScale
1. Copy the config Secret from the CSI PowerScale namespace into the Container Storage Modules Observability namespace:
```
kubectl get secret isilon-creds -n [CSI_DRIVER_NAMESPACE] -o yaml | sed 's/namespace: [CSI_DRIVER_NAMESPACE]/namespace: [CSM_NAMESPACE]/' | kubectl create -f -
```
  If the CSI driver secret name is not the default isilon-creds, please use the following command to copy secret:

Mon, 01 Jan 0001 00:00:00 +0000

Copy only the deployed CSI driver entities to the Observability namespace

PowerStore
1. Copy the config Secret from the CSI PowerStore namespace into the Container Storage Modules Observability namespace:
```
kubectl get secret powerstore-config -n [CSI_DRIVER_NAMESPACE] -o yaml | sed 's/namespace: [CSI_DRIVER_NAMESPACE]/namespace: [CSM_NAMESPACE]/' | kubectl create -f -
```
  If the CSI driver secret name is not the default powerstore-config, please use the following command to copy secret:

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules (CSM) for Observability Helm chart bootstraps an Observability deployment on a Kubernetes cluster using the Helm package manager.

Prerequisites

Helm 3.x
The deployment of one or more supported Dell CSI drivers

Install the CSM for Observability Helm Chart

Steps

Mon, 01 Jan 0001 00:00:00 +0000

Dynamic parameters

CSM for Resiliency has configuration parameters that can be updated dynamically, such as the logging level and format. This can be done by editing the Dell CSI Driver’s parameters ConfigMap. The ConfigMap can be queried using kubectl. For example, the Dell Powerflex CSI Driver ConfigMaps can be found using this command: kubectl get -n vxflexos configmap. The ConfigMap to edit will have this pattern: -config-params (e.g., vxflexos-config-params).

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

CSM for Resiliency is installed as part of the Dell CSI driver installation.

For information on the PowerFlex CSI driver, see PowerFlex CSI Driver. For information on the Unity XT CSI driver, see Unity XT CSI Driver. For information on the PowerScale CSI driver, see PowerScale CSI Driver. For information on the PowerStore CSI driver, see PowerStore CSI Driver. For information on the PowerStore CSI driver, see PowerMax CSI Driver.

Prerequisite

The CSM for Resiliency module only acts on pods with a specific label.
This label must match the key and value set in the module’s configuration.
On startup, CSM for Resiliency logs the label key and value it uses to monitor pods.
Apply this label to the Statefulset you want monitored by CSM for Resiliency.

labelSelector: {map[podmon.dellemc.com/driver:csi-<driver>]}

The above message indicates the key is: podmon.dellemc.com/driver and the label value is csi-<driver>. To search for the pods that would be monitored, try this:

Mon, 01 Jan 0001 00:00:00 +0000

PowerFlex Specific Recommendations

PowerFlex supports a very robust array connection validation mechanism that can detect changes in connectivity in about two seconds and can detect whether I/O has occurred over a five-second sample. For that reason it is recommended to set “skipArrayConnectionValidation=false” (which is the default) and to set “arrayConnectivityPollRate=5” (5 seconds) and “arrayConnectivityConnectionLossThreshold=3” to 3 or more.

Mon, 01 Jan 0001 00:00:00 +0000

PowerMax Specific Recommendations

Here is a typical installation used for testing:

podmon:
  enabled: false
  controller:
    args:
      - "--csisock=unix:/var/run/csi/csi.sock"
      - "--labelvalue=csi-powermax"
      - "--arrayConnectivityPollRate=60"
      - "--driverPath=csi-powermax.dellemc.com"
      - "--mode=controller"
      - "--skipArrayConnectionValidation=false"
      - "--driver-config-params=/powermax-config-params/driver-config-params.yaml"
      - "--driverPodLabelValue=dell-storage"
      - "--ignoreVolumelessPods=false"

  node:
    args:
      - "--csisock=unix:/var/lib/kubelet/plugins/powermax.emc.dell.com/csi_sock"
      - "--labelvalue=csi-powermax"
      - "--arrayConnectivityPollRate=60"
      - "--driverPath=csi-powermax.dellemc.com"
      - "--mode=node"
      - "--leaderelection=false"
      - "--driver-config-params=/powermax-config-params/driver-config-params.yaml"
      - "--driverPodLabelValue=dell-storage"
      - "--ignoreVolumelessPods=false"

Mon, 01 Jan 0001 00:00:00 +0000

PowerScale Specific Recommendations

Here is a typical installation used for testing:

podmon:
  enabled: true
  controller:
    args:
      - "--csisock=unix:/var/run/csi/csi.sock"
      - "--labelvalue=csi-isilon"
      - "--arrayConnectivityPollRate=60"
      - "--driverPath=csi-isilon.dellemc.com"
      - "--mode=controller"
      - "--skipArrayConnectionValidation=false"
      - "--driver-config-params=/csi-isilon-config-params/driver-config-params.yaml"
      - "--driverPodLabelValue=dell-storage"
      - "--ignoreVolumelessPods=false"
  node:
    args:
      - "--csisock=unix:/var/lib/kubelet/plugins/csi-isilon/csi_sock"
      - "--labelvalue=csi-isilon"
      - "--arrayConnectivityPollRate=60"
      - "--driverPath=csi-isilon.dellemc.com"
      - "--mode=node"
      - "--leaderelection=false"
      - "--driver-config-params=/csi-isilon-config-params/driver-config-params.yaml"
      - "--driverPodLabelValue=dell-storage"
      - "--ignoreVolumelessPods=false"

Mon, 01 Jan 0001 00:00:00 +0000

PowerStore Specific Recommendations

Here is a typical installation used for testing:

podmon:
  enabled: true
  controller:
    args:
      - "--csisock=unix:/var/run/csi/csi.sock"
      - "--labelvalue=csi-powerstore"
      - "--arrayConnectivityPollRate=60"
      - "--driverPath=csi-powerstore.dellemc.com"
      - "--mode=controller"
      - "--skipArrayConnectionValidation=false"
      - "--driver-config-params=/powerstore-config-params/driver-config-params.yaml"
      - "--driverPodLabelValue=dell-storage"
      - "--ignoreVolumelessPods=false"

  node:
    args:
      - "--csisock=unix:/var/lib/kubelet/plugins/csi-powerstore.dellemc.com/csi_sock"
      - "--labelvalue=csi-powerstore"
      - "--arrayConnectivityPollRate=60"
      - "--driverPath=csi-powerstore.dellemc.com"
      - "--mode=node"
      - "--leaderelection=false"
      - "--driver-config-params=/powerstore-config-params/driver-config-params.yaml"
      - "--driverPodLabelValue=dell-storage"
      - "--ignoreVolumelessPods=false"

Mon, 01 Jan 0001 00:00:00 +0000

Unity XT Specific Recommendations

Here is a typical installation used for testing:

podmon:
   enabled: true
   controller:
     args:
       - "--csisock=unix:/var/run/csi/csi.sock"
       - "--labelvalue=csi-unity"
       - "--driverPath=csi-unity.dellemc.com"
       - "--mode=controller"
       - "--skipArrayConnectionValidation=false"
       - "--driver-config-params=/unity-config/driver-config-params.yaml"
       - "--driverPodLabelValue=dell-storage"
       - "--ignoreVolumelessPods=false"
   node:
     args:
       - "--csisock=unix:/var/lib/kubelet/plugins/unity.emc.dell.com/csi_sock"
       - "--labelvalue=csi-unity"
       - "--driverPath=csi-unity.dellemc.com"
       - "--mode=node"
       - "--leaderelection=false"
       - "--driver-config-params=/unity-config/driver-config-params.yaml"
       - "--driverPodLabelValue=dell-storage"
       - "--ignoreVolumelessPods=false"

Mon, 01 Jan 0001 00:00:00 +0000

CSM Installation Wizard | Dell Technologies

Container Storage Modules (CSM) Installation Wizard

Configure installation settings and repository

Installation Type

Array

Image Repository

Reset to default

CSM Version

Select modules for installation

Observability

Observability Metrics

Observability

Observability Metrics

Observability Topology

Observability Otel Collector

Replication

Target Cluster ID

Target Array ID

Target Unisphere

Resiliency

Label Value

Reset to default

Array Connectivity Poll Rate

Reset to default

Skip Array Connection Validation

Leader Election

Driver Pod Label Value

Reset to default

Ignore Volumeless Pods

Array Connectivity ConnectionLoss Threshold

Reset to default

Select the features for installation

Authorization

Authorization Skip Certificate Validation

Proxy Host

Cert Manager

Health Monitor

Migration

Resizer

Snapshot

Snap Name Prefix

Reset to default

Install SDC

SDC is required for using block storage. Verify your environment is supported on the SDC Release Notes before selecting this option. If your environment is not supported, refer to the manual installation instructions on the CSM Documentation.

Enable SDC SFTP Repo

Address for SDC SFTP Repo

Username for SDC SFTP Repo

Private secret name for SDC SFTP Repo

Public secret name for SDC SFTP Repo

Allow driver to rename SDC to match name of node

Prefix to apply for SDC names

Allow driver to approve SDC

Storage Capacity Tracking

Volume Group Snapshot

Max Volumes Per Node

Reset to default

NFS volume operations

Quota

Other configurations for installation

Storage Array Id

Storage Array Endpoint URL

Storage Array Backup Endpoint URL

Managed Array Id

Managed Array Endpoint URL

CSI Reverse Proxy

Cluster Prefix

Port Groups

Transport Protocol

iSCSI CHAP

Node Topology

vSphere

fc Port Group

fc Host Name

vCenter Host

vCenter Cred Secret

Allow Monitoring Pod

Certificate Secret Count

FS Group Policy

Controller Pods Count

Reset to default

Credentials

Volume Name Prefix

Reset to default

Multi NAS Failure Threshold

Reset to default

Multi NAS Cooldown Period

Reset to default

Install Controller Pods On Control Plane

Install Node Pods On Control Plane

Node Selector Label

Reset to default

Taint

Reset to default

Namespace

Reset to default

Generate YAML

Click on the documentation link for the steps to generate the certificates

Mon, 01 Jan 0001 00:00:00 +0000

Uninstall a CSI driver installed via Helm

To uninstall a driver, the csi-uninstall.sh script provides a handy wrapper around the helm utility. The only required argument for uninstallation is the namespace name. For example, to uninstall the driver:

Mon, 01 Jan 0001 00:00:00 +0000

This section outlines the uninstallation steps for Container Storage Modules (CSM) for Authorization v2.

Delete all Authorization Custom Resources(CRs)

The commands below will delete a Tenant, Role, and Storage system. All CRs must be deleted before Authorization is uninstalled.

Mon, 01 Jan 0001 00:00:00 +0000

Uninstall the CSM for Observability Helm Chart

The command below removes all the Kubernetes components associated with the chart.

helm delete karavi-observability --namespace [CSM_NAMESPACE]

You may also want to uninstall the CRDs created for cert-manager.

Mon, 01 Jan 0001 00:00:00 +0000

Uninstalling replication controller

To uninstall the replication controller, you can use the script uninstall.sh located in the scripts folder:

./uninstall.sh

This script will automatically detect how the current version was installed (repctl or Helm) and use the correct method to delete it.

Mon, 01 Jan 0001 00:00:00 +0000

Uninstallation through driver upgrade

Disable the podmon feature in your values file

podmon: 
  enabled: false

Upgrade the driver
- Helm

Mon, 01 Jan 0001 00:00:00 +0000

Uninstall CSI Driver and CSM Modules

The CSI Drivers and CSM Modules can be uninstalled by deleting the Custom Resource.

For e.g.

kubectl delete csm/<csm-object> -n <driver-namespace>

By default, the forceRemoveDriver option is set to true which will uninstall the CSI Driver and CSM Modules when the Custom Resource is deleted. Setting this option to false is not recommended.

Mon, 01 Jan 0001 00:00:00 +0000

Configure the parameters and install the CSM for Observability Helm Chart

A default values.yaml file is located here that can be used for installation. This can be copied into a file named myvalues.yaml and either used as is or modified accordingly.

Note:
- For CSI PowerFlex with Authorization, configure karaviMetricsPowerflex.authorization in myvalues.yaml.
- For CSI PowerScale with Authorization, configure karaviMetricsPowerscale.authorization in myvalues.yaml.
- For CSI PowerMax with Authorization, configure karaviMetricsPowerMax.authorization in myvalues.yaml

Mon, 01 Jan 0001 00:00:00 +0000

Copy only the deployed CSI driver entities to the Observability namespace

PowerMax
1. Copy the configmap powermax-reverseproxy-config from the CSI Driver for PowerMax namespace to the CSM namespace.
```
kubectl get configmap powermax-reverseproxy-config -n [CSI_DRIVER_NAMESPACE] -o yaml | sed 's/namespace: [CSI_DRIVER_NAMESPACE]/namespace: [CSM_NAMESPACE]/' | kubectl create -f -
```
  If the CSI driver configmap name is not the default powermax-reverseproxy-config, please use the following command to copy configmap:

Mon, 01 Jan 0001 00:00:00 +0000

Copy only the deployed CSI driver entities to the Observability namespace

PowerScale
1. Copy the config Secret from the CSI PowerScale namespace into the Container Storage Modules Observability namespace:
```
kubectl get secret isilon-creds -n [CSI_DRIVER_NAMESPACE] -o yaml | sed 's/namespace: [CSI_DRIVER_NAMESPACE]/namespace: [CSM_NAMESPACE]/' | kubectl create -f -
```
  If the CSI driver secret name is not the default isilon-creds, please use the following command to copy secret:

Mon, 01 Jan 0001 00:00:00 +0000

Copy only the deployed CSI driver entities to the Observability namespace

PowerStore
1. Copy the config Secret from the CSI PowerStore namespace into the Container Storage Modules Observability namespace:
```
kubectl get secret powerstore-config -n [CSI_DRIVER_NAMESPACE] -o yaml | sed 's/namespace: [CSI_DRIVER_NAMESPACE]/namespace: [CSM_NAMESPACE]/' | kubectl create -f -
```
  If the CSI driver secret name is not the default powerstore-config, please use the following command to copy secret:

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules (CSM) for Observability Helm chart bootstraps an Observability deployment on a Kubernetes cluster using the Helm package manager.

Prerequisites

Helm 3.x
The deployment of one or more supported Dell CSI drivers

Install the CSM for Observability Helm Chart

Steps

Mon, 01 Jan 0001 00:00:00 +0000

Dynamic parameters

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

CSM for Resiliency is installed as part of the Dell CSI driver installation.

Prerequisite

The CSM for Resiliency module only acts on pods with a specific label.
This label must match the key and value set in the module’s configuration.
On startup, CSM for Resiliency logs the label key and value it uses to monitor pods.
Apply this label to the Statefulset you want monitored by CSM for Resiliency.

labelSelector: {map[podmon.dellemc.com/driver:csi-<driver>]}

The above message indicates the key is: podmon.dellemc.com/driver and the label value is csi-<driver>. To search for the pods that would be monitored, try this:

Mon, 01 Jan 0001 00:00:00 +0000

PowerFlex Specific Recommendations

Mon, 01 Jan 0001 00:00:00 +0000

PowerMax Specific Recommendations

Here is a typical installation used for testing:

podmon:
  enabled: false
  controller:
    args:
      - "--csisock=unix:/var/run/csi/csi.sock"
      - "--labelvalue=csi-powermax"
      - "--arrayConnectivityPollRate=60"
      - "--driverPath=csi-powermax.dellemc.com"
      - "--mode=controller"
      - "--skipArrayConnectionValidation=false"
      - "--driver-config-params=/powermax-config-params/driver-config-params.yaml"
      - "--driverPodLabelValue=dell-storage"
      - "--ignoreVolumelessPods=false"

  node:
    args:
      - "--csisock=unix:/var/lib/kubelet/plugins/powermax.emc.dell.com/csi_sock"
      - "--labelvalue=csi-powermax"
      - "--arrayConnectivityPollRate=60"
      - "--driverPath=csi-powermax.dellemc.com"
      - "--mode=node"
      - "--leaderelection=false"
      - "--driver-config-params=/powermax-config-params/driver-config-params.yaml"
      - "--driverPodLabelValue=dell-storage"
      - "--ignoreVolumelessPods=false"

Mon, 01 Jan 0001 00:00:00 +0000

PowerScale Specific Recommendations

Here is a typical installation used for testing:

podmon:
  enabled: true
  controller:
    args:
      - "--csisock=unix:/var/run/csi/csi.sock"
      - "--labelvalue=csi-isilon"
      - "--arrayConnectivityPollRate=60"
      - "--driverPath=csi-isilon.dellemc.com"
      - "--mode=controller"
      - "--skipArrayConnectionValidation=false"
      - "--driver-config-params=/csi-isilon-config-params/driver-config-params.yaml"
      - "--driverPodLabelValue=dell-storage"
      - "--ignoreVolumelessPods=false"
  node:
    args:
      - "--csisock=unix:/var/lib/kubelet/plugins/csi-isilon/csi_sock"
      - "--labelvalue=csi-isilon"
      - "--arrayConnectivityPollRate=60"
      - "--driverPath=csi-isilon.dellemc.com"
      - "--mode=node"
      - "--leaderelection=false"
      - "--driver-config-params=/csi-isilon-config-params/driver-config-params.yaml"
      - "--driverPodLabelValue=dell-storage"
      - "--ignoreVolumelessPods=false"

Mon, 01 Jan 0001 00:00:00 +0000

PowerStore Specific Recommendations

Here is a typical installation used for testing:

podmon:
  enabled: true
  controller:
    args:
      - "--csisock=unix:/var/run/csi/csi.sock"
      - "--labelvalue=csi-powerstore"
      - "--arrayConnectivityPollRate=60"
      - "--driverPath=csi-powerstore.dellemc.com"
      - "--mode=controller"
      - "--skipArrayConnectionValidation=false"
      - "--driver-config-params=/powerstore-config-params/driver-config-params.yaml"
      - "--driverPodLabelValue=dell-storage"
      - "--ignoreVolumelessPods=false"

  node:
    args:
      - "--csisock=unix:/var/lib/kubelet/plugins/csi-powerstore.dellemc.com/csi_sock"
      - "--labelvalue=csi-powerstore"
      - "--arrayConnectivityPollRate=60"
      - "--driverPath=csi-powerstore.dellemc.com"
      - "--mode=node"
      - "--leaderelection=false"
      - "--driver-config-params=/powerstore-config-params/driver-config-params.yaml"
      - "--driverPodLabelValue=dell-storage"
      - "--ignoreVolumelessPods=false"

Mon, 01 Jan 0001 00:00:00 +0000

Unity XT Specific Recommendations

Here is a typical installation used for testing:

podmon:
   enabled: true
   controller:
     args:
       - "--csisock=unix:/var/run/csi/csi.sock"
       - "--labelvalue=csi-unity"
       - "--driverPath=csi-unity.dellemc.com"
       - "--mode=controller"
       - "--skipArrayConnectionValidation=false"
       - "--driver-config-params=/unity-config/driver-config-params.yaml"
       - "--driverPodLabelValue=dell-storage"
       - "--ignoreVolumelessPods=false"
   node:
     args:
       - "--csisock=unix:/var/lib/kubelet/plugins/unity.emc.dell.com/csi_sock"
       - "--labelvalue=csi-unity"
       - "--driverPath=csi-unity.dellemc.com"
       - "--mode=node"
       - "--leaderelection=false"
       - "--driver-config-params=/unity-config/driver-config-params.yaml"
       - "--driverPodLabelValue=dell-storage"
       - "--ignoreVolumelessPods=false"

Mon, 01 Jan 0001 00:00:00 +0000

CSM Installation Wizard | Dell Technologies

Container Storage Modules (CSM) Installation Wizard

Configure installation settings and repository

Installation Type

Array

Image Repository

Reset to default

CSM Version

Select modules for installation

Observability

Observability Metrics

Observability

Observability Metrics

Observability Topology

Observability Otel Collector

Replication

Target Cluster ID

Target Array ID

Target Unisphere

Resiliency

Label Value

Reset to default

Array Connectivity Poll Rate

Reset to default

Skip Array Connection Validation

Leader Election

Driver Pod Label Value

Reset to default

Ignore Volumeless Pods

Array Connectivity ConnectionLoss Threshold

Reset to default

Select the features for installation

Authorization

Authorization Skip Certificate Validation

Proxy Host

Cert Manager

Health Monitor

Migration

Resizer

Snapshot

Snap Name Prefix

Reset to default

Install SDC

Enable SDC SFTP Repo

Address for SDC SFTP Repo

Username for SDC SFTP Repo

Private secret name for SDC SFTP Repo

Public secret name for SDC SFTP Repo

Allow driver to rename SDC to match name of node

Prefix to apply for SDC names

Allow driver to approve SDC

Storage Capacity Tracking

Volume Group Snapshot

Max Volumes Per Node

Reset to default

NFS volume operations

Quota

Other configurations for installation

Storage Array Id

Storage Array Endpoint URL

Storage Array Backup Endpoint URL

Managed Array Id

Managed Array Endpoint URL

CSI Reverse Proxy

Cluster Prefix

Port Groups

Transport Protocol

iSCSI CHAP

Node Topology

vSphere

fc Port Group

fc Host Name

vCenter Host

vCenter Cred Secret

Allow Monitoring Pod

Certificate Secret Count

FS Group Policy

Controller Pods Count

Reset to default

Credentials

Volume Name Prefix

Reset to default

Multi NAS Failure Threshold

Reset to default

Multi NAS Cooldown Period

Reset to default

Install Controller Pods On Control Plane

Install Node Pods On Control Plane

Node Selector Label

Reset to default

Taint

Reset to default

Namespace

Reset to default

Generate YAML

Click on the documentation link for the steps to generate the certificates

Mon, 01 Jan 0001 00:00:00 +0000

Uninstall a CSI driver installed via Helm

Mon, 01 Jan 0001 00:00:00 +0000

This section outlines the uninstallation steps for Container Storage Modules (CSM) for Authorization v2.

Delete all Authorization Custom Resources(CRs)

The commands below will delete a Tenant, Role, and Storage system. All CRs must be deleted before Authorization is uninstalled.

Mon, 01 Jan 0001 00:00:00 +0000

Uninstall the CSM for Observability Helm Chart

The command below removes all the Kubernetes components associated with the chart.

helm delete karavi-observability --namespace [CSM_NAMESPACE]

You may also want to uninstall the CRDs created for cert-manager.

Mon, 01 Jan 0001 00:00:00 +0000

Uninstalling replication controller

To uninstall the replication controller, you can use the script uninstall.sh located in the scripts folder:

./uninstall.sh

This script will automatically detect how the current version was installed (repctl or Helm) and use the correct method to delete it.

Mon, 01 Jan 0001 00:00:00 +0000

Uninstallation through driver upgrade

Disable the podmon feature in your values file

podmon: 
  enabled: false

Upgrade the driver
- Helm

Mon, 01 Jan 0001 00:00:00 +0000

Uninstall CSI Driver and CSM Modules

The CSI Drivers and CSM Modules can be uninstalled by deleting the Custom Resource.

For e.g.

kubectl delete csm/<csm-object> -n <driver-namespace>

By default, the forceRemoveDriver option is set to true which will uninstall the CSI Driver and CSM Modules when the Custom Resource is deleted. Setting this option to false is not recommended.

Mon, 01 Jan 0001 00:00:00 +0000

Configure the parameters and install the CSM for Observability Helm Chart

A default values.yaml file is located here that can be used for installation. This can be copied into a file named myvalues.yaml and either used as is or modified accordingly.

Note:
- The default values.yaml deploys the CSM for Observability Topology service.
- For CSI PowerFlex with Authorization, configure karaviMetricsPowerflex.authorization in myvalues.yaml.
- For CSI PowerScale with Authorization, configure karaviMetricsPowerscale.authorization in myvalues.yaml.
- For CSI PowerMax with Authorization, configure karaviMetricsPowerMax.authorization in myvalues.yaml

Mon, 01 Jan 0001 00:00:00 +0000

Copy only the deployed CSI driver entities to the Observability namespace

PowerMax
1. Copy the configmap powermax-reverseproxy-config from the CSI Driver for PowerMax namespace to the CSM namespace.
```
kubectl get configmap powermax-reverseproxy-config -n [CSI_DRIVER_NAMESPACE] -o yaml | sed 's/namespace: [CSI_DRIVER_NAMESPACE]/namespace: [CSM_NAMESPACE]/' | kubectl create -f -
```
  If the CSI driver configmap name is not the default powermax-reverseproxy-config, please use the following command to copy configmap:

Mon, 01 Jan 0001 00:00:00 +0000

Copy only the deployed CSI driver entities to the Observability namespace

PowerScale
1. Copy the config Secret from the CSI PowerScale namespace into the Container Storage Modules Observability namespace:
```
kubectl get secret isilon-creds -n [CSI_DRIVER_NAMESPACE] -o yaml | sed 's/namespace: [CSI_DRIVER_NAMESPACE]/namespace: [CSM_NAMESPACE]/' | kubectl create -f -
```
  If the CSI driver secret name is not the default isilon-creds, please use the following command to copy secret:

Mon, 01 Jan 0001 00:00:00 +0000

Copy only the deployed CSI driver entities to the Observability namespace

PowerStore
1. Copy the config Secret from the CSI PowerStore namespace into the Container Storage Modules Observability namespace:
```
kubectl get secret powerstore-config -n [CSI_DRIVER_NAMESPACE] -o yaml | sed 's/namespace: [CSI_DRIVER_NAMESPACE]/namespace: [CSM_NAMESPACE]/' | kubectl create -f -
```
  If the CSI driver secret name is not the default powerstore-config, please use the following command to copy secret:

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules (CSM) for Observability Helm chart bootstraps an Observability deployment on a Kubernetes cluster using the Helm package manager.

Prerequisites

Helm 3.x
The deployment of one or more supported Dell CSI drivers

Install the CSM for Observability Helm Chart

Steps

Mon, 01 Jan 0001 00:00:00 +0000

Dynamic parameters

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

CSM for Resiliency is installed as part of the Dell CSI driver installation.

Prerequisite

The CSM for Resiliency module only acts on pods with a specific label.
This label must match the key and value set in the module’s configuration.
On startup, CSM for Resiliency logs the label key and value it uses to monitor pods.
Apply this label to the Statefulset you want monitored by CSM for Resiliency.

labelSelector: {map[podmon.dellemc.com/driver:csi-<driver>]}

The above message indicates the key is: podmon.dellemc.com/driver and the label value is csi-<driver>. To search for the pods that would be monitored, try this:

Mon, 01 Jan 0001 00:00:00 +0000

PowerFlex Specific Recommendations

Mon, 01 Jan 0001 00:00:00 +0000

PowerMax Specific Recommendations

Here is a typical installation used for testing:

podmon:
  enabled: false
  controller:
    args:
      - "--csisock=unix:/var/run/csi/csi.sock"
      - "--labelvalue=csi-powermax"
      - "--arrayConnectivityPollRate=60"
      - "--driverPath=csi-powermax.dellemc.com"
      - "--mode=controller"
      - "--skipArrayConnectionValidation=false"
      - "--driver-config-params=/powermax-config-params/driver-config-params.yaml"
      - "--driverPodLabelValue=dell-storage"
      - "--ignoreVolumelessPods=false"

  node:
    args:
      - "--csisock=unix:/var/lib/kubelet/plugins/powermax.emc.dell.com/csi_sock"
      - "--labelvalue=csi-powermax"
      - "--arrayConnectivityPollRate=60"
      - "--driverPath=csi-powermax.dellemc.com"
      - "--mode=node"
      - "--leaderelection=false"
      - "--driver-config-params=/powermax-config-params/driver-config-params.yaml"
      - "--driverPodLabelValue=dell-storage"
      - "--ignoreVolumelessPods=false"

Mon, 01 Jan 0001 00:00:00 +0000

PowerScale Specific Recommendations

Here is a typical installation used for testing:

podmon:
  enabled: true
  controller:
    args:
      - "--csisock=unix:/var/run/csi/csi.sock"
      - "--labelvalue=csi-isilon"
      - "--arrayConnectivityPollRate=60"
      - "--driverPath=csi-isilon.dellemc.com"
      - "--mode=controller"
      - "--skipArrayConnectionValidation=false"
      - "--driver-config-params=/csi-isilon-config-params/driver-config-params.yaml"
      - "--driverPodLabelValue=dell-storage"
      - "--ignoreVolumelessPods=false"
  node:
    args:
      - "--csisock=unix:/var/lib/kubelet/plugins/csi-isilon/csi_sock"
      - "--labelvalue=csi-isilon"
      - "--arrayConnectivityPollRate=60"
      - "--driverPath=csi-isilon.dellemc.com"
      - "--mode=node"
      - "--leaderelection=false"
      - "--driver-config-params=/csi-isilon-config-params/driver-config-params.yaml"
      - "--driverPodLabelValue=dell-storage"
      - "--ignoreVolumelessPods=false"

Mon, 01 Jan 0001 00:00:00 +0000

PowerStore Specific Recommendations

Here is a typical installation used for testing:

podmon:
  enabled: true
  controller:
    args:
      - "--csisock=unix:/var/run/csi/csi.sock"
      - "--labelvalue=csi-powerstore"
      - "--arrayConnectivityPollRate=60"
      - "--driverPath=csi-powerstore.dellemc.com"
      - "--mode=controller"
      - "--skipArrayConnectionValidation=false"
      - "--driver-config-params=/powerstore-config-params/driver-config-params.yaml"
      - "--driverPodLabelValue=dell-storage"
      - "--ignoreVolumelessPods=false"

  node:
    args:
      - "--csisock=unix:/var/lib/kubelet/plugins/csi-powerstore.dellemc.com/csi_sock"
      - "--labelvalue=csi-powerstore"
      - "--arrayConnectivityPollRate=60"
      - "--driverPath=csi-powerstore.dellemc.com"
      - "--mode=node"
      - "--leaderelection=false"
      - "--driver-config-params=/powerstore-config-params/driver-config-params.yaml"
      - "--driverPodLabelValue=dell-storage"
      - "--ignoreVolumelessPods=false"

Mon, 01 Jan 0001 00:00:00 +0000

Unity XT Specific Recommendations

Here is a typical installation used for testing:

podmon:
   enabled: true
   controller:
     args:
       - "--csisock=unix:/var/run/csi/csi.sock"
       - "--labelvalue=csi-unity"
       - "--driverPath=csi-unity.dellemc.com"
       - "--mode=controller"
       - "--skipArrayConnectionValidation=false"
       - "--driver-config-params=/unity-config/driver-config-params.yaml"
       - "--driverPodLabelValue=dell-storage"
       - "--ignoreVolumelessPods=false"
   node:
     args:
       - "--csisock=unix:/var/lib/kubelet/plugins/unity.emc.dell.com/csi_sock"
       - "--labelvalue=csi-unity"
       - "--driverPath=csi-unity.dellemc.com"
       - "--mode=node"
       - "--leaderelection=false"
       - "--driver-config-params=/unity-config/driver-config-params.yaml"
       - "--driverPodLabelValue=dell-storage"
       - "--ignoreVolumelessPods=false"

Mon, 01 Jan 0001 00:00:00 +0000

CSM Installation Wizard | Dell Technologies

Container Storage Modules (CSM) Installation Wizard

Configure installation settings and repository

Installation Type

Array

Image Repository

Reset to default

CSM Version

Select modules for installation

Observability

Observability Metrics

Observability

Observability Metrics

Observability Topology

Observability Otel Collector

Replication

Target Cluster ID

Target Array ID

Target Unisphere

Resiliency

Label Value

Reset to default

Array Connectivity Poll Rate

Reset to default

Skip Array Connection Validation

Leader Election

Driver Pod Label Value

Reset to default

Ignore Volumeless Pods

Array Connectivity ConnectionLoss Threshold

Reset to default

Select the features for installation

Authorization

Authorization Skip Certificate Validation

Proxy Host

Cert Manager

Health Monitor

Migration

Resizer

Snapshot

Snap Name Prefix

Reset to default

Install SDC

Enable SDC SFTP Repo

Address for SDC SFTP Repo

Username for SDC SFTP Repo

Private secret name for SDC SFTP Repo

Public secret name for SDC SFTP Repo

Allow driver to rename SDC to match name of node

Prefix to apply for SDC names

Allow driver to approve SDC

Storage Capacity Tracking

Volume Group Snapshot

Max Volumes Per Node

Reset to default

NFS volume operations

Quota

Other configurations for installation

Storage Array Id

Storage Array Endpoint URL

Storage Array Backup Endpoint URL

Managed Array Id

Managed Array Endpoint URL

CSI Reverse Proxy

Cluster Prefix

Port Groups

Transport Protocol

iSCSI CHAP

Node Topology

vSphere

fc Port Group

fc Host Name

vCenter Host

vCenter Cred Secret

Allow Monitoring Pod

Certificate Secret Count

FS Group Policy

Controller Pods Count

Reset to default

Credentials

Volume Name Prefix

Reset to default

Multi NAS Failure Threshold

Reset to default

Multi NAS Cooldown Period

Reset to default

Install Controller Pods On Control Plane

Install Node Pods On Control Plane

Node Selector Label

Reset to default

Taint

Reset to default

Namespace

Reset to default

Generate YAML

Click on the documentation link for the steps to generate the certificates

Mon, 01 Jan 0001 00:00:00 +0000

Uninstall a CSI driver installed via Helm

Mon, 01 Jan 0001 00:00:00 +0000

This section outlines the uninstallation steps for Container Storage Modules (CSM) for Authorization.

Uninstall the CSM for Authorization Helm Chart

The command below removes all the Kubernetes components associated with the chart.

helm uninstall authorization --namespace authorization

You may also want to delete the karavi-config-secret secret.

Mon, 01 Jan 0001 00:00:00 +0000

This section outlines the uninstallation steps for Container Storage Modules (CSM) for Authorization v2.

Delete all Authorization Custom Resources(CRs)

The commands below will delete a Tenant, Role, and Storage system. All CRs must be deleted before Authorization is uninstalled.

Mon, 01 Jan 0001 00:00:00 +0000

Uninstall the CSM for Observability Helm Chart

The command below removes all the Kubernetes components associated with the chart.

helm delete karavi-observability --namespace [CSM_NAMESPACE]

You may also want to uninstall the CRDs created for cert-manager.

Mon, 01 Jan 0001 00:00:00 +0000

Uninstalling replication controller

To uninstall the replication controller, you can use the script uninstall.sh located in the scripts folder:

./uninstall.sh

This script will automatically detect how the current version was installed (repctl or Helm) and use the correct method to delete it.

Mon, 01 Jan 0001 00:00:00 +0000

Uninstallation through driver upgrade

Disable the podmon feature in your values file

podmon: 
  enabled: false

Upgrade the driver
- Helm

Mon, 01 Jan 0001 00:00:00 +0000

Uninstall CSI Driver and CSM Modules

The CSI Drivers and CSM Modules can be uninstalled by deleting the Custom Resource.

For e.g.

kubectl delete csm/<csm-object> -n <driver-namespace>

By default, the forceRemoveDriver option is set to true which will uninstall the CSI Driver and CSM Modules when the Custom Resource is deleted. Setting this option to false is not recommended.

Mon, 01 Jan 0001 00:00:00 +0000

CSM Installation Wizard | Dell Technologies

Container Storage Modules (CSM) Installation Wizard

Configure installation settings and repository

Installation Type

Array

Image Repository

Reset to default

CSM Version

Select modules for installation

Observability

Observability Metrics

Observability

Observability Metrics

Observability Topology

Observability Otel Collector

Replication

Target Cluster ID

Target Array ID

Target Unisphere

Resiliency

Label Value

Reset to default

Array Connectivity Poll Rate

Reset to default

Skip Array Connection Validation

Leader Election

Driver Pod Label Value

Reset to default

Ignore Volumeless Pods

Array Connectivity ConnectionLoss Threshold

Reset to default

Select the features for installation

Authorization

Authorization Skip Certificate Validation

Proxy Host

Cert Manager

Health Monitor

Migration

Resizer

Snapshot

Snap Name Prefix

Reset to default

Install SDC

Allow driver to rename SDC to match name of node

Prefix to apply for SDC names

Allow driver to approve SDC

Storage Capacity Tracking

Volume Group Snapshot

Max Volumes Per Node

Reset to default

NFS volume operations

Quota

Other configurations for installation

Storage Array Id

Storage Array Endpoint URL

Storage Array Backup Endpoint URL

Managed Array Id

Managed Array Endpoint URL

CSI Reverse Proxy

Cluster Prefix

Port Groups

Transport Protocol

iSCSI CHAP

Node Topology

vSphere

fc Port Group

fc Host Name

vCenter Host

vCenter Cred Secret

Allow Monitoring Pod

Certificate Secret Count

FS Group Policy

Controller Pods Count

Reset to default

Volume Name Prefix

Reset to default

Install Controller Pods On Control Plane

Install Node Pods On Control Plane

Node Selector Label

Reset to default

Taint

Reset to default

Namespace

Reset to default

Generate YAML

Click on the documentation link for the steps to generate the certificates

Authorization v1.x

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.
As of Container Storage Modules v1.15, Authorization v1.x will not be supported. Please migrate to Authorization v2.0 using the following guide.

Container Storage Modules Authorization can be installed by using the provided Helm v3 charts on Kubernetes platforms.

The following Container Storage Modules Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v1.x

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.
As of Container Storage Modules v1.15, Authorization v1.x will not be supported. Please migrate to Authorization v2.0 using the following guide.

Install CSM Authorization via Container Storage Modules Operator

Prerequisite

Execute kubectl create namespace authorization to create the authorization namespace (if not already present). Note that the namespace can be any user-defined name, in this example, we assume that the namespace is ‘authorization’.

Authorization v1.x

Mon, 01 Jan 0001 00:00:00 +0000

Authorization v1.x

Mon, 01 Jan 0001 00:00:00 +0000

Upgrade CSM Authorization

This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization is handled in 2 parts:

Upgrading the Authorization proxy server
Upgrading CSI Driver, Authorization sidecar with Authorization module enabled

Upgrading the Authorization Proxy Server

Modifying the existing Authorization Proxy Server installation directly via kubectl edit

Authorization v1.x

Mon, 01 Jan 0001 00:00:00 +0000

Upgrade CSM Authorization

This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization is handled in 2 parts:

Upgrading the Authorization proxy server
Upgrading CSI Driver, Authorization sidecar with Authorization module enabled

Upgrading the Authorization Proxy Server

Modifying the existing Authorization Proxy Server installation directly via kubectl edit

Authorization v1.x

Mon, 01 Jan 0001 00:00:00 +0000

Upgrade CSM Authorization

This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization is handled in 2 parts:

Upgrading the Authorization proxy server
Upgrading CSI Driver, Authorization sidecar with Authorization module enabled

Upgrading the Authorization Proxy Server

Modifying the existing Authorization Proxy Server installation directly via kubectl edit

Authorization v1.x

Mon, 01 Jan 0001 00:00:00 +0000

Upgrade CSM Authorization

This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization is handled in 2 parts:

Upgrading the Authorization proxy server
Upgrading CSI Driver, Authorization sidecar with Authorization module enabled

Upgrading the Authorization Proxy Server

Modifying the existing Authorization Proxy Server installation directly via kubectl edit

Authorization v1.x

Mon, 01 Jan 0001 00:00:00 +0000

Upgrade CSM Authorization

This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization is handled in 2 parts:

Upgrading the Authorization proxy server
Upgrading CSI Driver, Authorization sidecar with Authorization module enabled

Upgrading the Authorization Proxy Server

Modifying the existing Authorization Proxy Server installation directly via kubectl edit

Authorization v1.x

Mon, 01 Jan 0001 00:00:00 +0000

Upgrade CSM Authorization

This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization is handled in 2 parts:

Upgrading the Authorization proxy server
Upgrading CSI Driver, Authorization sidecar with Authorization module enabled

Upgrading the Authorization Proxy Server

Modifying the existing Authorization Proxy Server installation directly via kubectl edit

Authorization v1.x

Mon, 01 Jan 0001 00:00:00 +0000

Upgrade CSM Authorization

This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization is handled in 2 parts:

Upgrading the Authorization proxy server
Upgrading CSI Driver, Authorization sidecar with Authorization module enabled

Upgrading the Authorization Proxy Server

Modifying the existing Authorization Proxy Server installation directly via kubectl edit

Authorization v1.x

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.
As of Container Storage Modules v1.15, Authorization v1.x will not be supported. Please migrate to Authorization v2.0 using the following guide.

Install CSM Authorization via Dell CSM Operator

The CSM Authorization module for supported Dell CSI Drivers can be installed via the Dell CSM Operator. To deploy the Operator, follow the instructions available here.

Authorization v1.x

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.
As of Container Storage Modules v1.15, Authorization v1.x will not be supported. Please migrate to Authorization v2.0 using the following guide.

This section outlines the deployment steps for Container Storage Modules (CSM) for Authorization. The deployment of CSM for Authorization is handled in 2 parts:

Deploying the CSM for Authorization proxy server, to be controlled by storage administrators
Configuring one to many supported Dell CSI drivers with CSM for Authorization

Prerequisites

The CSM for Authorization proxy server requires a Linux host with the following minimum resource allocations:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Authorization can be installed by using the provided Helm v3 charts on Kubernetes platforms.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following Authorization components are installed in the specified namespace:

proxy-service, which forwards requests from the CSI Driver to the backend storage array
tenant-service, which configures tenants, role bindings, and generates JSON Web Tokens
role-service, which configures roles for tenants to be bound to
storage-service, which configures backend storage arrays for the proxy-server to forward requests to

The following third-party components are installed in the specified namespace:

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Install Container Storage Modules Authorization via Container Storage Modules Operator

Prerequisite

Install Vault or configure an existing Vault.

Authorization v2.0

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

Install CSM Authorization via Dell CSM Operator

The CSM Authorization module for supported Dell CSI Drivers can be installed via the Dell CSM Operator. To deploy the Operator, follow the instructions available here.

Community Qualified Configurations

Mon, 01 Jan 0001 00:00:00 +0000

cert-csi results	OS	CO	Storage Platform	Protocol	CSM
Ticket 1079	Debian 10	K3s v1.24.7+k3s1	Unity VSA 5.3.1.0.5.008	iSCSI	CSI v2.8.0
Ticket 1177	Ubuntu OS 22.04	Amazon EKS (K8s 1.29)	PowerFlex	SCINI	CSI v2.9.2
Ticket 1361	RHCOS 4.12	OpenShift 4.12	PowerStore	iSCSI	CSI v2.8.0
Ticket 1362	RHCOS 4.12	OpenShift 4.12	PowerScale	NFS	CSI v2.8.0
Ticket 1390	RHCOS 4.15	OpenShift 4.15	PowerStore	NVMeTCP	CSI v2.10.1
Ticket 1441 Ticket 1462	Ubuntu 20.04.x	MKE 3.6.13	PowerScale, PowerFlex	NFS	CSI v2.11.0
Ticket 1442	RHCOS 4.14.92	OKE 4.14.31	PowerScale	NFS	CSI v2.11.0
Ticket 1456	RHCOS 4.14.92	OKE 4.14.31	PowerFlex	NFS	CSI v2.11.0
Ticket 1479	Ubuntu 18.04.x	OpenShift 4.17	PowerFlex	iSCSI	CSI v2.11.0
Ticket 1500 Ticket 1501	RHCOS 4.14	OpenShift 4.14.x	PowerStore	iSCSI	CSI 2.10.1
Ticket 1513	RHCOS 4.14	OpenShift 4.14	PowerScale	NFS	CSI v2.6.1
Ticket 1516	Ubuntu 20.04.x	MKE - 3.6.13	PowerFlex	iSCSI	CSI v2.11.0
Ticket 1590	RHCOS 4.14	OpenShift 4.14	Unity 680F 5.4.0.0.5.094	NFS	CSI v2.12.0
Ticket 1622	Ubuntu 20.04.6 LTS	MKE - 3.6.13	PowerScale v9.5.0.8	NFS	CSI v2.12.0
Ticket 1623	Red Hat Enterprise Linux CoreOS	OKE 4.14.31	PowerScale v9.5.0.8	NFS	CSI v2.12.0
Ticket 1624	Red Hat Enterprise Linux CoreOS	OKE 4.14.31	PowerFlex 3.6.4000	NFS	CSI v2.12.0
Ticket 1625	Ubuntu 20.04.6 LTS	MKE - 3.6.13	PowerFlex 3.6.4000	NFS	CSI v2.12.0

CSI to CSM Operator Migration

Mon, 01 Jan 0001 00:00:00 +0000

Migration Steps

Save the CR yaml file of the current CSI driver to preserve the settings. Use the following commands in your cluster to get the CR:

    kubectl -n <namespace> get <CRD_kind>
    kubectl -n <namespace> get <CRD_kind>/<CR_name> -o yaml

Installation Wizard Overview

Installation Wizard

Mon, 01 Jan 0001 00:00:00 +0000

CSM Installation Wizard Support Matrix Click Here

Generate Manifest File

Open the Installation Wizard.
Select the Installation Type as Helm/Operator.
Select the Array.
Enter the Image Repository. The default value is dellemc.
Select the CSM Version.
Select the modules for installation. If there are module specific inputs, enter their values.
If needed, modify the Controller Pods Count.
If needed, select Install Controller Pods on Control Plane and/or Install Node Pods on Control Plane.
Enter the Namespace. The default value is csi-<array>.
Click on Generate YAML.
A manifest file, values.yaml will be generated and downloaded.
A section Run the following commands to install will be displayed.
Run the commands displayed to install Dell CSI Driver and Modules using the generated manifest file.

Installation Using Operator

Steps

Installation Wizard

Mon, 01 Jan 0001 00:00:00 +0000

CSM Installation Wizard Support Matrix Click Here

Generate Manifest File

Open the Installation Wizard.
Select the Installation Type as Helm/Operator.
Select the Array.
Enter the Image Repository. The default value is dellemc.
Select the CSM Version.
Select the modules for installation. If there are module specific inputs, enter their values.
If needed, modify the Controller Pods Count.
If needed, select Install Controller Pods on Control Plane and/or Install Node Pods on Control Plane.
Enter the Namespace. The default value is csi-<array>.
Click on Generate YAML.
A manifest file, values.yaml will be generated and downloaded.
A section Run the following commands to install will be displayed.
Run the commands displayed to install Dell CSI Driver and Modules using the generated manifest file.

Installation Using Operator

Steps

Installation Wizard

Mon, 01 Jan 0001 00:00:00 +0000

CSM Installation Wizard Support Matrix Click Here

Generate Manifest File

Open the Installation Wizard.
Select the Installation Type as Helm/Operator.
Select the Array.
Enter the Image Repository. The default value is dellemc.
Select the CSM Version.
Select the modules for installation. If there are module specific inputs, enter their values.
If needed, modify the Controller Pods Count.
If needed, select Install Controller Pods on Control Plane and/or Install Node Pods on Control Plane.
Enter the Namespace. The default value is csi-<array>.
Click on Generate YAML.
A manifest file, values.yaml will be generated and downloaded.
A section Run the following commands to install will be displayed.
Run the commands displayed to install Dell CSI Driver and Modules using the generated manifest file.

Installation Using Operator

Steps

Installation Wizard

Mon, 01 Jan 0001 00:00:00 +0000

CSM Installation Wizard Support Matrix Click Here

Generate Manifest File

Open the Installation Wizard.
Select the Installation Type as Helm/Operator.
Select the Array.
Enter the Image Repository. The default value is dellemc.
Select the CSM Version.
Select the modules for installation. If there are module specific inputs, enter their values.
If needed, modify the Controller Pods Count.
If needed, select Install Controller Pods on Control Plane and/or Install Node Pods on Control Plane.
Enter the Namespace. The default value is csi-<array>.
Click on Generate YAML.
A manifest file, values.yaml will be generated and downloaded.
A section Run the following commands to install will be displayed.
Run the commands displayed to install Dell CSI Driver and Modules using the generated manifest file.

Installation Using Operator

Steps

Installation Wizard

Mon, 01 Jan 0001 00:00:00 +0000

CSM Installation Wizard Support Matrix Click Here

Generate Manifest File

Open the Installation Wizard.
Select the Installation Type as Helm/Operator.
Select the Array.
Enter the Image Repository. The default value is dellemc.
Select the CSM Version.
Select the modules for installation. If there are module specific inputs, enter their values.
If needed, modify the Controller Pods Count.
If needed, select Install Controller Pods on Control Plane and/or Install Node Pods on Control Plane.
Enter the Namespace. The default value is csi-<array>.
Click on Generate YAML.
A manifest file, values.yaml will be generated and downloaded.
A section Run the following commands to install will be displayed.
Run the commands displayed to install Dell CSI Driver and Modules using the generated manifest file.

Installation Using Operator

Steps

Installation Wizard

Mon, 01 Jan 0001 00:00:00 +0000

CSM Installation Wizard Support Matrix Click Here

Generate Manifest File

Open the Installation Wizard.
Select the Installation Type as Helm/Operator.
Select the Array.
Enter the Image Repository. The default value is dellemc.
Select the CSM Version.
Select the modules for installation. If there are module specific inputs, enter their values.
If needed, modify the Controller Pods Count.
If needed, select Install Controller Pods on Control Plane and/or Install Node Pods on Control Plane.
Enter the Namespace. The default value is csi-<array>.
Click on Generate YAML.
A manifest file, values.yaml will be generated and downloaded.
A section Run the following commands to install will be displayed.
Run the commands displayed to install Dell CSI Driver and Modules using the generated manifest file.

Installation Using Operator

Steps

Installation Wizard

Mon, 01 Jan 0001 00:00:00 +0000

CSM Installation Wizard Support Matrix Click Here

Generate Manifest File

Open the Installation Wizard.
Select the Installation Type as Helm/Operator.
Select the Array.
Enter the Image Repository. The default value is dellemc.
Select the CSM Version.
Select the modules for installation. If there are module specific inputs, enter their values.
If needed, modify the Controller Pods Count.
If needed, select Install Controller Pods on Control Plane and/or Install Node Pods on Control Plane.
Enter the Namespace. The default value is csi-<array>.
Click on Generate YAML.
A manifest file, values.yaml will be generated and downloaded.
A section Run the following commands to install will be displayed.
Run the commands displayed to install Dell CSI Driver and Modules using the generated manifest file.

Installation Using Operator

Steps

Installation Wizard

Mon, 01 Jan 0001 00:00:00 +0000

CSM Installation Wizard Support Matrix Click Here

Generate Manifest File

Open the Installation Wizard.
Select the Installation Type as Helm/Operator.
Select the Array.
Enter the Image Repository. The default value is dellemc.
Select the CSM Version.
Select the modules for installation. If there are module specific inputs, enter their values.
If needed, modify the Controller Pods Count.
If needed, select Install Controller Pods on Control Plane and/or Install Node Pods on Control Plane.
Enter the Namespace. The default value is csi-<array>.
Click on Generate YAML.
A manifest file, values.yaml will be generated and downloaded.
A section Run the following commands to install will be displayed.
Run the commands displayed to install Dell CSI Driver and Modules using the generated manifest file.

Installation Using Operator

Steps

Installation Wizard

Mon, 01 Jan 0001 00:00:00 +0000

CSM Installation Wizard Support Matrix Click Here

Generate Manifest File

Open the Installation Wizard.
Select the Installation Type as Helm/Operator.
Select the Array.
Enter the Image Repository. The default value is dellemc.
Select the CSM Version.
Select the modules for installation. If there are module specific inputs, enter their values.
If needed, modify the Controller Pods Count.
If needed, select Install Controller Pods on Control Plane and/or Install Node Pods on Control Plane.
Enter the Namespace. The default value is csi-<array>.
Click on Generate YAML.
A manifest file, values.yaml will be generated and downloaded.
A section Run the following commands to install will be displayed.
Run the commands displayed to install Dell CSI Driver and Modules using the generated manifest file.

Installation Using Operator

Steps

Installation Wizard

Mon, 01 Jan 0001 00:00:00 +0000

CSM Installation Wizard Support Matrix Click Here

Generate Manifest File

Open the Installation Wizard.
Select the Installation Type as Helm/Operator.
Select the Array.
Enter the Image Repository. The default value is dellemc.
Select the CSM Version.
Select the modules for installation. If there are module specific inputs, enter their values.
If needed, modify the Controller Pods Count.
If needed, select Install Controller Pods on Control Plane and/or Install Node Pods on Control Plane.
Enter the Namespace. The default value is csi-<array>.
Click on Generate YAML.
A manifest file, values.yaml will be generated and downloaded.
A section Run the following commands to install will be displayed.
Run the commands displayed to install Dell CSI Driver and Modules using the generated manifest file.

Installation Using Operator

Steps

Installation Wizard

Mon, 01 Jan 0001 00:00:00 +0000

CSM Installation Wizard Support Matrix Click Here

Generate Manifest File

Open the Installation Wizard.
Select the Installation Type as Helm/Operator.
Select the Array.
Enter the Image Repository. The default value is dellemc.
Select the CSM Version.
Select the modules for installation. If there are module specific inputs, enter their values.
If needed, modify the Controller Pods Count.
If needed, select Install Controller Pods on Control Plane and/or Install Node Pods on Control Plane.
Enter the Namespace. The default value is csi-<array>.
Click on Generate YAML.
A manifest file, values.yaml will be generated and downloaded.
A section Run the following commands to install will be displayed.
Run the commands displayed to install Dell CSI Driver and Modules using the generated manifest file.

Installation Using Operator

Steps

Installation Wizard

Mon, 01 Jan 0001 00:00:00 +0000

CSM Installation Wizard Support Matrix Click Here

Generate Manifest File

Open the Installation Wizard.
Select the Installation Type as Helm/Operator.
Select the Array.
Enter the Image Repository. The default value is dellemc.
Select the CSM Version.
Select the modules for installation. If there are module specific inputs, enter their values.
If needed, modify the Controller Pods Count.
If needed, select Install Controller Pods on Control Plane and/or Install Node Pods on Control Plane.
Enter the Namespace. The default value is csi-<array>.
Click on Generate YAML.
A manifest file, values.yaml will be generated and downloaded.
A section Run the following commands to install will be displayed.
Run the commands displayed to install Dell CSI Driver and Modules using the generated manifest file.

Installation Using Operator

Steps

Observability

Mon, 01 Jan 0001 00:00:00 +0000

The Observability module installed by the Dell CSM Operator can be updated like any Kubernetes resource.

Modifying the existing driver and module installation directly via kubectl edit
```
kubectl get <driver-object> -n <driver-namespace>
```
For example - If the CSI driver is installed then run this command to get the object name

Observability

Mon, 01 Jan 0001 00:00:00 +0000

The Observability module installed by the Dell CSM Operator can be updated like any Kubernetes resource.

Modifying the existing driver and module installation directly via kubectl edit
```
kubectl get <driver-object> -n <driver-namespace>
```
For example - If the CSI PowerScale driver is installed then run this command to get the object name

Observability

Mon, 01 Jan 0001 00:00:00 +0000

The Observability module installed by the Dell CSM Operator can be updated like any Kubernetes resource.

Modifying the existing driver and module installation directly via kubectl edit
```
kubectl get <driver-object> -n <driver-namespace>
```
For example - If the CSI PowerScale driver is installed then run this command to get the object name

Observability

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The CSM Observability module for supported Dell CSI Drivers can be installed via the Dell CSM Operator. Dell CSM Operator will deploy CSM Observability, including topology service, Otel collector, and metrics services.

Prerequisites

Create a namespace karavi

Powerflex

Mon, 01 Jan 0001 00:00:00 +0000

Copy only the deployed CSI driver entities to the Observability namespace

PowerFlex
1. Copy the config Secret from the CSI PowerFlex namespace into the Container Storage Modules Observability namespace:
```
kubectl get secret vxflexos-config -n [CSI_DRIVER_NAMESPACE] -o yaml | sed 's/namespace: [CSI_DRIVER_NAMESPACE]/namespace: [CSM_NAMESPACE]/' | kubectl create -f -
```
  If the CSI driver secret name is not the default vxflexos-config, please use the following command to copy secret:

Powerflex

Mon, 01 Jan 0001 00:00:00 +0000

Copy only the deployed CSI driver entities to the Observability namespace

PowerFlex
1. Copy the config Secret from the CSI PowerFlex namespace into the Container Storage Modules Observability namespace:
```
kubectl get secret vxflexos-config -n [CSI_DRIVER_NAMESPACE] -o yaml | sed 's/namespace: [CSI_DRIVER_NAMESPACE]/namespace: [CSM_NAMESPACE]/' | kubectl create -f -
```
  If the CSI driver secret name is not the default vxflexos-config, please use the following command to copy secret:

Powerflex

Mon, 01 Jan 0001 00:00:00 +0000

Copy only the deployed CSI driver entities to the Observability namespace

PowerFlex
1. Copy the config Secret from the CSI PowerFlex namespace into the Container Storage Modules Observability namespace:
```
kubectl get secret vxflexos-config -n [CSI_DRIVER_NAMESPACE] -o yaml | sed 's/namespace: [CSI_DRIVER_NAMESPACE]/namespace: [CSM_NAMESPACE]/' | kubectl create -f -
```
  If the CSI driver secret name is not the default vxflexos-config, please use the following command to copy secret:

Test PowerFlex CSI Driver

Mon, 01 Jan 0001 00:00:00 +0000

This section provides multiple methods to test driver functionality in your environment.

Note: To run the test for CSI Driver for PowerFlex, install Helm 3.

Test deploying a simple pod with PowerFlex storage

Test the deployment workflow of a simple pod on PowerFlex storage.

PowerFlex

Mon, 01 Jan 0001 00:00:00 +0000

Symptoms	Prevention, Resolution or Workaround
The installation fails with the following error message: `Node xxx does not have the SDC installed`	Install the PowerFlex SDC on listed nodes. The SDC must be installed on all the nodes that need to pull an image of the driver.
When you run the command `kubectl describe pods vxflexos-controller-* –n vxflexos`, the system indicates that the driver image could not be loaded.	- If on Kubernetes, edit the `daemon.json` file found in the registry location and add `{ "insecure-registries" :[ "hostname.cloudapp.net:5000" ] }` - If on OpenShift, run the command `oc edit image.config.openshift.io/cluster` and add registries to yaml file that is displayed when you run the command.
The `kubectl logs -n vxflexos vxflexos-controller-* driver` logs show that the driver is not authenticated.	Check the username, password, and the gateway IP address for the PowerFlex system.
The `kubectl logs vxflexos-controller-* -n vxflexos driver` logs show that the system ID is incorrect.	Use the `get_vxflexos_info.sh` to find the correct system ID.
The `kubectl logs vxflexos-controller-* -n vxflexos driver` logs show that the system ID is incorrect.	Use the `get_vxflexos_info.sh` to find the correct system ID. Add the system ID to `myvalues.yaml` script.
CreateVolume error System is not configured in the driver	Powerflex name if used for systemID in StorageClass ensure same name is also used in array config systemID
Defcontext mount option seems to be ignored, volumes still are not being labeled correctly.	Ensure SElinux is enabled on a worker node, and ensure your container run time manager is properly configured to be utilized with SElinux.
Mount options that interact with SElinux are not working (like defcontext).	Check that your container orchestrator is properly configured to work with SElinux.
The `kubectl logs -n vxflexos vxflexos-controller-* driver` logs show `x509: certificate signed by unknown authority`	A self assigned certificate is used for PowerFlex array. See certificate validation for PowerFlex Gateway
When you run the command `kubectl apply -f snapclass-v1.yaml`, you get the error `error: unable to recognize "snapclass-v1.yaml": no matches for kind "VolumeSnapshotClass" in version "snapshot.storage.k8s.io/v1"`	Check to make sure that the v1 snapshotter CRDs are installed, and not the v1beta1 CRDs, which are no longer supported.
The controller pod is stuck and producing errors such as" `Failed to watch v1.VolumeSnapshotContent: failed to list v1.VolumeSnapshotContent: the server could not find the requested resource (get volumesnapshotcontents.snapshot.storage.k8s.io)`	Make sure that v1 snapshotter CRDs and v1 snapclass are installed, and not v1beta1, which is no longer supported.
Driver install or upgrade fails because of an incompatible Kubernetes version, even though the version seems to be within the range of compatibility. For example: `Error: UPGRADE FAILED: chart requires kubeVersion: >= 1.21.0 <= 1.28.0 which is incompatible with Kubernetes V1.21.11-mirantis-1`	If you are using an extended Kubernetes version, see the helm Chart at `helm/csi-vxflexos/Chart.yaml` and use the alternate `kubeVersion` check that is provided in the comments. Note: this is not meant to be used to enable the use of pre-release alpha and beta versions, which is not supported.
Volume metrics are missing	Enable Volume Health Monitoring
When a node goes down, the block volumes attached to the node cannot be attached to another node	This is a known issue and has been reported at https://github.com/kubernetes-csi/external-attacher/issues/215. Workaround: 1. Force delete the pod running on the node that went down 2. Delete the volumeattachment to the node that went down. Now the volume can be attached to the new node.
CSI-PowerFlex volumes cannot mount; are being recognized as multipath devices	CSI-PowerFlex does not support multipath; to fix: 1. Remove any multipath mapping involving a powerflex volume with `multipath -f <powerflex volume>` 2. Blacklist CSI-PowerFlex volumes in multipath config file
When attempting a driver upgrade, you see: `spec.fsGroupPolicy: Invalid value: "xxx": field is immutable`	You cannot upgrade between drivers with different fsGroupPolicies. See upgrade documentation for more details
When accessing ROX mode PVC in OpenShift where the worker nodes are non-root user, you see: `Permission denied` while accessing the PVC mount location from the pod.	Set the `securityContext` for ROX mode PVC pod as below, as it defines privileges for the pods or containers. securityContext: runAsUser: 0 runAsGroup: 0
When a cluster node goes down, the block volumes attached to the node cannot be attached to another node.	This is a known issue reported at kubernetes-csi/external-attacher#215. Workaround: 1. Force delete the pod running on the node that went down. 2. Delete the pod’s persistent volume attachment on the node that went down. Now the volume can be attached to the new node.
A CSI ephemeral pod may not get created in OpenShift 4.13 and fail with the error `"error when creating pod: the pod uses an inline volume provided by CSIDriver csi-vxflexos.dellemc.com, and the namespace has a pod security enforcement level that is lower than privileged."`	This issue occurs because OpenShift 4.13 introduced the CSI Volume Admission plugin to restrict the use of a CSI driver capable of provisioning CSI ephemeral volumes during pod admission. Therefore, an additional label `security.openshift.io/csi-ephemeral-volume-profile` in csidriver.yaml file with the required security profile value should be provided. Follow OpenShift 4.13 documentation for CSI Ephemeral Volumes for more information.
Standby controller pod is in crashloopbackoff state	Scale down the replica count of the controller pod’s deployment to 1 using `kubectl scale deployment <deployment_name> --replicas=1 -n <driver_namespace>`
CSM object `vxflexos` is in failed state and CSI-Powerflex driver is not in running state	Verify the secret name: `kubectl get secret -n <namespace_name>` it should be in `<CR-name>-config` format. 1. Retrieve the existing secret: `kubectl get secret old-secret-name -n <namespace_name> -o yaml > secret.yaml` 2. Edit the secret.yaml file: Change metadata.name to -Config 3. Apply the new secret: `kubectl apply -f secret.yaml` 4. Delete the old secret: kubectl delete secret old-secret-name

Test PowerFlex CSI Driver

Mon, 01 Jan 0001 00:00:00 +0000

This section provides multiple methods to test driver functionality in your environment.

Note: To run the test for CSI Driver for PowerFlex, install Helm 3.

Test deploying a simple pod with PowerFlex storage

Test the deployment workflow of a simple pod on PowerFlex storage.

PowerFlex

Mon, 01 Jan 0001 00:00:00 +0000

Symptoms	Prevention, Resolution or Workaround
The installation fails with the following error message: `Node xxx does not have the SDC installed`	Install the PowerFlex SDC on listed nodes. The SDC must be installed on all the nodes that need to pull an image of the driver.
When you run the command `kubectl describe pods vxflexos-controller-* –n vxflexos`, the system indicates that the driver image could not be loaded.	- If on Kubernetes, edit the `daemon.json` file found in the registry location and add `{ "insecure-registries" :[ "hostname.cloudapp.net:5000" ] }` - If on OpenShift, run the command `oc edit image.config.openshift.io/cluster` and add registries to yaml file that is displayed when you run the command.
The `kubectl logs -n vxflexos vxflexos-controller-* driver` logs show that the driver is not authenticated.	Check the username, password, and the gateway IP address for the PowerFlex system.
The `kubectl logs vxflexos-controller-* -n vxflexos driver` logs show that the system ID is incorrect.	Use the `get_vxflexos_info.sh` to find the correct system ID.
The `kubectl logs vxflexos-controller-* -n vxflexos driver` logs show that the system ID is incorrect.	Use the `get_vxflexos_info.sh` to find the correct system ID. Add the system ID to `myvalues.yaml` script.
CreateVolume error System is not configured in the driver	Powerflex name if used for systemID in StorageClass ensure same name is also used in array config systemID
Defcontext mount option seems to be ignored, volumes still are not being labeled correctly.	Ensure SElinux is enabled on a worker node, and ensure your container run time manager is properly configured to be utilized with SElinux.
Mount options that interact with SElinux are not working (like defcontext).	Check that your container orchestrator is properly configured to work with SElinux.
The `kubectl logs -n vxflexos vxflexos-controller-* driver` logs show `x509: certificate signed by unknown authority`	A self assigned certificate is used for PowerFlex array. See certificate validation for PowerFlex Gateway
When you run the command `kubectl apply -f snapclass-v1.yaml`, you get the error `error: unable to recognize "snapclass-v1.yaml": no matches for kind "VolumeSnapshotClass" in version "snapshot.storage.k8s.io/v1"`	Check to make sure that the v1 snapshotter CRDs are installed, and not the v1beta1 CRDs, which are no longer supported.
The controller pod is stuck and producing errors such as" `Failed to watch v1.VolumeSnapshotContent: failed to list v1.VolumeSnapshotContent: the server could not find the requested resource (get volumesnapshotcontents.snapshot.storage.k8s.io)`	Make sure that v1 snapshotter CRDs and v1 snapclass are installed, and not v1beta1, which is no longer supported.
Driver install or upgrade fails because of an incompatible Kubernetes version, even though the version seems to be within the range of compatibility. For example: `Error: UPGRADE FAILED: chart requires kubeVersion: >= 1.21.0 <= 1.28.0 which is incompatible with Kubernetes V1.21.11-mirantis-1`	If you are using an extended Kubernetes version, see the helm Chart at `helm/csi-vxflexos/Chart.yaml` and use the alternate `kubeVersion` check that is provided in the comments. Note: this is not meant to be used to enable the use of pre-release alpha and beta versions, which is not supported.
Volume metrics are missing	Enable Volume Health Monitoring
When a node goes down, the block volumes attached to the node cannot be attached to another node	This is a known issue and has been reported at https://github.com/kubernetes-csi/external-attacher/issues/215. Workaround: 1. Force delete the pod running on the node that went down 2. Delete the volumeattachment to the node that went down. Now the volume can be attached to the new node.
CSI-PowerFlex volumes cannot mount; are being recognized as multipath devices	CSI-PowerFlex does not support multipath; to fix: 1. Remove any multipath mapping involving a powerflex volume with `multipath -f <powerflex volume>` 2. Blacklist CSI-PowerFlex volumes in multipath config file
When attempting a driver upgrade, you see: `spec.fsGroupPolicy: Invalid value: "xxx": field is immutable`	You cannot upgrade between drivers with different fsGroupPolicies. See upgrade documentation for more details
When accessing ROX mode PVC in OpenShift where the worker nodes are non-root user, you see: `Permission denied` while accessing the PVC mount location from the pod.	Set the `securityContext` for ROX mode PVC pod as below, as it defines privileges for the pods or containers. securityContext: runAsUser: 0 runAsGroup: 0
When a cluster node goes down, the block volumes attached to the node cannot be attached to another node.	This is a known issue reported at kubernetes-csi/external-attacher#215. Workaround: 1. Force delete the pod running on the node that went down. 2. Delete the pod’s persistent volume attachment on the node that went down. Now the volume can be attached to the new node.
A CSI ephemeral pod may not get created in OpenShift 4.13 and fail with the error `"error when creating pod: the pod uses an inline volume provided by CSIDriver csi-vxflexos.dellemc.com, and the namespace has a pod security enforcement level that is lower than privileged."`	This issue occurs because OpenShift 4.13 introduced the CSI Volume Admission plugin to restrict the use of a CSI driver capable of provisioning CSI ephemeral volumes during pod admission. Therefore, an additional label `security.openshift.io/csi-ephemeral-volume-profile` in csidriver.yaml file with the required security profile value should be provided. Follow OpenShift 4.13 documentation for CSI Ephemeral Volumes for more information.
Standby controller pod is in crashloopbackoff state	Scale down the replica count of the controller pod’s deployment to 1 using `kubectl scale deployment <deployment_name> --replicas=1 -n <driver_namespace>`
CSM object `vxflexos` is in failed state and CSI-Powerflex driver is not in running state	Verify the secret name: `kubectl get secret -n <namespace_name>` it should be in `<CR-name>-config` format. 1. Retrieve the existing secret: `kubectl get secret old-secret-name -n <namespace_name> -o yaml > secret.yaml` 2. Edit the secret.yaml file: Change metadata.name to -Config 3. Apply the new secret: `kubectl apply -f secret.yaml` 4. Delete the old secret: kubectl delete secret old-secret-name

Test PowerFlex CSI Driver

Mon, 01 Jan 0001 00:00:00 +0000

This section provides multiple methods to test driver functionality in your environment.

Note: To run the test for CSI Driver for PowerFlex, install Helm 3.

Test deploying a simple pod with PowerFlex storage

Test the deployment workflow of a simple pod on PowerFlex storage.

PowerFlex

Mon, 01 Jan 0001 00:00:00 +0000

Symptoms	Prevention, Resolution or Workaround
The installation fails with the following error message: `Node xxx does not have the SDC installed`	Install the PowerFlex SDC on listed nodes. The SDC must be installed on all the nodes that need to pull an image of the driver.
When you run the command `kubectl describe pods vxflexos-controller-* –n vxflexos`, the system indicates that the driver image could not be loaded.	- If on Kubernetes, edit the `daemon.json` file found in the registry location and add `{ "insecure-registries" :[ "hostname.cloudapp.net:5000" ] }` - If on OpenShift, run the command `oc edit image.config.openshift.io/cluster` and add registries to yaml file that is displayed when you run the command.
The `kubectl logs -n vxflexos vxflexos-controller-* driver` logs show that the driver is not authenticated.	Check the username, password, and the gateway IP address for the PowerFlex system.
The `kubectl logs vxflexos-controller-* -n vxflexos driver` logs show that the system ID is incorrect.	Use the `get_vxflexos_info.sh` to find the correct system ID.
The `kubectl logs vxflexos-controller-* -n vxflexos driver` logs show that the system ID is incorrect.	Use the `get_vxflexos_info.sh` to find the correct system ID. Add the system ID to `myvalues.yaml` script.
CreateVolume error System is not configured in the driver	Powerflex name if used for systemID in StorageClass ensure same name is also used in array config systemID
Defcontext mount option seems to be ignored, volumes still are not being labeled correctly.	Ensure SElinux is enabled on a worker node, and ensure your container run time manager is properly configured to be utilized with SElinux.
Mount options that interact with SElinux are not working (like defcontext).	Check that your container orchestrator is properly configured to work with SElinux.
The `kubectl logs -n vxflexos vxflexos-controller-* driver` logs show `x509: certificate signed by unknown authority`	A self assigned certificate is used for PowerFlex array. See certificate validation for PowerFlex Gateway
When you run the command `kubectl apply -f snapclass-v1.yaml`, you get the error `error: unable to recognize "snapclass-v1.yaml": no matches for kind "VolumeSnapshotClass" in version "snapshot.storage.k8s.io/v1"`	Check to make sure that the v1 snapshotter CRDs are installed, and not the v1beta1 CRDs, which are no longer supported.
The controller pod is stuck and producing errors such as" `Failed to watch v1.VolumeSnapshotContent: failed to list v1.VolumeSnapshotContent: the server could not find the requested resource (get volumesnapshotcontents.snapshot.storage.k8s.io)`	Make sure that v1 snapshotter CRDs and v1 snapclass are installed, and not v1beta1, which is no longer supported.
Driver install or upgrade fails because of an incompatible Kubernetes version, even though the version seems to be within the range of compatibility. For example: `Error: UPGRADE FAILED: chart requires kubeVersion: >= 1.21.0 <= 1.28.0 which is incompatible with Kubernetes V1.21.11-mirantis-1`	If you are using an extended Kubernetes version, see the helm Chart at `helm/csi-vxflexos/Chart.yaml` and use the alternate `kubeVersion` check that is provided in the comments. Note: this is not meant to be used to enable the use of pre-release alpha and beta versions, which is not supported.
Volume metrics are missing	Enable Volume Health Monitoring
When a node goes down, the block volumes attached to the node cannot be attached to another node	This is a known issue and has been reported at https://github.com/kubernetes-csi/external-attacher/issues/215. Workaround: 1. Force delete the pod running on the node that went down 2. Delete the volumeattachment to the node that went down. Now the volume can be attached to the new node.
CSI-PowerFlex volumes cannot mount; are being recognized as multipath devices	CSI-PowerFlex does not support multipath; to fix: 1. Remove any multipath mapping involving a powerflex volume with `multipath -f <powerflex volume>` 2. Blacklist CSI-PowerFlex volumes in multipath config file
When attempting a driver upgrade, you see: `spec.fsGroupPolicy: Invalid value: "xxx": field is immutable`	You cannot upgrade between drivers with different fsGroupPolicies. See upgrade documentation for more details
When accessing ROX mode PVC in OpenShift where the worker nodes are non-root user, you see: `Permission denied` while accessing the PVC mount location from the pod.	Set the `securityContext` for ROX mode PVC pod as below, as it defines privileges for the pods or containers. securityContext: runAsUser: 0 runAsGroup: 0
When a cluster node goes down, the block volumes attached to the node cannot be attached to another node.	This is a known issue reported at kubernetes-csi/external-attacher#215. Workaround: 1. Force delete the pod running on the node that went down. 2. Delete the pod’s persistent volume attachment on the node that went down. Now the volume can be attached to the new node.
A CSI ephemeral pod may not get created in OpenShift 4.13 and fail with the error `"error when creating pod: the pod uses an inline volume provided by CSIDriver csi-vxflexos.dellemc.com, and the namespace has a pod security enforcement level that is lower than privileged."`	This issue occurs because OpenShift 4.13 introduced the CSI Volume Admission plugin to restrict the use of a CSI driver capable of provisioning CSI ephemeral volumes during pod admission. Therefore, an additional label `security.openshift.io/csi-ephemeral-volume-profile` in csidriver.yaml file with the required security profile value should be provided. Follow OpenShift 4.13 documentation for CSI Ephemeral Volumes for more information.
Standby controller pod is in crashloopbackoff state	Scale down the replica count of the controller pod’s deployment to 1 using `kubectl scale deployment <deployment_name> --replicas=1 -n <driver_namespace>`
CSM object `vxflexos` is in failed state and CSI-Powerflex driver is not in running state	Verify the secret name: `kubectl get secret -n <namespace_name>` it should be in `<CR-name>-config` format. 1. Retrieve the existing secret: `kubectl get secret old-secret-name -n <namespace_name> -o yaml > secret.yaml` 2. Edit the secret.yaml file: Change metadata.name to -Config 3. Apply the new secret: `kubectl apply -f secret.yaml` 4. Delete the old secret: kubectl delete secret old-secret-name

Test PowerFlex CSI Driver

Mon, 01 Jan 0001 00:00:00 +0000

This section provides multiple methods to test driver functionality in your environment.

Note: To run the test for CSI Driver for Dell PowerFlex, install Helm 3.

Test deploying a simple pod with PowerFlex storage

Test the deployment workflow of a simple pod on PowerFlex storage.

PowerFlex

Mon, 01 Jan 0001 00:00:00 +0000

Symptoms	Prevention, Resolution or Workaround
The installation fails with the following error message: `Node xxx does not have the SDC installed`	Install the PowerFlex SDC on listed nodes. The SDC must be installed on all the nodes that need to pull an image of the driver.
When you run the command `kubectl describe pods vxflexos-controller-* –n vxflexos`, the system indicates that the driver image could not be loaded.	- If on Kubernetes, edit the `daemon.json` file found in the registry location and add `{ "insecure-registries" :[ "hostname.cloudapp.net:5000" ] }` - If on OpenShift, run the command `oc edit image.config.openshift.io/cluster` and add registries to yaml file that is displayed when you run the command.
The `kubectl logs -n vxflexos vxflexos-controller-* driver` logs show that the driver is not authenticated.	Check the username, password, and the gateway IP address for the PowerFlex system.
The `kubectl logs vxflexos-controller-* -n vxflexos driver` logs show that the system ID is incorrect.	Use the `get_vxflexos_info.sh` to find the correct system ID.
The `kubectl logs vxflexos-controller-* -n vxflexos driver` logs show that the system ID is incorrect.	Use the `get_vxflexos_info.sh` to find the correct system ID. Add the system ID to `myvalues.yaml` script.
CreateVolume error System is not configured in the driver	Powerflex name if used for systemID in StorageClass ensure same name is also used in array config systemID
Defcontext mount option seems to be ignored, volumes still are not being labeled correctly.	Ensure SElinux is enabled on a worker node, and ensure your container run time manager is properly configured to be utilized with SElinux.
Mount options that interact with SElinux are not working (like defcontext).	Check that your container orchestrator is properly configured to work with SElinux.
The `kubectl logs -n vxflexos vxflexos-controller-* driver` logs show `x509: certificate signed by unknown authority`	A self assigned certificate is used for PowerFlex array. See certificate validation for PowerFlex Gateway
When you run the command `kubectl apply -f snapclass-v1.yaml`, you get the error `error: unable to recognize "snapclass-v1.yaml": no matches for kind "VolumeSnapshotClass" in version "snapshot.storage.k8s.io/v1"`	Check to make sure that the v1 snapshotter CRDs are installed, and not the v1beta1 CRDs, which are no longer supported.
The controller pod is stuck and producing errors such as" `Failed to watch v1.VolumeSnapshotContent: failed to list v1.VolumeSnapshotContent: the server could not find the requested resource (get volumesnapshotcontents.snapshot.storage.k8s.io)`	Make sure that v1 snapshotter CRDs and v1 snapclass are installed, and not v1beta1, which is no longer supported.
Driver install or upgrade fails because of an incompatible Kubernetes version, even though the version seems to be within the range of compatibility. For example: `Error: UPGRADE FAILED: chart requires kubeVersion: >= 1.21.0 <= 1.28.0 which is incompatible with Kubernetes V1.21.11-mirantis-1`	If you are using an extended Kubernetes version, see the helm Chart at `helm/csi-vxflexos/Chart.yaml` and use the alternate `kubeVersion` check that is provided in the comments. Note: this is not meant to be used to enable the use of pre-release alpha and beta versions, which is not supported.
Volume metrics are missing	Enable Volume Health Monitoring
When a node goes down, the block volumes attached to the node cannot be attached to another node	This is a known issue and has been reported at https://github.com/kubernetes-csi/external-attacher/issues/215. Workaround: 1. Force delete the pod running on the node that went down 2. Delete the volumeattachment to the node that went down. Now the volume can be attached to the new node.
CSI-PowerFlex volumes cannot mount; are being recognized as multipath devices	CSI-PowerFlex does not support multipath; to fix: 1. Remove any multipath mapping involving a powerflex volume with `multipath -f <powerflex volume>` 2. Blacklist CSI-PowerFlex volumes in multipath config file
When attempting a driver upgrade, you see: `spec.fsGroupPolicy: Invalid value: "xxx": field is immutable`	You cannot upgrade between drivers with different fsGroupPolicies. See upgrade documentation for more details
When accessing ROX mode PVC in OpenShift where the worker nodes are non-root user, you see: `Permission denied` while accessing the PVC mount location from the pod.	Set the `securityContext` for ROX mode PVC pod as below, as it defines privileges for the pods or containers. securityContext: runAsUser: 0 runAsGroup: 0
When a cluster node goes down, the block volumes attached to the node cannot be attached to another node.	This is a known issue reported at kubernetes-csi/external-attacher#215. Workaround: 1. Force delete the pod running on the node that went down. 2. Delete the pod’s persistent volume attachment on the node that went down. Now the volume can be attached to the new node.
A CSI ephemeral pod may not get created in OpenShift 4.13 and fail with the error `"error when creating pod: the pod uses an inline volume provided by CSIDriver csi-vxflexos.dellemc.com, and the namespace has a pod security enforcement level that is lower than privileged."`	This issue occurs because OpenShift 4.13 introduced the CSI Volume Admission plugin to restrict the use of a CSI driver capable of provisioning CSI ephemeral volumes during pod admission. Therefore, an additional label `security.openshift.io/csi-ephemeral-volume-profile` in csidriver.yaml file with the required security profile value should be provided. Follow OpenShift 4.13 documentation for CSI Ephemeral Volumes for more information.
Standby controller pod is in crashloopbackoff state	Scale down the replica count of the controller pod’s deployment to 1 using `kubectl scale deployment <deployment_name> --replicas=1 -n <driver_namespace>`
CSM object `vxflexos` is in failed state and CSI-Powerflex driver is not in running state	Verify the secret name: `kubectl get secret -n <namespace_name>` it should be in `<CR-name>-config` format. 1. Retrieve the existing secret: `kubectl get secret old-secret-name -n <namespace_name> -o yaml > secret.yaml` 2. Edit the secret.yaml file: Change metadata.name to -Config 3. Apply the new secret: `kubectl apply -f secret.yaml` 4. Delete the old secret: kubectl delete secret old-secret-name

PowerFlex

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The CSI Driver for Dell PowerFlex can be installed via the Dell CSM Operator. To deploy the Operator, follow the instructions available here.

Note that the deployment of the driver using the operator does not use any Helm charts and the installation and configuration parameters will be slightly different from the one specified via the Helm installer.

Listing installed drivers

To query for all Dell CSI drivers installed with the ContainerStorageModule CRD use the following command:

PowerFlex

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The CSI Driver for Dell PowerFlex can be deployed by using the provided Helm v3 charts and installation scripts on both Kubernetes and OpenShift platforms. For more detailed information on the installation scripts, review the script documentation.

Prerequisites

The following are requirements that must be met before installing the CSI Driver for Dell PowerFlex:

Test PowerMax CSI Driver

Mon, 01 Jan 0001 00:00:00 +0000

This section provides multiple methods to test driver functionality in your environment. The tests are validated using bash as the default shell.

Note: To run the test for CSI Driver for PowerMax, install Helm 3.

The csi-powermax repository includes examples of how you can use CSI Driver for PowerMax. The shell scripts are used to automate the installation and uninstallation of helm charts for the creation of Pods with a different number of volumes in a given namespace using the storageclass provided. To test the installation of the CSI driver, perform these tests:

PowerMax

Mon, 01 Jan 0001 00:00:00 +0000

Symptoms	Prevention, Resolution or Workaround
`kubectl describe pod powermax-controller-<xyz> –n <namespace>` indicates that the driver image could not be loaded	You may need to put an insecure-registries entry in `/etc/docker/daemon.json` or log in to the docker registry
`kubectl logs powermax-controller-<xyz> –n <namespace> driver` logs show that the driver cannot authenticate	Check your secret’s username and password
`kubectl logs powermax-controller-<xyz> –n <namespace> driver` logs show that the driver failed to connect to the U4P because it could not verify the certificates	Check the powermax-certs secret and ensure it is not empty or it has the valid certificates
Driver install or upgrade fails because of an incompatible Kubernetes version, even though the version seems to be within the range of compatibility. For example: Error: UPGRADE FAILED: chart requires kubeVersion: >= 1.23.0 < 1.27.0 which is incompatible with Kubernetes V1.23.11-mirantis-1	If you are using an extended Kubernetes version, please see the helm Chart and use the alternate kubeVersion check that is provided in the comments. Please note that this is not meant to be used to enable the use of pre-release alpha and beta versions, which are not supported.
When a node goes down, the block volumes attached to the node cannot be attached to another node	1. Force delete the pod running on the node that went down 2. Delete the volumeattachment to the node that went down. Now the volume can be attached to the new node.
When attempting a driver upgrade, you see: `spec.fsGroupPolicy: Invalid value: "xxx": field is immutable`	You cannot upgrade between drivers with different fsGroupPolicies. See upgrade documentation for more details
Ater the migration group is in “migrated” state but unable to move to “commit ready” state because the new paths are not being discovered on the cluster nodes.	Run the following commands manually on the cluster nodes `rescan-scsi-bus.sh  -i` `rescan-scsi-bus.sh  -a`
`Failed to fetch details for array: 000000000000. [Unauthorized]`"	Please make sure that correct encrypted username and password in secret files are used, also ensure whether the RBAC is enabled for the user
`Error looking up volume for idempotence check: Not Found` or `Get Volume step fails for: (000000000000) symID with error (Invalid Response from API)`	Make sure that Unisphere endpoint doesn’t end with front slash
`FailedPrecondition desc = no topology keys could be generate`	Make sure that FC or iSCSI connectivity to the arrays are proper
CreateHost failed with error `initiator is already part of different host.`	Update modifyHostName to true in values.yaml Or Remove the initiator from existing host
`kubectl logs powermax-controller-<xyz> –n <namespace>` driver logs says connection refused and the reverseproxy logs says “Failed to setup server.(secrets "secret-name" not found)”	Make sure the given secret exist on the cluster
nodestage is failing with error `Error invalid IQN Target iqn.EMC.0648.SE1F`	1. Update initiator name to full default name , ex: iqn.1993-08.org.debian:01:e9afae962192 2.Ensure that the iSCSI initiators are available on all the nodes where the driver node plugin will be installed and it should be full default name.
Volume mount is failing on few OS(ex:VMware Virtual Platform) during node publish with error `wrong fs type, bad option, bad superblock`	1. Check the multipath configuration(if enabled) 2. Edit Vm Advanced settings->hardware and add the param `disk.enableUUID=true` and reboot the node
Standby controller pod is in crashloopbackoff state	Scale down the replica count of the controller pod’s deployment to 1 using `kubectl scale deployment <deployment_name> --replicas=1 -n <driver_namespace>`
When running CSI-PowerMax with Replication in a multi-cluster configuration, the driver on the target cluster fails and the following error is seen in logs: `error="CSI reverseproxy service host or port not found, CSI reverseproxy not installed properly"`	The reverseproxy service needs to be created manually on the target cluster. Follow the instructions here to create it.
PVC creation is failing with error `A problem occurred modifying the storage group resource: Failed to create batch task(s): The maximum allowed devices for a storage group has been exceeded`. This is because of a hardware limit of 4k devices in a storage group.	Create a separate Storage Class with a new unique `ApplicationPrefix` parameter (such as `ApplicationPrefix: OCPX`) or add a new unique `StorageGroup` parameter (such as `StorageGroup: "custom_SG_1"`) to place the provisioned volumes in a new Storage Group.
Despite having `skipCertificateValidation` set to true, the driver fails to start with the following error appearing in the reverseproxy container logs: `[ERROR] Failed to run server: secrets "xxx" not found`	Upgrade PowerMax ReverseProxy image to v2.16.0 or remove the `certSecret` field from your secret/configmap

Test PowerMax CSI Driver

Mon, 01 Jan 0001 00:00:00 +0000

This section provides multiple methods to test driver functionality in your environment. The tests are validated using bash as the default shell.

Note: To run the test for CSI Driver for PowerMax, install Helm 3.

PowerMax

Mon, 01 Jan 0001 00:00:00 +0000

Symptoms	Prevention, Resolution or Workaround
`kubectl describe pod powermax-controller-<xyz> –n <namespace>` indicates that the driver image could not be loaded	You may need to put an insecure-registries entry in `/etc/docker/daemon.json` or log in to the docker registry
`kubectl logs powermax-controller-<xyz> –n <namespace> driver` logs show that the driver cannot authenticate	Check your secret’s username and password
`kubectl logs powermax-controller-<xyz> –n <namespace> driver` logs show that the driver failed to connect to the U4P because it could not verify the certificates	Check the powermax-certs secret and ensure it is not empty or it has the valid certificates
Driver install or upgrade fails because of an incompatible Kubernetes version, even though the version seems to be within the range of compatibility. For example: Error: UPGRADE FAILED: chart requires kubeVersion: >= 1.23.0 < 1.27.0 which is incompatible with Kubernetes V1.23.11-mirantis-1	If you are using an extended Kubernetes version, please see the helm Chart and use the alternate kubeVersion check that is provided in the comments. Please note that this is not meant to be used to enable the use of pre-release alpha and beta versions, which are not supported.
When a node goes down, the block volumes attached to the node cannot be attached to another node	1. Force delete the pod running on the node that went down 2. Delete the volumeattachment to the node that went down. Now the volume can be attached to the new node.
When attempting a driver upgrade, you see: `spec.fsGroupPolicy: Invalid value: "xxx": field is immutable`	You cannot upgrade between drivers with different fsGroupPolicies. See upgrade documentation for more details
Ater the migration group is in “migrated” state but unable to move to “commit ready” state because the new paths are not being discovered on the cluster nodes.	Run the following commands manually on the cluster nodes `rescan-scsi-bus.sh  -i` `rescan-scsi-bus.sh  -a`
`Failed to fetch details for array: 000000000000. [Unauthorized]`"	Please make sure that correct encrypted username and password in secret files are used, also ensure whether the RBAC is enabled for the user
`Error looking up volume for idempotence check: Not Found` or `Get Volume step fails for: (000000000000) symID with error (Invalid Response from API)`	Make sure that Unisphere endpoint doesn’t end with front slash
`FailedPrecondition desc = no topology keys could be generate`	Make sure that FC or iSCSI connectivity to the arrays are proper
CreateHost failed with error `initiator is already part of different host.`	Update modifyHostName to true in values.yaml Or Remove the initiator from existing host
`kubectl logs powermax-controller-<xyz> –n <namespace>` driver logs says connection refused and the reverseproxy logs says “Failed to setup server.(secrets "secret-name" not found)”	Make sure the given secret exist on the cluster
nodestage is failing with error `Error invalid IQN Target iqn.EMC.0648.SE1F`	1. Update initiator name to full default name , ex: iqn.1993-08.org.debian:01:e9afae962192 2.Ensure that the iSCSI initiators are available on all the nodes where the driver node plugin will be installed and it should be full default name.
Volume mount is failing on few OS(ex:VMware Virtual Platform) during node publish with error `wrong fs type, bad option, bad superblock`	1. Check the multipath configuration(if enabled) 2. Edit Vm Advanced settings->hardware and add the param `disk.enableUUID=true` and reboot the node
Standby controller pod is in crashloopbackoff state	Scale down the replica count of the controller pod’s deployment to 1 using `kubectl scale deployment <deployment_name> --replicas=1 -n <driver_namespace>`
When running CSI-PowerMax with Replication in a multi-cluster configuration, the driver on the target cluster fails and the following error is seen in logs: `error="CSI reverseproxy service host or port not found, CSI reverseproxy not installed properly"`	The reverseproxy service needs to be created manually on the target cluster. Follow the instructions here to create it.
PVC creation is failing with error `A problem occurred modifying the storage group resource: Failed to create batch task(s): The maximum allowed devices for a storage group has been exceeded`. This is because of a hardware limit of 4k devices in a storage group.	Create a separate Storage Class with a new unique `ApplicationPrefix` parameter (such as `ApplicationPrefix: OCPX`) or add a new unique `StorageGroup` parameter (such as `StorageGroup: "custom_SG_1"`) to place the provisioned volumes in a new Storage Group.

Test PowerMax CSI Driver

Mon, 01 Jan 0001 00:00:00 +0000

This section provides multiple methods to test driver functionality in your environment. The tests are validated using bash as the default shell.

Note: To run the test for CSI Driver for PowerMax, install Helm 3.

PowerMax

Mon, 01 Jan 0001 00:00:00 +0000

Symptoms	Prevention, Resolution or Workaround
`kubectl describe pod powermax-controller-<xyz> –n <namespace>` indicates that the driver image could not be loaded	You may need to put an insecure-registries entry in `/etc/docker/daemon.json` or log in to the docker registry
`kubectl logs powermax-controller-<xyz> –n <namespace> driver` logs show that the driver cannot authenticate	Check your secret’s username and password
`kubectl logs powermax-controller-<xyz> –n <namespace> driver` logs show that the driver failed to connect to the U4P because it could not verify the certificates	Check the powermax-certs secret and ensure it is not empty or it has the valid certificates
Driver install or upgrade fails because of an incompatible Kubernetes version, even though the version seems to be within the range of compatibility. For example: Error: UPGRADE FAILED: chart requires kubeVersion: >= 1.23.0 < 1.27.0 which is incompatible with Kubernetes V1.23.11-mirantis-1	If you are using an extended Kubernetes version, please see the helm Chart and use the alternate kubeVersion check that is provided in the comments. Please note that this is not meant to be used to enable the use of pre-release alpha and beta versions, which are not supported.
When a node goes down, the block volumes attached to the node cannot be attached to another node	1. Force delete the pod running on the node that went down 2. Delete the volumeattachment to the node that went down. Now the volume can be attached to the new node.
When attempting a driver upgrade, you see: `spec.fsGroupPolicy: Invalid value: "xxx": field is immutable`	You cannot upgrade between drivers with different fsGroupPolicies. See upgrade documentation for more details
Ater the migration group is in “migrated” state but unable to move to “commit ready” state because the new paths are not being discovered on the cluster nodes.	Run the following commands manually on the cluster nodes `rescan-scsi-bus.sh  -i` `rescan-scsi-bus.sh  -a`
`Failed to fetch details for array: 000000000000. [Unauthorized]`"	Please make sure that correct encrypted username and password in secret files are used, also ensure whether the RBAC is enabled for the user
`Error looking up volume for idempotence check: Not Found` or `Get Volume step fails for: (000000000000) symID with error (Invalid Response from API)`	Make sure that Unisphere endpoint doesn’t end with front slash
`FailedPrecondition desc = no topology keys could be generate`	Make sure that FC or iSCSI connectivity to the arrays are proper
CreateHost failed with error `initiator is already part of different host.`	Update modifyHostName to true in values.yaml Or Remove the initiator from existing host
`kubectl logs powermax-controller-<xyz> –n <namespace>` driver logs says connection refused and the reverseproxy logs says “Failed to setup server.(secrets "secret-name" not found)”	Make sure the given secret exist on the cluster
nodestage is failing with error `Error invalid IQN Target iqn.EMC.0648.SE1F`	1. Update initiator name to full default name , ex: iqn.1993-08.org.debian:01:e9afae962192 2.Ensure that the iSCSI initiators are available on all the nodes where the driver node plugin will be installed and it should be full default name.
Volume mount is failing on few OS(ex:VMware Virtual Platform) during node publish with error `wrong fs type, bad option, bad superblock`	1. Check the multipath configuration(if enabled) 2. Edit Vm Advanced settings->hardware and add the param `disk.enableUUID=true` and reboot the node
Standby controller pod is in crashloopbackoff state	Scale down the replica count of the controller pod’s deployment to 1 using `kubectl scale deployment <deployment_name> --replicas=1 -n <driver_namespace>`
When running CSI-PowerMax with Replication in a multi-cluster configuration, the driver on the target cluster fails and the following error is seen in logs: `error="CSI reverseproxy service host or port not found, CSI reverseproxy not installed properly"`	The reverseproxy service needs to be created manually on the target cluster. Follow the instructions here to create it.
PVC creation is failing with error `A problem occurred modifying the storage group resource: Failed to create batch task(s): The maximum allowed devices for a storage group has been exceeded`. This is because of a hardware limit of 4k devices in a storage group.	Create a separate Storage Class with a new unique `ApplicationPrefix` parameter (such as `ApplicationPrefix: OCPX`) or add a new unique `StorageGroup` parameter (such as `StorageGroup: "custom_SG_1"`) to place the provisioned volumes in a new Storage Group.

PowerMax

Mon, 01 Jan 0001 00:00:00 +0000

Release Notes - CSI PowerMax v2.13.0

Note: Auto SRDF group creation is currently not supported in PowerMaxOS 10.1 (6079) Arrays.

Note: Starting from CSI v2.4.0, Only Unisphere 10.0 REST endpoints are supported. It is mandatory that Unisphere should be updated to 10.0. Please find the instructions here.

Test PowerMax CSI Driver

Mon, 01 Jan 0001 00:00:00 +0000

This section provides multiple methods to test driver functionality in your environment. The tests are validated using bash as the default shell.

Note: To run the test for CSI Driver for Dell PowerMax, install Helm 3.

The csi-powermax repository includes examples of how you can use CSI Driver for Dell PowerMax. The shell scripts are used to automate the installation and uninstallation of helm charts for the creation of Pods with a different number of volumes in a given namespace using the storageclass provided. To test the installation of the CSI driver, perform these tests:

PowerMax

Mon, 01 Jan 0001 00:00:00 +0000

Symptoms	Prevention, Resolution or Workaround
`kubectl describe pod powermax-controller-<xyz> –n <namespace>` indicates that the driver image could not be loaded	You may need to put an insecure-registries entry in `/etc/docker/daemon.json` or log in to the docker registry
`kubectl logs powermax-controller-<xyz> –n <namespace> driver` logs show that the driver cannot authenticate	Check your secret’s username and password
`kubectl logs powermax-controller-<xyz> –n <namespace> driver` logs show that the driver failed to connect to the U4P because it could not verify the certificates	Check the powermax-certs secret and ensure it is not empty or it has the valid certificates
Driver install or upgrade fails because of an incompatible Kubernetes version, even though the version seems to be within the range of compatibility. For example: Error: UPGRADE FAILED: chart requires kubeVersion: >= 1.23.0 < 1.27.0 which is incompatible with Kubernetes V1.23.11-mirantis-1	If you are using an extended Kubernetes version, please see the helm Chart and use the alternate kubeVersion check that is provided in the comments. Please note that this is not meant to be used to enable the use of pre-release alpha and beta versions, which are not supported.
When a node goes down, the block volumes attached to the node cannot be attached to another node	1. Force delete the pod running on the node that went down 2. Delete the volumeattachment to the node that went down. Now the volume can be attached to the new node.
When attempting a driver upgrade, you see: `spec.fsGroupPolicy: Invalid value: "xxx": field is immutable`	You cannot upgrade between drivers with different fsGroupPolicies. See upgrade documentation for more details
Ater the migration group is in “migrated” state but unable to move to “commit ready” state because the new paths are not being discovered on the cluster nodes.	Run the following commands manually on the cluster nodes `rescan-scsi-bus.sh  -i` `rescan-scsi-bus.sh  -a`
`Failed to fetch details for array: 000000000000. [Unauthorized]`"	Please make sure that correct encrypted username and password in secret files are used, also ensure whether the RBAC is enabled for the user
`Error looking up volume for idempotence check: Not Found` or `Get Volume step fails for: (000000000000) symID with error (Invalid Response from API)`	Make sure that Unisphere endpoint doesn’t end with front slash
`FailedPrecondition desc = no topology keys could be generate`	Make sure that FC or iSCSI connectivity to the arrays are proper
CreateHost failed with error `initiator is already part of different host.`	Update modifyHostName to true in values.yaml Or Remove the initiator from existing host
`kubectl logs powermax-controller-<xyz> –n <namespace>` driver logs says connection refused and the reverseproxy logs says “Failed to setup server.(secrets "secret-name" not found)”	Make sure the given secret exist on the cluster
nodestage is failing with error `Error invalid IQN Target iqn.EMC.0648.SE1F`	1. Update initiator name to full default name , ex: iqn.1993-08.org.debian:01:e9afae962192 2.Ensure that the iSCSI initiators are available on all the nodes where the driver node plugin will be installed and it should be full default name.
Volume mount is failing on few OS(ex:VMware Virtual Platform) during node publish with error `wrong fs type, bad option, bad superblock`	1. Check the multipath configuration(if enabled) 2. Edit Vm Advanced settings->hardware and add the param `disk.enableUUID=true` and reboot the node
Standby controller pod is in crashloopbackoff state	Scale down the replica count of the controller pod’s deployment to 1 using `kubectl scale deployment <deployment_name> --replicas=1 -n <driver_namespace>`
When running CSI-PowerMax with Replication in a multi-cluster configuration, the driver on the target cluster fails and the following error is seen in logs: `error="CSI reverseproxy service host or port not found, CSI reverseproxy not installed properly"`	The reverseproxy service needs to be created manually on the target cluster. Follow the instructions here to create it.
PVC creation is failing with error `A problem occurred modifying the storage group resource: Failed to create batch task(s): The maximum allowed devices for a storage group has been exceeded`. This is because of a hardware limit of 4k devices in a storage group.	Create a separate Storage Class with a new unique `ApplicationPrefix` parameter (such as `ApplicationPrefix: OCPX`) or add a new unique `StorageGroup` parameter (such as `StorageGroup: "custom_SG_1"`) to place the provisioned volumes in a new Storage Group.

PowerMax

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The CSI Driver for Dell PowerMax can be installed via the Dell CSM Operator. To deploy the Operator, follow the instructions available here.

Listing installed drivers

To query for all Dell CSI drivers installed with the ContainerStorageModule CRD use the following command:

PowerMax

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The CSI Driver for Dell PowerMax can be deployed by using the provided Helm v3 charts and installation scripts on both Kubernetes and OpenShift platforms. For more detailed information on the installation scripts, see the script documentation.

Prerequisites

Symptoms	Prevention, Resolution or Workaround
The `kubectl logs isilon-controller-0 -n isilon -c driver` logs shows the driver cannot authenticate	Check your secret’s username and password for corresponding cluster
The `kubectl logs isilon-controller-0 -n isilon -c driver` logs shows the driver failed to connect to the Isilon because it couldn’t verify the certificates	Check the isilon-certs- secret and ensure it is not empty and it has the valid certificates. Set `isiInsecure: "true"` for insecure connection. SSL validation is recommended in the production environment.
The `kubectl logs isilon-controller-0 -n isilon -c driver` logs shows the driver error: create volume failed, Access denied. create directory as requested	This situation can happen when the user who created the base path is different from the user configured for the driver. Make sure the user used to deploy CSI-Driver must have enough rights on the base path (i.e. isiPath) to perform all operations.
Volume/filesystem is allowed to mount by any host in the network, though that host is not a part of the export of that particular volume under /ifs directory	“Dell PowerScale: OneFS NFS Design Considerations and Best Practices”: There is a default shared directory (ifs) of OneFS, which lets clients running Windows, UNIX, Linux, or Mac OS X access the same directories and files. It is recommended to disable the ifs shared directory in a production environment and create dedicated NFS exports and SMB shares for your workload.
Creating snapshot fails if the parameter IsiPath in volume snapshot class and related storage class is not the same. The driver uses the incorrect IsiPath parameter and tries to locate the source volume due to the inconsistency.	Ensure IsiPath in VolumeSnapshotClass yaml and related storageClass yaml are the same.
While deleting a volume, if there are files or folders created on the volume that are owned by different users. If the Isilon credentials used are for a nonprivileged Isilon user, the delete volume action fails. It is due to the limitation in Linux permission control.	To perform the delete volume action, the user account must be assigned a role that has the privilege ISI_PRIV_IFS_RESTORE. The user account must have the following set of privileges to ensure that all the CSI Isilon driver capabilities work properly: * ISI_PRIV_LOGIN_PAPI * ISI_PRIV_NFS * ISI_PRIV_QUOTA * ISI_PRIV_SNAPSHOT * ISI_PRIV_IFS_RESTORE * ISI_PRIV_NS_IFS_ACCESS * ISI_PRIV_STATISTICS In some cases, ISI_PRIV_BACKUP is also required, for example, when files owned by other users have mode bits set to 700.
If the hostname is mapped to loopback IP in /etc/hosts file, and pods are created using 1.3.0.1 release, after upgrade to driver version 1.4.0 or later there is a possibility of “localhost” as a stale entry in export	Recommended setup: User should not map a hostname to loopback IP in /etc/hosts file
Driver node pod is in “CrashLoopBackOff” as “Node ID” generated is not with proper FQDN.	This might be due to “dnsPolicy” implemented on the driver node pod which may differ with different networks. This parameter is configurable in both helm and Operator installer and the user can try with different “dnsPolicy” according to the environment.
The `kubectl logs isilon-controller-0 -n isilon -c driver` logs shows the driver Authentication failed. Trying to re-authenticate when using Session-based authentication	The issue has been resolved from OneFS 9.3 onwards, for OneFS versions prior to 9.3 for session-based authentication either smart connect can be created against a single node of Isilon or CSI Driver can be installed/pointed to a particular node of the Isilon else basic authentication can be used by setting isiAuthType in `values.yaml` to 0
When an attempt is made to create more than one ReadOnly PVC from the same volume snapshot, the second and subsequent requests result in PVCs in state `Pending`, with a warning `another RO volume from this snapshot is already present`. This is because the driver allows only one RO volume from a specific snapshot at any point in time. This is to allow faster creation(within a few seconds) of a RO PVC from a volume snapshot irrespective of the size of the volume snapshot.	Wait for the deletion of the first RO PVC created from the same volume snapshot.
Driver install or upgrade fails because of an incompatible Kubernetes version, even though the version seems to be within the range of compatibility. For example: Error: UPGRADE FAILED: chart requires kubeVersion: >= 1.22.0 < 1.25.0 which is incompatible with Kubernetes V1.22.11-mirantis-1	If you are using an extended Kubernetes version, please see the helm Chart and use the alternate kubeVersion check that is provided in the comments. Please note that this is not meant to be used to enable the use of pre-release alpha and beta versions, which is not supported.
Standby controller pod is in crashloopbackoff state	Scale down the replica count of the controller pod’s deployment to 1 using `kubectl scale deployment <deployment_name> --replicas=1 -n <driver_namespace>`
fsGroupPolicy may not work as expected without root privileges for NFS only https://github.com/kubernetes/examples/issues/260	To get the desired behavior set “RootClientEnabled” = “true” in the storage class parameter

PowerScale

Mon, 01 Jan 0001 00:00:00 +0000

Release Notes - CSI Driver for PowerScale v2.13.0

New Features/Changes

Fixed Issues

Known Issues

Issue	Resolution or workaround, if known
Storage capacity tracking does not return `MaximumVolumeSize` parameter. PowerScale is purely NFS based meaning it has no actual volumes. Therefore `MaximumVolumeSize` cannot be implemented if there is no volume creation.	CSI PowerScale 2.9.1 is compliant with CSI 1.6 specification since the field `MaximumVolumeSize` is optional.
If the length of the nodeID exceeds 128 characters, the driver fails to update the CSINode object and installation fails. This is due to a limitation set by CSI spec which doesn’t allow nodeID to be greater than 128 characters.	The CSI PowerScale driver uses the hostname for building the nodeID which is set in the CSINode resource object, hence we recommend not having very long hostnames in order to avoid this issue. This current limitation of 128 characters is likely to be relaxed in future Kubernetes versions as per this issue in the community: https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver/issues/581 Note: In kubernetes 1.22 this limit has been relaxed to 192 characters.
If some older NFS exports /terminated worker nodes still in NFS export client list, CSI driver tries to add a new worker node it fails (For RWX volume).	User need to manually clean the export client list from old entries to make successful addition of new worker nodes.
Delete namespace that has PVCs and pods created with the driver. The External health monitor sidecar crashes as a result of this operation.	Deleting the namespace deletes the PVCs first and then removes the pods in the namespace. This brings a condition where pods exist without their PVCs and causes the external-health-monitor sidecar to crash. This is a known issue and has been reported at https://github.com/kubernetes-csi/external-health-monitor/issues/100
fsGroupPolicy may not work as expected without root privileges for NFS only https://github.com/kubernetes/examples/issues/260	To get the desired behavior set “RootClientEnabled” = “true” in the storage class parameter
PowerScale 9.5.0, Driver installation fails with session based auth, “HTTP/1.1 401 Unauthorized”	Fix is available in PowerScale >= 9.5.0.4
If the volume limit is exhausted and there are pending pods and PVCs due to `exceed max volume count`, the pending PVCs will be bound to PVs and the pending pods will be scheduled to nodes when the driver pods are restarted.	It is advised not to have any pending pods or PVCs once the volume limit per node is exhausted on a CSI Driver. There is an open issue reported with kubernetes at https://github.com/kubernetes/kubernetes/issues/95911 with the same behavior.

Note

Support for Kubernetes alpha features like Volume Health Monitoring will not be available in Openshift environment as Openshift doesn’t support enabling of alpha features for Production Grade clusters.

Test PowerScale CSI Driver

Mon, 01 Jan 0001 00:00:00 +0000

This section provides multiple methods to test driver functionality in your environment.

Note: To run the test for CSI Driver for Dell PowerScale, install Helm 3.

Test deploying a simple pod with PowerScale storage

Test the deployment workflow of a simple pod on PowerScale storage.

PowerScale

Mon, 01 Jan 0001 00:00:00 +0000

Here are some installation failures that might be encountered and how to mitigate them.

Symptoms	Prevention, Resolution or Workaround
The `kubectl logs isilon-controller-0 -n isilon -c driver` logs shows the driver cannot authenticate	Check your secret’s username and password for corresponding cluster
The `kubectl logs isilon-controller-0 -n isilon -c driver` logs shows the driver failed to connect to the Isilon because it couldn’t verify the certificates	Check the isilon-certs- secret and ensure it is not empty and it has the valid certificates. Set `isiInsecure: "true"` for insecure connection. SSL validation is recommended in the production environment.
The `kubectl logs isilon-controller-0 -n isilon -c driver` logs shows the driver error: create volume failed, Access denied. create directory as requested	This situation can happen when the user who created the base path is different from the user configured for the driver. Make sure the user used to deploy CSI-Driver must have enough rights on the base path (i.e. isiPath) to perform all operations.
Volume/filesystem is allowed to mount by any host in the network, though that host is not a part of the export of that particular volume under /ifs directory	“Dell PowerScale: OneFS NFS Design Considerations and Best Practices”: There is a default shared directory (ifs) of OneFS, which lets clients running Windows, UNIX, Linux, or Mac OS X access the same directories and files. It is recommended to disable the ifs shared directory in a production environment and create dedicated NFS exports and SMB shares for your workload.
Creating snapshot fails if the parameter IsiPath in volume snapshot class and related storage class is not the same. The driver uses the incorrect IsiPath parameter and tries to locate the source volume due to the inconsistency.	Ensure IsiPath in VolumeSnapshotClass yaml and related storageClass yaml are the same.
While deleting a volume, if there are files or folders created on the volume that are owned by different users. If the Isilon credentials used are for a nonprivileged Isilon user, the delete volume action fails. It is due to the limitation in Linux permission control.	To perform the delete volume action, the user account must be assigned a role that has the privilege ISI_PRIV_IFS_RESTORE. The user account must have the following set of privileges to ensure that all the CSI Isilon driver capabilities work properly: * ISI_PRIV_LOGIN_PAPI * ISI_PRIV_NFS * ISI_PRIV_QUOTA * ISI_PRIV_SNAPSHOT * ISI_PRIV_IFS_RESTORE * ISI_PRIV_NS_IFS_ACCESS * ISI_PRIV_STATISTICS In some cases, ISI_PRIV_BACKUP is also required, for example, when files owned by other users have mode bits set to 700.
If the hostname is mapped to loopback IP in /etc/hosts file, and pods are created using 1.3.0.1 release, after upgrade to driver version 1.4.0 or later there is a possibility of “localhost” as a stale entry in export	Recommended setup: User should not map a hostname to loopback IP in /etc/hosts file
Driver node pod is in “CrashLoopBackOff” as “Node ID” generated is not with proper FQDN.	This might be due to “dnsPolicy” implemented on the driver node pod which may differ with different networks. This parameter is configurable in both helm and Operator installer and the user can try with different “dnsPolicy” according to the environment.
The `kubectl logs isilon-controller-0 -n isilon -c driver` logs shows the driver Authentication failed. Trying to re-authenticate when using Session-based authentication	The issue has been resolved from OneFS 9.3 onwards, for OneFS versions prior to 9.3 for session-based authentication either smart connect can be created against a single node of Isilon or CSI Driver can be installed/pointed to a particular node of the Isilon else basic authentication can be used by setting isiAuthType in `values.yaml` to 0
When an attempt is made to create more than one ReadOnly PVC from the same volume snapshot, the second and subsequent requests result in PVCs in state `Pending`, with a warning `another RO volume from this snapshot is already present`. This is because the driver allows only one RO volume from a specific snapshot at any point in time. This is to allow faster creation(within a few seconds) of a RO PVC from a volume snapshot irrespective of the size of the volume snapshot.	Wait for the deletion of the first RO PVC created from the same volume snapshot.
Driver install or upgrade fails because of an incompatible Kubernetes version, even though the version seems to be within the range of compatibility. For example: Error: UPGRADE FAILED: chart requires kubeVersion: >= 1.22.0 < 1.25.0 which is incompatible with Kubernetes V1.22.11-mirantis-1	If you are using an extended Kubernetes version, please see the helm Chart and use the alternate kubeVersion check that is provided in the comments. Please note that this is not meant to be used to enable the use of pre-release alpha and beta versions, which is not supported.
Standby controller pod is in crashloopbackoff state	Scale down the replica count of the controller pod’s deployment to 1 using `kubectl scale deployment <deployment_name> --replicas=1 -n <driver_namespace>`
fsGroupPolicy may not work as expected without root privileges for NFS only https://github.com/kubernetes/examples/issues/260	To get the desired behavior set “RootClientEnabled” = “true” in the storage class parameter

PowerScale

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The CSI Driver for Dell PowerScale can be installed via the Dell CSM Operator. To deploy the Operator, follow the instructions available here.

Listing installed drivers

To query for all Dell CSI drivers installed with the ContainerStorageModule CRD use the following command:

PowerScale

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The CSI Driver for Dell PowerScale can be deployed by using the provided Helm v3 charts and installation scripts on both Kubernetes and OpenShift platforms. For more detailed information on the installation scripts, review the script documentation.

Prerequisites

The following are requirements to be met before installing the CSI Driver for Dell PowerScale:

Test PowerStore CSI Driver

Mon, 01 Jan 0001 00:00:00 +0000

In the repository, a simple test manifest exists that creates three different PersistentVolumeClaims using default ext4, xfs, and nfs storage classes and automatically mounts them to the pod.

It assumes that you’ve created the same basic three storage classes from samples/storageclass folder without changing their names. If you’ve created different storage classes please edit tests/simple/simple.yaml and change PersistentVolumeClaim definitions to point to correct storage classes.

Steps

To run this test, run the kubectl command from the root directory of the repository:
```
kubectl create -f ./tests/simple/
```

You can find all the created resources in testpowerstore namespace.

PowerStore

Mon, 01 Jan 0001 00:00:00 +0000

Symptoms	Prevention, Resolution or Workaround
When you run the command `kubectl describe pods powerstore-controller-<suffix> –n csi-powerstore`, the system indicates that the driver image could not be loaded.	- If on Kubernetes, edit the daemon.json file found in the registry location and add `{ "insecure-registries" :[ "hostname.cloudapp.net:5000" ] }` - If on OpenShift, run the command `oc edit image.config.openshift.io/cluster` and add registries to yaml file that is displayed when you run the command.
The `kubectl logs -n csi-powerstore powerstore-node-<suffix>` driver logs show that the driver can’t connect to PowerStore API.	Check if you’ve created a secret with correct credentials
Installation of the driver on Kubernetes supported versions fails with the following error: `Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "VolumeSnapshotClass" in version "snapshot.storage.k8s.io/v1"`	Kubernetes v1.21/v1.22/v1.23 requires v1 version of snapshot CRDs to be created in cluster, see the Volume Snapshot Requirements
If PVC is not getting created and getting the following error in PVC description: `failed to provision volume with StorageClass "powerstore-iscsi": rpc error: code = Internal desc = : Unknown error:`	Check if you’ve created a secret with correct credentials
If the NVMeFC pod is not getting created and the host looses the ssh connection, causing the driver pods to go to error state	remove the nvme_tcp module from the host in case of NVMeFC connection
When a node goes down, the block volumes attached to the node cannot be attached to another node	1. Force delete the pod running on the node that went down 2. Delete the volumeattachment to the node that went down. Now the volume can be attached to the new node.
If the pod creation for NVMe takes time when the connections between the host and the array are more than 2 and considerable volumes are mounted on the host	Reduce the number of connections between the host and the array to 2.
Driver install or upgrade fails because of an incompatible Kubernetes version, even though the version seems to be within the range of compatibility. For example: Error: UPGRADE FAILED: chart requires kubeVersion: >= 1.22.0 < 1.25.0 which is incompatible with Kubernetes V1.22.11-mirantis-1	If you are using an extended Kubernetes version, please see the helm Chart and use the alternate kubeVersion check that is provided in the comments. Please note that this is not meant to be used to enable the use of pre-release alpha and beta versions, which is not supported.
If two separate networks are configured for ISCSI and NVMeTCP, the driver may encounter difficulty identifying the second network (e.g., NVMeTCP).	This is a known issue, and the workaround involves creating a single network on the array to serve both ISCSI and NVMeTCP purposes.
Unable to provision PVC’s via driver	Ensure that the NAS name matches the one provided on the array side.
Unable to install or upgrade the driver	Ensure that the firewall is configured to grant adequate permissions for downloading images from the registry.
Faulty paths in the multipath	Ensure that the configuration of the multipath is correct and connectivity to the underlying hardware is intact.
Unable to install or upgrade the driver due to minimum Kubernetes version or Openshift version	Currently CSM only supports n, n-1, n-2 version of Kubernetes and Openshift, if you still wanted to continue with existing version update the `verify.sh` to continue.
Volumes are not getting deleted on the array when PV’s are deleted	Ensure `persistentVolumeReclaimPolicy` is set to Delete.
fsGroupPolicy may not work as expected without root privileges for NFS only https://github.com/kubernetes/examples/issues/260	To get the desired behavior set “RootClientEnabled” = “true” in the storage class parameter

Test PowerStore CSI Driver

Mon, 01 Jan 0001 00:00:00 +0000

In the repository, a simple test manifest exists that creates three different PersistentVolumeClaims using default ext4, xfs, and nfs storage classes and automatically mounts them to the pod.

It assumes that you’ve created the same basic three storage classes from samples/storageclass folder without changing their names. If you’ve created different storage classes please edit tests/simple/simple.yaml and change PersistentVolumeClaim definitions to point to correct storage classes.

Steps

To run this test, run the kubectl command from the root directory of the repository:
```
kubectl create -f ./tests/simple/
```

You can find all the created resources in testpowerstore namespace.

PowerStore

Mon, 01 Jan 0001 00:00:00 +0000

Symptoms	Prevention, Resolution or Workaround
When you run the command `kubectl describe pods powerstore-controller-<suffix> –n csi-powerstore`, the system indicates that the driver image could not be loaded.	- If on Kubernetes, edit the daemon.json file found in the registry location and add `{ "insecure-registries" :[ "hostname.cloudapp.net:5000" ] }` - If on OpenShift, run the command `oc edit image.config.openshift.io/cluster` and add registries to yaml file that is displayed when you run the command.
The `kubectl logs -n csi-powerstore powerstore-node-<suffix>` driver logs show that the driver can’t connect to PowerStore API.	Check if you’ve created a secret with correct credentials
Installation of the driver on Kubernetes supported versions fails with the following error: `Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "VolumeSnapshotClass" in version "snapshot.storage.k8s.io/v1"`	Kubernetes v1.21/v1.22/v1.23 requires v1 version of snapshot CRDs to be created in cluster, see the Volume Snapshot Requirements
If PVC is not getting created and getting the following error in PVC description: `failed to provision volume with StorageClass "powerstore-iscsi": rpc error: code = Internal desc = : Unknown error:`	Check if you’ve created a secret with correct credentials
If the NVMeFC pod is not getting created and the host looses the ssh connection, causing the driver pods to go to error state	remove the nvme_tcp module from the host in case of NVMeFC connection
When a node goes down, the block volumes attached to the node cannot be attached to another node	1. Force delete the pod running on the node that went down 2. Delete the volumeattachment to the node that went down. Now the volume can be attached to the new node.
If the pod creation for NVMe takes time when the connections between the host and the array are more than 2 and considerable volumes are mounted on the host	Reduce the number of connections between the host and the array to 2.
Driver install or upgrade fails because of an incompatible Kubernetes version, even though the version seems to be within the range of compatibility. For example: Error: UPGRADE FAILED: chart requires kubeVersion: >= 1.22.0 < 1.25.0 which is incompatible with Kubernetes V1.22.11-mirantis-1	If you are using an extended Kubernetes version, please see the helm Chart and use the alternate kubeVersion check that is provided in the comments. Please note that this is not meant to be used to enable the use of pre-release alpha and beta versions, which is not supported.
If two separate networks are configured for ISCSI and NVMeTCP, the driver may encounter difficulty identifying the second network (e.g., NVMeTCP).	This is a known issue, and the workaround involves creating a single network on the array to serve both ISCSI and NVMeTCP purposes.
Unable to provision PVC’s via driver	Ensure that the NAS name matches the one provided on the array side.
Unable to install or upgrade the driver	Ensure that the firewall is configured to grant adequate permissions for downloading images from the registry.
Faulty paths in the multipath	Ensure that the configuration of the multipath is correct and connectivity to the underlying hardware is intact.
Unable to install or upgrade the driver due to minimum Kubernetes version or Openshift version	Currently CSM only supports n, n-1, n-2 version of Kubernetes and Openshift, if you still wanted to continue with existing version update the `verify.sh` to continue.
Volumes are not getting deleted on the array when PV’s are deleted	Ensure `persistentVolumeReclaimPolicy` is set to Delete.
fsGroupPolicy may not work as expected without root privileges for NFS only https://github.com/kubernetes/examples/issues/260	To get the desired behavior set “RootClientEnabled” = “true” in the storage class parameter

Test PowerStore CSI Driver

Mon, 01 Jan 0001 00:00:00 +0000

In the repository, a simple test manifest exists that creates three different PersistentVolumeClaims using default ext4, xfs, and nfs storage classes and automatically mounts them to the pod.

It assumes that you’ve created the same basic three storage classes from samples/storageclass folder without changing their names. If you’ve created different storage classes please edit tests/simple/simple.yaml and change PersistentVolumeClaim definitions to point to correct storage classes.

Steps

To run this test, run the kubectl command from the root directory of the repository:
```
kubectl create -f ./tests/simple/
```

You can find all the created resources in testpowerstore namespace.

PowerStore

Mon, 01 Jan 0001 00:00:00 +0000

Symptoms	Prevention, Resolution or Workaround
When you run the command `kubectl describe pods powerstore-controller-<suffix> –n csi-powerstore`, the system indicates that the driver image could not be loaded.	- If on Kubernetes, edit the daemon.json file found in the registry location and add `{ "insecure-registries" :[ "hostname.cloudapp.net:5000" ] }` - If on OpenShift, run the command `oc edit image.config.openshift.io/cluster` and add registries to yaml file that is displayed when you run the command.
The `kubectl logs -n csi-powerstore powerstore-node-<suffix>` driver logs show that the driver can’t connect to PowerStore API.	Check if you’ve created a secret with correct credentials
Installation of the driver on Kubernetes supported versions fails with the following error: `Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "VolumeSnapshotClass" in version "snapshot.storage.k8s.io/v1"`	Kubernetes v1.21/v1.22/v1.23 requires v1 version of snapshot CRDs to be created in cluster, see the Volume Snapshot Requirements
If PVC is not getting created and getting the following error in PVC description: `failed to provision volume with StorageClass "powerstore-iscsi": rpc error: code = Internal desc = : Unknown error:`	Check if you’ve created a secret with correct credentials
If the NVMeFC pod is not getting created and the host looses the ssh connection, causing the driver pods to go to error state	remove the nvme_tcp module from the host in case of NVMeFC connection
When a node goes down, the block volumes attached to the node cannot be attached to another node	1. Force delete the pod running on the node that went down 2. Delete the volumeattachment to the node that went down. Now the volume can be attached to the new node.
If the pod creation for NVMe takes time when the connections between the host and the array are more than 2 and considerable volumes are mounted on the host	Reduce the number of connections between the host and the array to 2.
Driver install or upgrade fails because of an incompatible Kubernetes version, even though the version seems to be within the range of compatibility. For example: Error: UPGRADE FAILED: chart requires kubeVersion: >= 1.22.0 < 1.25.0 which is incompatible with Kubernetes V1.22.11-mirantis-1	If you are using an extended Kubernetes version, please see the helm Chart and use the alternate kubeVersion check that is provided in the comments. Please note that this is not meant to be used to enable the use of pre-release alpha and beta versions, which is not supported.
If two separate networks are configured for ISCSI and NVMeTCP, the driver may encounter difficulty identifying the second network (e.g., NVMeTCP).	This is a known issue, and the workaround involves creating a single network on the array to serve both ISCSI and NVMeTCP purposes.
Unable to provision PVC’s via driver	Ensure that the NAS name matches the one provided on the array side.
Unable to install or upgrade the driver	Ensure that the firewall is configured to grant adequate permissions for downloading images from the registry.
Faulty paths in the multipath	Ensure that the configuration of the multipath is correct and connectivity to the underlying hardware is intact.
Unable to install or upgrade the driver due to minimum Kubernetes version or Openshift version	Currently CSM only supports n, n-1, n-2 version of Kubernetes and Openshift, if you still wanted to continue with existing version update the `verify.sh` to continue.
Volumes are not getting deleted on the array when PV’s are deleted	Ensure `persistentVolumeReclaimPolicy` is set to Delete.
fsGroupPolicy may not work as expected without root privileges for NFS only https://github.com/kubernetes/examples/issues/260	To get the desired behavior set “RootClientEnabled” = “true” in the storage class parameter

PowerStore

Mon, 01 Jan 0001 00:00:00 +0000

Release Notes - CSI PowerStore v2.13.0

New Features/Changes

Fixed Issues

Known Issues

Issue	Resolution or workaround, if known
Delete namespace that has PVCs and pods created with the driver. The External health monitor sidecar crashes as a result of this operation	Deleting the namespace deletes the PVCs first and then removes the pods in the namespace. This brings a condition where pods exist without their PVCs and causes the external-health-monitor sidecar to crash. This is a known issue and has been reported at https://github.com/kubernetes-csi/external-health-monitor/issues/100
fsGroupPolicy may not work as expected without root privileges for NFS only https://github.com/kubernetes/examples/issues/260	To get the desired behavior set “allowRoot: “true” in the storage class parameter
If the NVMeFC pod is not getting created and the host looses the ssh connection, causing the driver pods to go to error state	remove the nvme_tcp module from the host in case of NVMeFC connection
When a node goes down, the block volumes attached to the node cannot be attached to another node	This is a known issue and has been reported at https://github.com/kubernetes-csi/external-attacher/issues/215. Workaround: 1. Force delete the pod running on the node that went down 2. Delete the volumeattachment to the node that went down. Now the volume can be attached to the new node.
When driver node pods enter CrashLoopBackOff and PVC remains in pending state with one of the following events: 1. failed to provision volume with StorageClass `<storage-class-name>`: error generating accessibility requirements: no available topology found 2. waiting for a volume to be created, either by external provisioner “csi-powerstore.dellemc.com” or manually created by system administrator.	Check whether all array details present in the secret file are valid and remove any invalid entries if present. Redeploy the driver.
If an ephemeral pod is not being created in OpenShift 4.13 and is failing with the error “error when creating pod: the pod uses an inline volume provided by CSIDriver csi-powerstore.dellemc.com, and the namespace has a pod security enforcement level that is lower than privileged.”	This issue occurs because OpenShift 4.13 introduced the CSI Volume Admission plugin to restrict the use of a CSI driver capable of provisioning CSI ephemeral volumes during pod admission https://docs.openshift.com/container-platform/4.13/storage/container_storage_interface/ephemeral-storage-csi-inline.html . Therefore, an additional label “security.openshift.io/csi-ephemeral-volume-profile” needs to be added to the CSIDriver object to support inline ephemeral volumes.
In OpenShift 4.13, the root user is not allowed to perform write operations on NFS shares, when root squashing is enabled.	The workaround for this issue is to disable root squashing by setting allowRoot: “true” in the NFS storage class.
If the volume limit is exhausted and there are pending pods and PVCs due to `exceed max volume count`, the pending PVCs will be bound to PVs, and the pending pods will be scheduled to nodes when the driver pods are restarted.	It is advised not to have any pending pods or PVCs once the volume limit per node is exhausted on a CSI Driver. There is an open issue reported with Kubernetes at https://github.com/kubernetes/kubernetes/issues/95911 with the same behavior.
If two separate networks are configured for ISCSI and NVMeTCP, the driver may encounter difficulty identifying the second network (e.g., NVMeTCP).	This is a known issue, and the workaround involves creating a single network on the array to serve both ISCSI and NVMeTCP purposes.
When a PV/PVC is deleted in Kubernetes, it will trigger the deletion of the underlying volume and snapshot on the array as a default behaviour. This can result in a situation where the VolumeSnapshot and VolumeSnapshotContent will still show “readyToUse: true”, but leaves them unusable because it is no longer backed by underlying storage snapshot. This will not allow the creation of a PVC from snapshot and this could also lead to a data loss situations.	This is a known issue, and the workaround is use of retain policy on the various PV, VolumeSnapshot and VolumeSnapshotContent that you wish to use for cloning.

Note:

Support for Kubernetes alpha features like Volume Health Monitoring will not be available in Openshift environment as Openshift doesn’t support enabling of alpha features for Production Grade clusters.

Test PowerStore CSI Driver

Mon, 01 Jan 0001 00:00:00 +0000

In the repository, a simple test manifest exists that creates three different PersistentVolumeClaims using default ext4, xfs, and nfs storage classes and automatically mounts them to the pod.

It assumes that you’ve created the same basic three storage classes from samples/storageclass folder without changing their names. If you’ve created different storage classes please edit tests/simple/simple.yaml and change PersistentVolumeClaim definitions to point to correct storage classes.

Steps

To run this test, run the kubectl command from the root directory of the repository:
```
kubectl create -f ./tests/simple/
```

You can find all the created resources in testpowerstore namespace.

PowerStore

Mon, 01 Jan 0001 00:00:00 +0000

Symptoms	Prevention, Resolution or Workaround
When you run the command `kubectl describe pods powerstore-controller-<suffix> –n csi-powerstore`, the system indicates that the driver image could not be loaded.	- If on Kubernetes, edit the daemon.json file found in the registry location and add `{ "insecure-registries" :[ "hostname.cloudapp.net:5000" ] }` - If on OpenShift, run the command `oc edit image.config.openshift.io/cluster` and add registries to yaml file that is displayed when you run the command.
The `kubectl logs -n csi-powerstore powerstore-node-<suffix>` driver logs show that the driver can’t connect to PowerStore API.	Check if you’ve created a secret with correct credentials
Installation of the driver on Kubernetes supported versions fails with the following error: `Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "VolumeSnapshotClass" in version "snapshot.storage.k8s.io/v1"`	Kubernetes v1.21/v1.22/v1.23 requires v1 version of snapshot CRDs to be created in cluster, see the Volume Snapshot Requirements
If PVC is not getting created and getting the following error in PVC description: `failed to provision volume with StorageClass "powerstore-iscsi": rpc error: code = Internal desc = : Unknown error:`	Check if you’ve created a secret with correct credentials
If the NVMeFC pod is not getting created and the host looses the ssh connection, causing the driver pods to go to error state	remove the nvme_tcp module from the host in case of NVMeFC connection
When a node goes down, the block volumes attached to the node cannot be attached to another node	1. Force delete the pod running on the node that went down 2. Delete the volumeattachment to the node that went down. Now the volume can be attached to the new node.
If the pod creation for NVMe takes time when the connections between the host and the array are more than 2 and considerable volumes are mounted on the host	Reduce the number of connections between the host and the array to 2.
Driver install or upgrade fails because of an incompatible Kubernetes version, even though the version seems to be within the range of compatibility. For example: Error: UPGRADE FAILED: chart requires kubeVersion: >= 1.22.0 < 1.25.0 which is incompatible with Kubernetes V1.22.11-mirantis-1	If you are using an extended Kubernetes version, please see the helm Chart and use the alternate kubeVersion check that is provided in the comments. Please note that this is not meant to be used to enable the use of pre-release alpha and beta versions, which is not supported.
If two separate networks are configured for ISCSI and NVMeTCP, the driver may encounter difficulty identifying the second network (e.g., NVMeTCP).	This is a known issue, and the workaround involves creating a single network on the array to serve both ISCSI and NVMeTCP purposes.
Unable to provision PVC’s via driver	Ensure that the NAS name matches the one provided on the array side.
Unable to install or upgrade the driver	Ensure that the firewall is configured to grant adequate permissions for downloading images from the registry.
Faulty paths in the multipath	Ensure that the configuration of the multipath is correct and connectivity to the underlying hardware is intact.
Unable to install or upgrade the driver due to minimum Kubernetes version or Openshift version	Currently CSM only supports n, n-1, n-2 version of Kubernetes and Openshift, if you still wanted to continue with existing version update the `verify.sh` to continue.
Volumes are not getting deleted on the array when PV’s are deleted	Ensure `persistentVolumeReclaimPolicy` is set to Delete.
fsGroupPolicy may not work as expected without root privileges for NFS only https://github.com/kubernetes/examples/issues/260	To get the desired behavior set “RootClientEnabled” = “true” in the storage class parameter

PowerStore

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The CSI Driver for Dell PowerStore can be installed via the Dell CSM Operator. To deploy the Operator, follow the instructions available here.

Listing installed drivers

To query for all Dell CSI drivers installed with the ContainerStorageModule CRD use the following command:

PowerStore

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The CSI Driver for Dell PowerStore can be deployed by using the provided Helm v3 charts and installation scripts on both Kubernetes and OpenShift platforms. For more detailed information on the installation scripts, review the script documentation.

Prerequisites

The following requirements must be met before installing the CSI Driver for Dell PowerStore:

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules Operator installs the Replication module for supported Dell CSI Drivers, deploying the Replication sidecar and Controller Manage.

Prerequisites

To configure Replication prior to installation via Container Storage Modules Operator, you need:

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Review the SyncIQ configuration on both the source and target PowerScale

a. Use the below command to verify the SyncIQ is licensed on both PowerScale.

 isi license list

b. Use the below command to review the SyncIQ configuration on the source PowerScale

ps01-1# isi sync settings view

                                 Service: on
                           Source Subnet: -
                             Source Pool: -
                         Force Interface: No
                 Restrict Target Network: No
                       Tw Chkpt Interval: -
                          Report Max Age: 1Y
                        Report Max Count: 2000
                              RPO Alerts: Yes
                     Max Concurrent Jobs: 24
Bandwidth Reservation Reserve Percentage: 1
  Bandwidth Reservation Reserve Absolute: -
                     Encryption Required: Yes
                  Cluster Certificate ID: 809c57b723f765b33a4a1a9905fd5837c12ae0ebe5f75ffd5aa3353cd83536e8
              OCSP Issuer Certificate ID: 
                            OCSP Address: 
                  Encryption Cipher List: 
                     Elliptic Curve List: 
                    Renegotiation Period: 8H
                 Service History Max Age: 1Y
               Service History Max Count: 2000
                    Use Workers Per Node: No
                     Preferred RPO Alert: Never
                            Password Set: No

c. Use this command to review the SyncIQ configuration on the target PowerScale

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules Operator installs the Replication module for supported Dell CSI Drivers, deploying the Replication sidecar and Controller Manage.

Prerequisites

To configure Replication prior to installation via Container Storage Modules Operator, you need:

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Review the SyncIQ configuration on both the source and target PowerScale

a. Use the below command to verify the SyncIQ is licensed on both PowerScale.

 isi license list

b. Use the below command to review the SyncIQ configuration on the source PowerScale

ps01-1# isi sync settings view

                                 Service: on
                           Source Subnet: -
                             Source Pool: -
                         Force Interface: No
                 Restrict Target Network: No
                       Tw Chkpt Interval: -
                          Report Max Age: 1Y
                        Report Max Count: 2000
                              RPO Alerts: Yes
                     Max Concurrent Jobs: 24
Bandwidth Reservation Reserve Percentage: 1
  Bandwidth Reservation Reserve Absolute: -
                     Encryption Required: Yes
                  Cluster Certificate ID: 809c57b723f765b33a4a1a9905fd5837c12ae0ebe5f75ffd5aa3353cd83536e8
              OCSP Issuer Certificate ID: 
                            OCSP Address: 
                  Encryption Cipher List: 
                     Elliptic Curve List: 
                    Renegotiation Period: 8H
                 Service History Max Age: 1Y
               Service History Max Count: 2000
                    Use Workers Per Node: No
                     Preferred RPO Alert: Never
                            Password Set: No

c. Use this command to review the SyncIQ configuration on the target PowerScale

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules Operator installs the Replication module for supported Dell CSI Drivers, deploying the Replication sidecar and Controller Manage.

Prerequisites

To configure Replication prior to installation via Container Storage Modules Operator, you need:

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Review the SyncIQ configuration on both the source and target PowerScale

a. Use the below command to verify the SyncIQ is licensed on both PowerScale.

 isi license list

b. Use the below command to review the SyncIQ configuration on the source PowerScale

ps01-1# isi sync settings view

                                 Service: on
                           Source Subnet: -
                             Source Pool: -
                         Force Interface: No
                 Restrict Target Network: No
                       Tw Chkpt Interval: -
                          Report Max Age: 1Y
                        Report Max Count: 2000
                              RPO Alerts: Yes
                     Max Concurrent Jobs: 24
Bandwidth Reservation Reserve Percentage: 1
  Bandwidth Reservation Reserve Absolute: -
                     Encryption Required: Yes
                  Cluster Certificate ID: 809c57b723f765b33a4a1a9905fd5837c12ae0ebe5f75ffd5aa3353cd83536e8
              OCSP Issuer Certificate ID: 
                            OCSP Address: 
                  Encryption Cipher List: 
                     Elliptic Curve List: 
                    Renegotiation Period: 8H
                 Service History Max Age: 1Y
               Service History Max Count: 2000
                    Use Workers Per Node: No
                     Preferred RPO Alert: Never
                            Password Set: No

c. Use this command to review the SyncIQ configuration on the target PowerScale

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The CSM Replication module for supported Dell CSI Drivers can be installed via the Dell CSM Operator. Dell CSM Operator will deploy the CSM Replication sidecar and the CSM Replication Controller Manager.

Prerequisites

To configure Replication prior to installation via CSM Operator, you need:

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules Operator installs the Resiliency module for supported Dell CSI Drivers, deploying the Resiliency sidecar.

Prerequisite

The Resiliency module only acts on pods with a specific label. At startup, it logs the label key and value. Apply this label to the StatefulSet you want monitored

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Enable Resiliency Module

Use this command to create the ContainerStorageModule Custom Resource with Resiliency:

oc create -f csm-{{labels}}.yaml

Example:

cat << EOF > csm-{{labels}}.yaml
apiVersion: storage.dell.com/v1
kind: ContainerStorageModule
metadata:
  name: {{labels}}
  namespace: {{labels}}
spec:
  driver:
    csiDriverType: "{{Var}}"
    configVersion: Default text if no valid parameter is passed.
  modules:
  - name: resiliency
    enabled: true
EOF

Detailed Configuration: Use the sample file for detailed settings.

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules Operator installs the Resiliency module for supported Dell CSI Drivers, deploying the Resiliency sidecar.

Prerequisite

The Resiliency module only acts on pods with a specific label. At startup, it logs the label key and value. Apply this label to the StatefulSet you want monitored

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Enable Resiliency Module

Use this command to create the ContainerStorageModule Custom Resource with Resiliency:

oc create -f csm-{{labels}}.yaml

Example:

cat << EOF > csm-{{labels}}.yaml
apiVersion: storage.dell.com/v1
kind: ContainerStorageModule
metadata:
  name: {{labels}}
  namespace: {{labels}}
spec:
  driver:
    csiDriverType: "{{Var}}"
    configVersion: Default text if no valid parameter is passed.
  modules:
  - name: resiliency
    enabled: true
EOF

Detailed Configuration: Use the sample file for detailed settings.

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The Container Storage Modules Operator installs the Resiliency module for supported Dell CSI Drivers, deploying the Resiliency sidecar.

Prerequisite

The Resiliency module only acts on pods with a specific label. At startup, it logs the label key and value. Apply this label to the StatefulSet you want monitored

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Enable Resiliency Module

Use this command to create the ContainerStorageModule Custom Resource with Resiliency:

oc create -f csm-{{labels}}.yaml

Example:

cat << EOF > csm-{{labels}}.yaml
apiVersion: storage.dell.com/v1
kind: ContainerStorageModule
metadata:
  name: {{labels}}
  namespace: {{labels}}
spec:
  driver:
    csiDriverType: "{{Var}}"
    configVersion: Default text if no valid parameter is passed.
  modules:
  - name: resiliency
    enabled: true
EOF

Detailed Configuration: Use the sample file for detailed settings.

Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The CSM Resiliency module for supported Dell CSI Drivers can be installed via the Dell CSM Operator. Dell CSM Operator will deploy CSM Resiliency sidecar.

Prerequisite

When utilizing CSM for Resiliency module, it is crucial to note that it will solely act upon pods that have been assigned a designated label. This label must have both a key and a value that match what has been set in the resiliency module configuration. Upon startup, CSM for Resiliency generates a log message that displays the label key and value being used to monitor pods. This label must be applied the Statefulset that you want to be monitored by CSM for Resiliency.

Search Results

Symptoms	Prevention, Resolution or Workaround
When you run the command `kubectl describe pods unity-controller-<suffix> –n unity`, the system indicates that the driver image could not be loaded.	You may need to put an insecure-registries entry in `/etc/docker/daemon.json` or login to the docker registry
The `kubectl logs -n unity unity-node-<suffix>` driver logs show that the driver can’t connect to Unity XT - Authentication failure.	Check if you have created a secret with correct credentials
`fsGroup` specified in pod spec is not reflected in files or directories at mounted path of volume.	fsType of PVC must be set for fsGroup to work. fsType can be specified while creating a storage class. For NFS protocol, fsType can be specified as `nfs`. fsGroup doesn’t work for ephemeral inline volumes.
Dynamic array detection will not work in Topology based environment	Whenever a new array is added or removed, then the driver controller and node pod should be restarted with command kubectl get pods -n unity –no-headers=true \| awk ‘/unity-/{print $1}’\| xargs kubectl delete -n unity pod when topology-based storage classes are used. For dynamic array addition without topology, the driver will detect the newly added or removed arrays automatically
If source PVC is deleted when cloned PVC exists, then source PVC will be deleted in the cluster but on array, it will still be present and marked for deletion.	All the cloned PVC should be deleted in order to delete the source PVC from the array.
PVC creation fails on a fresh cluster with iSCSI and NFS protocols alone enabled with error failed to provision volume with StorageClass “unity-iscsi”: error generating accessibility requirements: no available topology found.	This is because iSCSI initiator login takes longer than the node pod startup time. This can be overcome by bouncing the node pods in the cluster using the below command the driver pods with kubectl get pods -n unity –no-headers=true \| awk ‘/unity-/{print $1}’\| xargs kubectl delete -n unity pod
Driver install or upgrade fails because of an incompatible Kubernetes version, even though the version seems to be within the range of compatibility. For example: `Error: UPGRADE FAILED: chart requires kubeVersion: >= 1.24.0 < 1.29.0 which is incompatible with Kubernetes 1.24.6-mirantis-1`	If you are using an extended Kubernetes version, see the helm Chart at `helm/csi-unity/Chart.yaml` and use the alternate `kubeVersion` check that is provided in the comments. Note that this is not meant to be used to enable the use of pre-release alpha and beta versions, which is not supported.
When a node goes down, the block volumes attached to the node cannot be attached to another node	1. Force delete the pod running on the node that went down 2. Delete the VolumeAttachment to the node that went down. Now the volume can be attached to the new node.
Standby controller pod is in crashloopbackoff state	Scale down the replica count of the controller pod’s deployment to 1 using `kubectl scale deployment <deployment_name> --replicas=1 -n <driver_namespace>`
fsGroupPolicy may not work as expected without root privileges for NFS only https://github.com/kubernetes/examples/issues/260	To get the desired behavior set “RootClientEnabled” = “true” in the storage class parameter
When both iSCSI IQNs and FC WWNs are present, host registrations on Unity systems will include all initiators. If only FC WWNs are present, a warning message will appear: ‘iSCSI Initiators’ cannot be retrieved.	Ensure only desired initiators are configured on the worker nodes to limit the initiators included in the host registrations

Unity XT

Mon, 01 Jan 0001 00:00:00 +0000

Release Notes - CSI Unity XT v2.13.0

New Features/Changes

There are no new features in this release.

Test Unity XT CSI Driver

Mon, 01 Jan 0001 00:00:00 +0000

Test deploying a simple Pod and PVC with Unity XT storage

In the repository, a simple test manifest exists that creates three different PersistentVolumeClaims using default NFS and iSCSI and FC storage classes and automatically mounts them to the pod.

Unity XT

Mon, 01 Jan 0001 00:00:00 +0000

Symptoms	Prevention, Resolution or Workaround
When you run the command `kubectl describe pods unity-controller-<suffix> –n unity`, the system indicates that the driver image could not be loaded.	You may need to put an insecure-registries entry in `/etc/docker/daemon.json` or login to the docker registry
The `kubectl logs -n unity unity-node-<suffix>` driver logs show that the driver can’t connect to Unity XT - Authentication failure.	Check if you have created a secret with correct credentials
`fsGroup` specified in pod spec is not reflected in files or directories at mounted path of volume.	fsType of PVC must be set for fsGroup to work. fsType can be specified while creating a storage class. For NFS protocol, fsType can be specified as `nfs`. fsGroup doesn’t work for ephemeral inline volumes.
Dynamic array detection will not work in Topology based environment	Whenever a new array is added or removed, then the driver controller and node pod should be restarted with command kubectl get pods -n unity –no-headers=true \| awk ‘/unity-/{print $1}’\| xargs kubectl delete -n unity pod when topology-based storage classes are used. For dynamic array addition without topology, the driver will detect the newly added or removed arrays automatically
If source PVC is deleted when cloned PVC exists, then source PVC will be deleted in the cluster but on array, it will still be present and marked for deletion.	All the cloned PVC should be deleted in order to delete the source PVC from the array.
PVC creation fails on a fresh cluster with iSCSI and NFS protocols alone enabled with error failed to provision volume with StorageClass “unity-iscsi”: error generating accessibility requirements: no available topology found.	This is because iSCSI initiator login takes longer than the node pod startup time. This can be overcome by bouncing the node pods in the cluster using the below command the driver pods with kubectl get pods -n unity –no-headers=true \| awk ‘/unity-/{print $1}’\| xargs kubectl delete -n unity pod
Driver install or upgrade fails because of an incompatible Kubernetes version, even though the version seems to be within the range of compatibility. For example: `Error: UPGRADE FAILED: chart requires kubeVersion: >= 1.24.0 < 1.29.0 which is incompatible with Kubernetes 1.24.6-mirantis-1`	If you are using an extended Kubernetes version, see the helm Chart at `helm/csi-unity/Chart.yaml` and use the alternate `kubeVersion` check that is provided in the comments. Note that this is not meant to be used to enable the use of pre-release alpha and beta versions, which is not supported.
When a node goes down, the block volumes attached to the node cannot be attached to another node	1. Force delete the pod running on the node that went down 2. Delete the VolumeAttachment to the node that went down. Now the volume can be attached to the new node.
Standby controller pod is in crashloopbackoff state	Scale down the replica count of the controller pod’s deployment to 1 using `kubectl scale deployment <deployment_name> --replicas=1 -n <driver_namespace>`
fsGroupPolicy may not work as expected without root privileges for NFS only https://github.com/kubernetes/examples/issues/260	To get the desired behavior set “RootClientEnabled” = “true” in the storage class parameter
When both iSCSI IQNs and FC WWNs are present, host registrations on Unity systems will include all initiators. If only FC WWNs are present, a warning message will appear: ‘iSCSI Initiators’ cannot be retrieved.	Ensure only desired initiators are configured on the worker nodes to limit the initiators included in the host registrations

Unity XT

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The CSI Driver for Dell Unity XT can be installed via the Dell CSM Operator. To deploy the Operator, follow the instructions available here.

Unity XT

Mon, 01 Jan 0001 00:00:00 +0000

Docker Hub images are discontinued. All deployments will be using images from quay.io.

The CSI Driver for Dell Unity XT can be deployed by using the provided Helm v3 charts and installation scripts on both Kubernetes and OpenShift platforms. For more detailed information on the installation scripts, review the script documentation.

Prerequisites

Before you install CSI Driver for Unity XT, verify the requirements that are mentioned in this topic are installed and configured.