clean up persistence handling (use existingClaim settings instead of checking accessMode) #11

Merged

jessebot merged 1 commit from chore/clean-up-persistence into main

2024-11-17 14:48:09 +00:00

jessebot commented

2024-11-17 14:44:22 +00:00

(Migrated from github.com)

Changes

If you want to use an existing Persistent Volume Claim: instead of setting persistence.db.accessMode and persistence.models.accessMode to ReadWriteMany, you just set persistence.db.existingClaim and persistence.models.existingClaim. The reason behind this is that you can now specify the name of your existing claim and the the accessMode independently.

I also went through and fixed some more spacing issues with the persistence section of the StatefulSet.

# Changes If you want to use an existing Persistent Volume Claim: instead of setting `persistence.db.accessMode` and `persistence.models.accessMode` to `ReadWriteMany`, you just set `persistence.db.existingClaim` and `persistence.models.existingClaim`. The reason behind this is that you can now specify the name of your existing claim and the the accessMode independently. I also went through and fixed some more spacing issues with the persistence section of the StatefulSet.