Using FlashArray as Part of an NKP Cluster Deployment

Configuring FlashArray During NKP Cluster Creation

FlashArray integration is set at cluster creation time, whether the cluster is deployed using:

• CLI (nkp create cluster nutanix)

• Nutanix Marketplace (Management Cluster Deployment)

• NKP Kommander (Workload Cluster deployment)

Two CSI configuration settings determine how FlashArray-backed storage will be used:

• CSI Storage Container selection

• CSI attachment model (guest vs hypervisor attached)

NKP CLI Deployment

When deploying an NKP cluster using:

nkp create cluster nutanix

FlashArray integration is primarily set by two CSI-related flags:

• --csi-storage-container

• --csi-hypervisor-attached-volumes

Selecting the FlashArray-Backed Storage Container

The --csi-storage-container flag determines where Persistent Volumes will be provisioned.

Example:

--csi-storage-container "<flasharray-backed-container>"

Choosing the CSI Attachment Mode

The --csi-hypervisor-attached-volumes flag controls how Nutanix Volume Groups are attached to Kubernetes worker node VMs.

Example (with recommended default):

--csi-hypervisor-attached-volumes=false

Values:

• false → Guest VM-attached

• true → Hypervisor-attached

For most FlashArray-backed NKP environments:

• Guest-attached (false) is the recommended default.

• Hypervisor-attached should be selected only when there is a specific validated performance or security requirement.

• Additional details regarding the operational differences and failover behavior between guest-attached and hypervisor-attached volumes are provided later in this guide.

Marketplace / Kommander UI Deployment

Nutanix Kubernetes Platform deployment can be done via the following UI options:

• Nutanix Marketplace (NKP Management Cluster creation)

• NKP Kommander (NKP Workload Cluster creation)

You will be prompted to select a Storage Container as part of the cluster configuration workflow.

To ensure PVs are backed by FlashArray:

• Select the storage container that is backed by FlashArray.

• The container name must match the name shown in Prism Central (or Prism Element).

Example FlashArray Storage Container Selection:

To locate the storage container name:

• Navigate to Storage → Storage Containers

• FlashArray-backed containers appear under External Storage

If a local or non-FlashArray container is selected, Persistent Volumes will not be backed by FlashArray for that NKP cluster by default.

Choosing the CSI Attachment Mode

During cluster creation in the UI, you will also see a dropdown option for Hypervisor-Attached Volumes.

This setting corresponds to the CLI flag:

--csi-hypervisor-attached-volumes

Recommended setting for most FlashArray-backed NKP environments:

• False (Guest VM-attached volumes) → Recommended default

• True (Hypervisor-attached volumes) → Use only when there is a specific validated performance requirement

Example Volume Attachment Screenshot (recommended default)

Additional details regarding operational differences and failover behavior between guest-attached and hypervisor-attached volumes are provided later in this guide.

Verifying FlashArray Backing After NKP Cluster Deployment

After cluster deployment, verify that the default StorageClass is mapped to the intended container.

Run:

kubectl get sc nutanix-volume -o yam

Confirm via the output:

• provisioner: csi.nutanix.com

• storageContainer: <flasharray-backed-container>

• storageType: NutanixVolumes

This confirms that new PVCs will provision Nutanix Volume Groups in the specified storage container.

You can further verify in Prism Central by locating the Volume Group created for a PVC during NKP cluster creation and confirm it resides in the FlashArray-backed storage container.