#Astra-Trident - Storage Prefix based on Namespace.

1 messages · Page 1 of 1 (latest)

ashen iron
#

Hi,

We are today building a multi-tenancy K8s cluster, we are using flux to tenant segmentation.

With that we find it difficult to tie a specific prefix to a tenant as this is on a cluster level and not namespace level today what we can see according to Astra doc

onyx crypt
#

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

ashen iron
#

@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.

onyx crypt
# ashen iron <@189749672921792512> Thank you for the input, have you been playing around with...

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

forest ruin
#

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.

onyx crypt
forest ruin