#Trident ANF minimum volume size

1 messages · Page 1 of 1 (latest)

patent pawn
#

My client needs additional throughput for their k8s clusters that they’re migrating from CVO to ANF so they need to start at 100Gi and would like to do it automatically rather than having to create manually.

They’re using the Trident Operator using the official Helm Chart to deploy.
Backend configs are defined as TridentBackendConfig object and being deployed by their CI/CD.

Is there an acceptable way to change the default minimum volume size for ANF from 50Gi to 100Gi?

When deploying 24.10 , it looks like the storage drivers are giving a default minimum of 50Gi and because their sizes in CVO are smaller than 50Gi, they’re just defaulting up to that when they used to default to 100Gi in previous versions. If they changed the MinimumANFVolumeSizeByte in azure_anf.go in the storage drivers of the trident-24.10.0 code from 53687091200 to 107374182400 would that work or would that break something? Is there another way to do it?

tawdry fjord
#

So you mean you created all your volumes without an explicit size and just used the default? I would always specify the expected size in the PVC explicitly