MDBC - Unable to configure persistence

[DrissiReda]

What did you do to encounter the bug?
Steps to reproduce the behavior:
Put this in your MongoDBCommunity CRD:

spec:
  podSpec:
    persistence:
      single:
        storage: "12Gi"
    storageClass: storage-class-name

What did you expect?
Storage configuration to change

What happened instead?

This doesn't remain in the CR after creation.
Storage in the StatefulSet remains as default, meaning keeping both data and logs pvcs with the default sizes
and without a storageClass

Operator Information

• 1.6.1
• quay.io/mongodb/mongodb-community-server:8.2.3-ubi8

Kubernetes Cluster Information

• RKE2
• 1.33.6+rke2r1
• quay.io

Any idea how I can do this?

[fealebenpae]

Hey @DrissiReda,

You need to actually override the PVC template the operator creates inside the statefulset:

spec:
  statefulSet:
    spec:
      volumeClaimTemplates:
        - metadata:
            name: data-volume
          spec:
            accessModes: ["ReadWriteOnce"]
            storageClassName: "my-custom-storage-class"
            resources:
              requests:
                storage: 10Gi
        - metadata:
            name: logs-volume
          spec:
            accessModes: ["ReadWriteOnce"]
            storageClassName: "my-custom-storage-class"
            resources:
              requests:
                storage: 2Gi

However, it's not possible to use a single volume for both data and logs in MongoDBCommunity.

[DrissiReda]

Thanks I figured out how to do that, but I wanted to use a single volume for both. Is there a resource containing the complete reference of the MongDBCommunity CRD? I can't seem to find it.

[fealebenpae]

We don't have an API reference of the Community CRD, but you can check out the raw CustomResourceDefinition or perhaps the actual Go structs that define the CRD to see what fields are there on the spec.