Your customer wants to use their HPE Alletra Storage MP B10000 array to store persistent data for Kubernetes-based applications. After deploying the CSI driver using Helm and creating the secret with the command kubectl create -f hpe-backed.yaml, what is the next required step to enable the containerized applications to consume persistent volumes on the Alletra MP array?
Detailed Explanatio n:
Rationale for Correct Answe r:
After installing the HPE CSI driver and creating backend secrets, the next critical step is to define a StorageClass that references the backend driver and parameters. Without the StorageClass, Kubernetes cannot dynamically provision PersistentVolumes (PVs). Once the StorageClass is created, workloads can request storage using PersistentVolumeClaims (PVCs).
Distractors:
A: Helm repo update only refreshes Helm charts; it does not enable CSI provisioning.
B: A PVC requires a StorageClass to bind dynamically --- it cannot be created successfully beforehand.
C: Manually creating PVs is possible, but not the HPE best practice with CSI, which relies on StorageClass for dynamic provisioning.
Key Concept: Kubernetes CSI workflow: Secret StorageClass PVC Pod.
Shonda
5 days agoReena
11 days agoMalinda
16 days agoKallie
21 days agoSherell
26 days agoLorita
1 months ago