Resizing the MongoDB PVC on eks existing clusters using gp2 as the MongoDB volume storageclass

on existing clusters, the customer is responsible for the eks configuration while using gp2 as the mongodb volume storageclass (rather than openebs we use for embedded clusters), we must resize the volumes in eks so customers with the same existing cluster configuration can follow the following steps prerequisites ensure permissions to edit volumes and persistent volume claims (pvcs) within your eks environment confirm the ability to access the kots admin console and aws console from kots admin console update kots config and redeploy kots version with resized db log in to the kots admin console navigate to the settings or configuration section update the mongodb volume size field to the new desired size under the database configuration redeploy the kots version to apply the updated configuration note ensure that the updated size is reflected in the configuration to avoid discrepancies when kubernetes applies the volume size from common cluster update volume size in persistent volume configs resize volume in aws console (gp2 storage class) these steps provide a thorough approach for resizing mongodb volumes using gp2 in a cluster on eks