Installing from the OpenShift web console

When using the Red Hat OpenShift Container Platform, the operator for IBM block storage CSI driver can be installed directly from OpenShift web console, through the OperatorHub. Installing the CSI (Container Storage Interface) driver is part of the operator installation process.

Before you begin

Important: The operator must be installed in the kube-system project/namespace.

Note: If using you are not using the Red Hat OpenShift Container Platform, use the instructions detailed in Installing from GitHub through command line terminal.

About this task

The Red Hat OpenShift Container Platform uses the following SecurityContextConstraints for the following serviceAccounts:

Note: This data is for informational purposes only.

serviceAccount	SecurityContextConstraint
ibm-block-csi-operator	restricted
ibm-block-csi-controller-sa	anyuid
ibm-block-csi-node-sa	privileged

Procedure

From Red Hat OpenShift Container Platform Operators > OperatorHub, select Projects: kube-system.
Search for IBM block storage CSI driver.
Select the Operator for IBM block storage CSI driver and click Install.
The Operator Subscription form appears.
Set the Installation Mode to kube-system, under A specific namespace on the cluster.
Click Subscribe.
From Operators > Installed Operators, check the status of the Operator for IBM block storage CSI driver.
Wait until the Status is Up to date and then InstallSucceeded.

Note: While waiting for the Status to change from Up to date to InstallSucceeded, you can check the pod progress and readiness status from Workloads > Pods.
Once the operator installation progress has completed, click on the installed Operator for IBM block storage CSI driver.
Click Create Instance to create the IBM block storage CSI driver (IBMBlockCSI).

(Optional:) Edit the yaml file in the web console as follows:

apiVersion: csi.ibm.com/v1
kind: IBMBlockCSI
metadata:
  name: ibm-block-csi
spec:
  controller:
    repository: ibmcom/ibm-block-csi-driver-controller
    tag: 1.0.0
    imagePullPolicy: IfNotPresent
    affinity:
      nodeAffinity:
        requiredDuringSchedulingIgnoredDuringExecution:
          nodeSelectorTerms:
            - matchExpressions:
              - key: kubernetes.io/arch
                operator: In
                values:
                  - amd64
  node:
    repository: ibmcom/ibm-block-csi-driver-node
    tag: 1.0.0
    imagePullPolicy: IfNotPresent
    affinity:
      nodeAffinity:
        requiredDuringSchedulingIgnoredDuringExecution:
          nodeSelectorTerms:
            - matchExpressions:
              - key: kubernetes.io/arch
                operator: In
                values:
                  - amd64
  sidecars:
    - name: csi-node-driver-registrar
      repository: quay.io/k8scsi/csi-node-driver-registrar
      tag: v1.2.0
      imagePullPolicy: IfNotPresent
    - name: csi-provisioner
      repository: quay.io/k8scsi/csi-provisioner
      tag: v1.3.0
      imagePullPolicy: IfNotPresent
    - name: csi-attacher
      repository: quay.io/k8scsi/csi-attacher
      tag: v1.2.1
      imagePullPolicy: IfNotPresent
    - name: livenessprobe
      repository: quay.io/k8scsi/livenessprobe
      tag: v1.1.0
      imagePullPolicy: IfNotPresent

Click Create.

Wait until the Status is Running.

Status:
  Controller Ready:  true
  Node Ready:        true
  Phase:             Running
  Version:           1.0.0
Events:              <none>