#Astra-Trident - Storage Prefix based on Namespace.
1 messages · Page 1 of 1 (latest)
you can configure the prefix per-backend so it should be possible to give different trident backends to different tenants on your k8s cluster
i.e. you can have more than oneTridentBackendConfig object in your cluster
@onyx crypt Thank you for the input, have you been playing around with "Virtual Pools" as well and can share something there? 🙂
We will at least explore that path, and see how far it will takes us and we can share that later on.
I never had the need for Virtual Pools for any of our customers, most of them have only one or two ONTAP systems and want to separate them out. Virtual Pools are only useful if you have many similar ONTAP systems (say, 10 FAS systems and 5 AFF systems) and you want to have Trident automagically pick any of these so that the k8s user only has to deal with 2 backends/storage classes (HDD and SSD) instead of 15
The problem we are face is that we use flux to enable multi-tenancy in our cluster which gives namespaces to each tenant and with a lot of tenants it's not really convenient (all though doable) to create a storage class for each tenant sense a lot of them are developers and we would prefer if they all could just use the default storageclass.
But Im also thinking about writing an operator that will modify the comment metadata for the volume in netapp with the tenants name.
you can do that but then all your volumes would have the same prefix and you'd have to do the accounting/billing via the objects in k8s, and not via volumes on the NetApp... Or a comment, yes, that might also be possible (although my k8s knowledge is nowhere deep enough to judge that 😅 )
Yeahhh that why we asked the question here if trident has that feature or anything similar sense the writing you own operator is doable but not suuuper native.
A really cool feature that trident could do is to have a pvc prefix based on a label on the claim!