Trident's CSI support changed the previously practical volume naming scheme
Applies to
- Trident 19.07 and higher
- Trident 19.04 with CSI beta implementation (not meant for production)
Issue
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)