Skip to main content
NetApp Knowledge Base

Igroup named NODE-TridentUUID is mapped to ONTAP-SAN volumes created via Trident

Views:
11
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:

Applies to

  • Astra Trident 22.07 or later
  • PersistentVolumeClaim(PVC) is created with ontap-san driver

Issue

ONTAP-SAN volumes created via Trident are mapped to per-node igroup named <NODE>-<Trident UUID> regardless of its backend definition
 
Example:
 
# kubectl get pvc
NAME                    STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
pvc-volume-ststest2-0   Bound    pvc-ed2ca871-e02a-4016-8eee-7a1943d986dd   1Gi        RWO            ontap-san      24m

::> lun mapping show
Vserver    Path                                                        Igroup                  LUN ID  Protocol
---------- ----------------------------------------------------------  ----------------------  ------  --------
iscsi_svm  /vol/trident_pvc_ed2ca871_e02a_4016_8eee_7a1943d986dd/lun0  <NODE>-<TridentUUID>         2  iscsi

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.