Installation Guide

Install CSI Driver

1. Create namespace:

      kubectl create namespace isilon
   

   This command creates a namespace called isilon. You can replace isilon with any name you prefer.

2. Create secret file:.

   a. Create a file called secret.yaml or pick a sample that has PowerScale array connection details:

   isilonClusters:
     - clusterName: "cluster2"
       username: "user"
       password: "password"
       endpoint: "1.2.3.4"
       isDefault: true
       endpointPort: "8080"
   

   • Update Parameters: Replace placeholders with actual values for your PowerScale array.
   • Add Blocks: If you have multiple PowerScale arrays, add similar blocks for each one.
   • Replication: If replication is enabled, make sure the secret.yaml includes all involved PowerScale arrays.
   
   b. After creating the secret.yaml, the following command can be used to create the secret,

   kubectl create secret generic isilon-creds -n isilon --from-file=config=secret.yaml
   

   Use the following command to replace or update the secret

   kubectl create secret generic isilon-creds -n isilon --from-file=config=secret.yaml -o yaml --dry-run | kubectl replace -f -
   

   Note: The user needs to validate the YAML syntax and array related key/values while replacing the isilon-creds secret. The driver will continue to use previous values in case of an error found in the YAML file.

3. Create isilon-certs-n secret.

   Please refer this section for creating cert-secrets.

   If certificate validation is skipped, empty secret must be created. To create an empty secret. Ex: empty-secret.yaml

   apiVersion: v1
   kind: Secret
   metadata:
     name: isilon-certs-0
     namespace: isilon
   type: Opaque
   data:
     cert-0: ""
   

   kubectl create -f empty-secret.yaml
   

4. Install Driver

   i. Create a CR (Custom Resource) for PowerScale using the sample files provided

   Starting from CSM version 1.16, users can utilize the spec.version parameter for automatic image management. No ConfigMap or custom registry configuration needed.
   
   For more details click on Advanced Image Configuration Options section.
   

   a. Minimal Configuration:

   apiVersion: storage.dell.com/v1
   kind: ContainerStorageModule
   metadata:
     name: isilon
     namespace: isilon
   spec:
     version: v1.16.1
     driver:
       csiDriverType: "isilon"
       forceRemoveDriver: true
   

   Refer the minimal sample files provided in respective CSM versions folder under samples here. Modify if needed.

   [OR]

   b. Detailed Configuration: Use the sample file for detailed settings or use Wizard to generate the sample file.

• Users should configure the parameters in CR. The following table lists the primary configurable parameters of the PowerScale driver and their default values:

Parameters

Parameter	Description	Required	Default
dnsPolicy	Determines the DNS Policy of the Node service	Yes	ClusterFirstWithHostNet
fsGroupPolicy	Defines which FS Group policy mode to be used, Supported modes None, File and ReadWriteOnceWithFSType. In OCP <= 4.16 and K8s <= 1.29, fsGroupPolicy is an immutable field.	No	“ReadWriteOnceWithFSType”
storageCapacity	Enable/Disable storage capacity tracking feature	No	false
Common parameters for node and controller
CSI_ENDPOINT	The UNIX socket address for handling gRPC calls	No	/var/run/csi/csi.sock
X_CSI_ISI_SKIP_CERTIFICATE_VALIDATION	Specifies whether SSL security needs to be enabled for communication between PowerScale and CSI Driver	No	true
X_CSI_ISI_PATH	Base path for the volumes to be created	Yes
X_CSI_ALLOWED_NETWORKS	Custom networks for PowerScale export. List of networks that can be used for NFS I/O traffic, CIDR format should be used	No	empty
X_CSI_ISI_AUTOPROBE	To enable auto probing for driver	No	true
X_CSI_ISI_NO_PROBE_ON_START	Indicates whether the controller/node should probe during initialization	Yes
X_CSI_ISI_VOLUME_PATH_PERMISSIONS	The permissions for isi volume directory path	Yes	0777
X_CSI_ISI_AUTH_TYPE	Indicates the authentication method to be used. If set to 1 then it follows as session-based authentication else basic authentication. If CSM Authorization is enabled, this value must be set to 1.	No	0
GOISILON_DEBUG	Enable/Disable gopowerscale library-level debugging.	No	false
Controller parameters
X_CSI_MODE	Driver starting mode	No	controller
X_CSI_ISI_ACCESS_ZONE	Name of the access zone a volume can be created in	No	System
X_CSI_ISI_QUOTA_ENABLED	To enable SmartQuotas	Yes
Node parameters
X_CSI_MAX_VOLUMES_PER_NODE	Specify the default value for the maximum number of volumes that the controller can publish to the node	Yes	0
X_CSI_MODE	Driver starting mode	No	node

ii. Create PowerScale custom resource:

kubectl create -f <input_sample_file.yaml>

This command will deploy the PowerScale driver in the namespace specified in the input YAML file.

5. Verify the installation as mentioned below

   • Check if ContainerStorageModule CR is created successfully using the command below:

     kubectl get csm/isilon -n isilon
     

   Check the status of the CR to verify if the driver installation is in the Succeeded state. If the status is not Succeeded, see the Troubleshooting guide for more information.

6. Create Storage Class

   apiVersion: storage.k8s.io/v1
   kind: StorageClass
   metadata:
     name: isilon
   provisioner: csi-isilon.dellemc.com
   reclaimPolicy: Delete
   allowVolumeExpansion: true
   parameters:
     AccessZone: System
     IsiPath: /ifs/data/csi
     RootClientEnabled: "false"
   volumeBindingMode: Immediate
   

   Refer Storage Class for different sample files.

   Run this command to create a storage class

     kubectl create -f < storage-class.yaml >
   

7. Create Volume Snapshot Class

   apiVersion: snapshot.storage.k8s.io/v1
   kind: VolumeSnapshotClass
   metadata:
      name: isilon-snapclass
   driver: csi-isilon.dellemc.com
   deletionPolicy: Delete
   parameters:
      IsiPath: /ifs/data/csi
   

   Refer Volume Snapshot Class for the sample files.

   Run this command to create a volume snapshot class

   kubectl create -f < volume-snapshot-class.yaml >
   

Note :

• “Kubelet config dir path” is not yet configurable in case of Operator based driver installation.
• Also, snapshotter and resizer sidecars are not optional to choose, it comes default with Driver installation.