PSC Virtualization & Container Integration 2

Question 1

What Kubernetes standard does Pure Storage use to provide dynamic volume provisioning for containers on both FlashArray and FlashBlade?

Accepted Answer

Container Storage Interface (CSI)

Answer

FlexVolume plugin API

Answer

in-tree Kubernetes storage driver

Answer

Container Network Interface (CNI)

Question 2

Pure Storage acquired which enterprise container data management company in 2020 to strengthen its Kubernetes storage portfolio?

Accepted Answer

Portworx

Answer

StorageOS

Answer

Rook

Answer

Longhorn

Question 3

Which Kubernetes access mode does the Pure Storage CSI driver support for FlashArray block volumes?

Accepted Answer

ReadWriteOnce (RWO), allowing the volume to be mounted read-write by a single node

Answer

ReadWriteMany (RWX), allowing concurrent read-write access from multiple pods

Answer

ReadOnlyMany (ROX), allowing shared read-only access across all cluster nodes

Answer

ReadWriteOncePod (RWOP), available only when using FlashArray NVMe-oF connections

Question 4

In a Kubernetes deployment with Pure Storage, what is the purpose of a StorageClass referencing the Pure Storage CSI provisioner?

Accepted Answer

It defines the backend array, access protocol, and parameters used when dynamically creating PersistentVolumes from PersistentVolumeClaims

Answer

It sets the Kubernetes RBAC permissions required for pods to access Pure Storage volumes

Answer

It configures the network path and VLAN used for storage traffic in the cluster

Answer

It schedules automated snapshot jobs for all PersistentVolumes on the referenced array

Question 5

Which Pure Storage product supports ReadWriteMany (RWX) access mode for shared persistent storage across multiple pods in Kubernetes?

Accepted Answer

FlashBlade, using NFS-based shared file storage

Answer

FlashArray//X, using NVMe-oF multi-path connections

Answer

FlashArray//C, using iSCSI multipath I/O

Answer

Pure1 Cloud Block Store, using object storage endpoints

Question 6

What happens to a backing Pure Storage volume when a Kubernetes PersistentVolumeClaim is deleted and the associated PersistentVolume has a reclaimPolicy of 'Delete'?

Accepted Answer

The CSI driver automatically deletes the volume from the FlashArray or FlashBlade

Answer

The volume is retained on the array and must be manually deleted by a storage administrator

Answer

The volume is converted to a snapshot for 30 days before automatic removal

Answer

The volume is moved to a Pure1 archive tier and retained for compliance purposes

Question 7

What is the recommended method for installing the Pure Storage CSI driver in a production Kubernetes cluster?

Accepted Answer

Using the official Pure Storage Helm chart to deploy and manage the CSI driver components

Answer

Manually copying CSI driver binaries to each Kubernetes node via SSH

Answer

Installing the driver as a kernel module on each node through the OS package manager

Answer

Embedding the driver directly into a custom Kubernetes distribution build