Volume Classes

If you're moving from GCP to AWS for the first time (or vice versa), one common issue that is easy run into and hard to decipher is incorrectly setting the storageClassName on a PersistentVolume incorrectly. Whereas GCP provides the standard storage class for use across clusters, AWS instead uses g2 as its default storage class.

In order to create a single Helm Chart capable of serving customers on both AWS and GCP, we recommend dynamically selecting the relevant storage class based on the dynamically provided mm_platform interpolated value, or, if possible, not setting storageClassName at all.

Last updated