Skip to main content
NetApp Knowledge Base

How to attach the same Trident created PVC to multiple k8s clusters

  1. Last updated
  2. Save as PDF
Views:
520
Visibility:
Public
Votes:
1
Category:
astra_trident
Specialty:
snapx
Last Updated:

Applies to

  • Astra Trident
  • Kubernetes (k8s)
    • Persistent Volumes (PV)
    • Persistent Volume Claims (PVC)

Description

This process could be for ongoing Read-Write-Many (RWM) access to unstructured data that is shared across pods residing in multiple k8s clusters, or it could be for moving an application between k8s clusters in a gradual fashion, while maintaining access to the unstructured data throughout the application migration.

Requirements
  • Don't use "autoExportPolicy" and "autoExportCIDRs" in the Trident backend definition.  Use an "exportPolicy" in the backend definition that covers the worker nodes in both k8s clusters, and manage the NFS clients in this export policy list manually (or use a subnet level export).
  • Set "reclaimPolicy: Retain" in the storage class that will have volumes shared between k8s clusters.  This means you will have to manually remove k8s PVs and storage volumes when they are ready to be deleted.  
  • Consider using a unique "storagePrefix" in the backend, and map storage classes to it, for storage classes that will have volumes shared between k8s clusters.  Consider doing the same for any backends using the same SVM that will *not* have volumes shared between k8s clusters.

 

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.