Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
NetApp Knowledge Base

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

Views:
36
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:

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)
Scan to view the article on your device
CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support