Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
NetApp Knowledge Base

Can existing Trident deployment be moved into a new namespace?

Views:
83
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
cloud
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

 

Scan to view the article on your device