Documentation
  • Getting Started
  • Creating a Product
    • Products Overview
    • Making a Helm Chart
      • Converting from docker-compose
      • Interpolated Values
      • Image Pull Secrets
      • Cluster Ingress
      • SSL Certificates
    • Setting up the Registry
      • Google Container Registry
  • Deploying a Product
    • Deployments Overview
    • Deploying on AWS
    • Deploying on GCP
    • Deploying on Azure (beta)
  • Debugging
    • GCP Permissions Errors
    • Volume Classes
Powered by GitBook
On this page
  1. Debugging

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.

PreviousGCP Permissions Errors

Last updated 4 years ago