- Run the following command to download the installation source files from GitHub:
- Run the following command to create the namespace called vxflexos:
- Collect information from the PowerFlex SDC by running the get_vxflexos_info.sh script.
- Copy the csi-vxflexos/values.yaml into a file called myvalues.yaml in the same directory as the csi-install.sh script.
- Edit myvalues.yaml to set the parameters like file system types, volume name prefix, and controller count, for the installation.
- Create a config.json for driver configuration. This file contains information like the PowerFlex system IP details and credentials.
- Run the following sh csi-install.sh command to proceed with the installation:
- Run the following commands to check the vxflexos namespace for running pods to verify it is deployed correctly:
For more information about CSI driver installation, see GitHub.
- Create the storage classes through the Rancher graphical UI.
- Ensure that the PowerFlex CSI driver is running on a Rancher Kubernetes cluster and the PowerFlex Storage classes are listed in the SUSE Rancher menu for any application that is launched in the SUSE Rancher Kubernetes cluster.
![](https://cdn-prod.scdn6.secure.raxcdn.com/static/media/346cfc6c-3aca-4bb4-8965-96a4e14ca160.png)
Figure 6. SUSE Rancher menu
![](https://cdn-prod.scdn6.secure.raxcdn.com/static/media/078cef6b-1829-4ca4-9ab2-7f2243a3f8a7.png)
Figure 7. Cluster explorer
- Test the deployment workflow of a simple pod on PowerFlex storage, For more information, see Test PowerFlex CSI Driver.
- Verify that the persistent volume is created in PowerFlex cluster using the Power Flex graphical user interface.
![](https://cdn-prod.scdn6.secure.raxcdn.com/static/media/9deccba4-924a-48c3-bfe4-f3a791c228d0.png)
Figure 8. PowerFlex graphical user interphase
- Verify the following output from SUSE Rancher UI and confirm that PowerFlex Persistent Volumes are used by the Kubernetes pods running under the test namespace:
![](https://cdn-prod.scdn6.secure.raxcdn.com/static/media/41479cc7-e1fe-4390-8b47-7938219acb4f.png)
Figure 9. Kubernetes pods running under test namespace