Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

\uD83E\uDD14 Problem

MongoDB pods cannot start due to persistent volume mounting error.

\uD83C\uDF31 Solution

Redeploy MongoDB to use a new persistent volume.

  1. Run command: kubectl delete statefulset mongo -n <onelist namespace>

  2. Download the mongo.yaml file below.

3. Edit the mongo.yaml file. Change the persistent volume name to a new value that is different to the current value in your cluster. For example: mongo-persistent-volume-2.

4. Run command: kubectl apply -f mongo.yaml -n <onelist namespace>

5. New MongoDB pods will start and mount to a new persistent volume.

  • No labels