Enable CSI

Summary and Key concepts

Summary:

The article outlines prerequisites and installation instructions for using Portworx with the CSI driver. It highlights required Kubernetes or OpenShift versions and discusses the importance of additional components known as "CSI Sidecars" for the proper functioning of the Portworx CSI Driver. The Portworx Operator is recommended for installation as it simplifies managing and upgrading both Kubernetes and Portworx versions. For OpenShift users, specific steps like adding the px-csi-account to the privileged security context are necessary. It also notes that certain features like Pure Storage FlashArray/FlashBlade DirectAccess depend on CSI being enabled.

Kubernetes Concepts:

• ServiceAccount: A Kubernetes object that allows processes to authenticate with the API server.

Portworx Concepts:

• Portworx Operator: Manages the lifecycle of the Portworx storage system, including installation and upgrades.

Prerequisites

Before you install and use Portworx with CSI, ensure you meet the prerequisistes:

• Openshift users must use Openshift 4.1 or higher
• Kubernetes users must use 1.13.12 or higher
• Certain features may require newer versions of Kubernetes or Portworx

Overview

The Portworx CSI Driver requires additional components called CSI Sidecars in order to function properly. To make sure these components and their dependencies are installed on your cluster, follow the instructions below.

Portworx CSI installed by default

Starting with the Portworx Operator, CSI is enabled by default for new Portworx installations. Due to the nature of CSI and its dependencies, it is highly recommend using the Portworx Operator for installation.

The Portworx Operator easily manages all CSI components based on your Kubernetes and Portworx versions. This makes upgrading Kubernetes and Portworx versions far easier.

note

Explicitly disabling CSI will also prevent the Pure Storage FlashArray/FlashBlade DirectAccess mode from working.

OpenShift installation

If you are using Openshift, you must add the px-csi-account service account to the privileged security context.

oc adm policy add-scc-to-user privileged system:serviceaccount:kube-system:px-csi-account

note

If you experience the error errorUnable to update cluster as v1alpha1 version of ... Remove these CRDs to allow the upgrade to proceed, follow this solution from RedHat.