Skip to main content
NetApp Knowledge Base

why does cloned PVCs Retain Source Backend Despite Specified StorageClass?

  1. Last updated
    Jun 16, 2025
  2. Save as PDF
Views:
8
Visibility:
Public
Votes:
0
Category:
trident-openshift
Specialty:
snapx
Last Updated:
6/16/2025, 8:22:32 AM

Applies to

  • NetApp Trident
  • OpenShift Virtualization with CDI (Containerized Data Importer)

Answer

This behavior is due to PVC cloning logic in OpenShift Virtualization/CDI:
• A VM is created from a template, which uses a DataVolume or PVC originally created using ontap-san-economy driver.
• Even if a new PVC specifies the storage class unsing onta-san driver, the clone operation references the original volume’s data source (DataVolume) — which still retain metadata from ontap-san-economy.
• Trident handles the clone by honoring the original volume’s backend, thus placing the cloned PVC under the backend (ontap-san-economy), despite the specified StorageClass.

Additional Information

Cloned PVCs Retain Source Backend Despite Specified StorageClass #987

 

 

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.