search

nextcloud / helm

A community maintained helm chart for deploying Nextcloud on Kubernetes.
GNU Affero General Public License v3.0
328 stars 265 forks source link

mariadb persisted replicated pvc doesn't use the same storage class #123

Closed kyle-rf closed 2 months ago

kyle-rf commented 3 years ago

With mariadb enabled, replication set to true, and persistence enabled, I have specified a non-default storage class. The helm deployment creates the replicated pvc, but it doesn't use the same storage class as mariadb.master.persistence.storageClass. It uses the default.

So I have two pvcs with one being the specified storage class and one being the default storage class.

image

I believe this to be a bug. The second pvc should use the same storage class as the first pvc.

jessebot commented 1 year ago

Since we use the bitnami helm chart for mariadb, it looks like you'd need to set global.storageClass, according to the bitnami mariadb helm chart docs, so in the nextcloud helm chart values.yaml, to have the same storage class for both primary and secondary PVC, it would be:

mariadb:
  global:
    # this is just using your example, the class could be anything though
    storageClass: rook-ceph-block

Otherwise you need to set both mariadb.primary.persistence.storageClass and mariadb.secondary.persistence.storageClass.

If you'd like, you can also submit a PR to add these notes to the README and values.yaml. If you have further questions, I'm happy to help if you can please post your values.yaml that you're having trouble with and confirm you're on the latest helm chart version. Otherwise, I'll close this ticket due to inactivity in a couple weeks or so.