Skip to main content
NetApp Stage KB

Trident's CSI support changed the previously practical volume naming scheme

Last Updated:

Applies to

  • Trident 19.07 and higher
  • Trident 19.04 with CSI beta implementation (not meant for production)


Changing from non-CSI to CSI implementation with Trident changes the flexvol naming in a way that inconviences previous usage of the ONTAP flexvols for:

  • storage admins to report on NAS volumes running full to the right kuberenetes application developer/maintainers
  • assign storage usage cost to the right cost centers, depending on namespace.

With the CSI usage, identifying the namespace and deployment requires accessing Trident and Kuberenetes based information:

  • take the Volume name (<storagePrefix>_<PVC>_<long_UUID>) from ONTAP and convert it to the PV syntax of Kuberenetes/OCP (pvc-<UUID>)
  • search from Kuberenetes/Openshift that PV to which PVC it ​​belongs
  • apply what the necessary functionality is from namespace and deployment (e.g. resizing the volume, or adding the data into a spreadsheet)

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.