Skip to main content
NetApp Knowledge Base

Can existing Trident deployment be moved into a new namespace?

Views:
172
Visibility:
Public
Votes:
1
Category:
astra_trident
Specialty:
snapx
Last Updated:

Applies to

NetApp Trident

Answer

It is possible, but it would be a very manual process involving modifying retention policies, deleting & recreating PVCs, CRs, etc..
Therefore it would be unsupported and we strongly discourage it.

Trident’s metadata is maintained in Kubernetes Custom Namespace Definitions (CRD) that are namespaced. Installing Trident in a new namespace is equivalent to creating a completely fresh Trident install.
For Trident to be moved to a new namespace and still be cognizant of the PVCs it created you will need to move all Trident CRs to the destination namespace.
Typically there are no PVCs in the Trident namespace. PVCs will be in the application namespaces.

Additional Information

See the Trident Documentation

 

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.
Scan to view the article on your device