#How do you manage a growing number of K8S PVs with trident and keeping everything clean?

1 messages · Page 1 of 1 (latest)

kind willow
#

Hey all! I hope this is the correct place to talk about this.

So for context, I'm working with a few Kubernetes clusters set up on VMs in our vSphere environment. Since we have a NetApp storage, we figured it was a good idea to use trident to dynamically create volumes on the NetApp array. It's going great so far, but as things are going forward and more and more applications are deployed, I have difficulties to keep up with the growing volumes on the NetApp side. They're restricted to a specific SVM, but the names of the volume being completely random and (as far as I know) with no way of customising that (to indicate the application name linked to that volume for example).
With the way our applications evolve, some volumes tends to not be used anymore and stay on the NetApp array indefinitely with very few options to identify what the original use was for those volumes and keeping everything tidy and clean is a very picky and long process.

I have two storage classes : one that auto-deletes the PVs and volumes and another (for prod workloads) that retains the volumes if we delete the Kubernetes objects. So I'm mainly struggly with the later.

It may be because I'm still learning, but I didn't find anything in Trident's documentation regarding keeping everything organised, clear and clean.

fervent vale
#

Trident supports using 'labels' to identify PVs
https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
And 'storagePrefix' to place a prefix on the ONTAP volume name:
https://docs.netapp.com/us-en/trident/trident-use/ontap-nas-examples.html

You can map a specific storage class to a specific backend:
https://docs.netapp.com/us-en/trident/trident-use/ontap-nas-examples.html#map-backends-to-storageclasses
https://docs.netapp.com/us-en/trident/trident-reference/objects.html#how-do-the-objects-interact-with-one-another
https://docs.netapp.com/us-en/trident/trident-reference/objects.html#storage-pool-selection-attributes
"For example, a value for additionalStoragePools might look like:
ontapnas_192.168.1.100:aggr1,aggr2;solidfire_192.168.1.101:bronze"

I hope this is helpful.

kind willow
#

There's no way to create a volume on netapp with trident with a custom part in its name right? Appart from the prefix, which is linked to the backend configuration?

Thanks for the links

fervent vale
#

@kind willow I believe that is correct.

celest spire
#

If the PVC and then the PV is deleted from k8s, the corresponding volume in NetApp should be deleted automatically by the Trident CSI provisioner.