Can we share the same ONTAP backend SVM for multiple backends on the same Kubernetes cluster? For example, can we use multiple ONTAP SAN backends for the same SVM or multiple ONTAP NAS backends for the same SVM? Any advice would be appreciated. Thanks."
#trident -- share the same ONTAP backend SVM for multiple backends on the same Kubernetes cluster?
silk dune
dusty thorn
AFAIK, there is nothing in Trident that prevents using same SVM by multiple backends. However, a backend config points to an SVM. Trident recommends using dedicating SVMs. Backend config parameters are for the SVM itself, These parameters would need to agree across the different backends or there will be conflicts. Please refer to the docs BP page for considerations. https://docs.netapp.com/us-en/trident/trident-reco/storage-config-best-practices.html#use-svms-dedicated-to-trident and the backend configs pages https://docs.netapp.com/us-en/trident/trident-use/backends.html. Hope this is helpful.
fossil vessel
Before creating multiple backends, Did you consider using Virtual Pools? https://docs.netapp.com/us-en/trident/trident-concepts/virtual-storage-pool.html
obtuse bobcat
also, if you want to differentiate objects in the same SVM, you can set a specific prefix per trident backend
silk dune
Before creating multiple backends, Did you consider using Virtual Pools? https:/...
@fossil vessel Users are trying to reduce numbers of svm and lif, parameters other than prefix will be the same