Frequently Asked Questions
This page answers common questions about PX-CSI, including feature support, resource configuration, and changes introduced in recent releases.
Is the pxctl CLI still supported?
The pxctl CLI was removed starting in PX-CSI 25.8.0.
Use Kubernetes-native resources like PersistentVolumeClaims (PVCs), PersistentVolumes (PVs), VolumeSnapshotClasses and VolumeSnapshots instead.
Where does PX-CSI store volume metadata?
PX-CSI stores volume metadata in Kubernetes CustomResourceDefinitions (CRDs) in the portworx namespace:
- PureVolume – volume metadata
- PureSnapshot – snapshot metadata
During an upgrade from 25.6.0 or earlier to 25.8.0 or later, PX-CSI automatically migrates metadata from KVDB to CRDs.
You can use the following commands to inspect the resources:
kubectl get purevolume -n portworx
kubectl get puresnapshot -n portworx
See PureVolume CRD reference and PureSnapshot CRD reference for more information.
How can I control resource limits, node placement, and tolerations?
Use the ComponentK8sConfig custom resource.
PX-CSI automatically creates a px-pure-csi-k8s-config Custom Resource. Configure resource limits, node selectors, node affinities, and tolerations in this custom resource instead of legacy StorageCluster configurations.
For more information, see Configure resource limits.
Are proxy volumes supported?
No. Proxy volumes are not supported starting in PX-CSI 25.8.0.
Before you upgrade, contact Portworx Support for assistance with migration or refactoring workflows that depend on proxy volumes.
How do I configure multiple iSCSI interfaces?
Add each interface to the iSCSI database, and set the PURE_ISCSI_ALLOWED_IFACES environment variable as a comma-separated list of interfaces. For more information, see Install Portworx CSI.
Does FBDA support an external backup provider?
No. FBDA does not support external backup providers.
How are changes to pure.json reflected in the Kubernetes cluster?
Restart both the CSI node plugin and CSI controller plugin pods to apply the changes.