Skip to main content
NetApp Knowledge Base

Trident does not create an Export Policy for cloned PV if scheduled to a new node

  1. Last updated
  2. Save as PDF
Views:
135
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
SNAPX
Last Updated:

Applies to

  • Astra Trident [Trident] version 25.02.1
  • ONTAP-NAS volumes
  • Persistent Volume [PV]

Issue

Trident version 25.02.1 is unable to create an Export Policy rule for a cloned PV (created from a snapshot or annotations) if the PV is scheduled/attached to a new node (different from the node where the parent node is scheduled). This issue is observed for ONTAP-NAS volumes.

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.