Configuring Storage for the Billing Database¶
Billing features require persistent storage. By default, the cluster's default StorageClass is used. If the cluster doesn't have a default storage class capable of provisioning a volume for billing, there are a few alternative ways to configure persistent storage.
Note: NFS should be used with caution. root-squash is incompatible, and other configurations may cause issues, such as mount options or NFS version constraints. See the MySQL documentation for details.
Configuring Billing to Use a Non-Default StorageClass¶
If the cluster has an alternative StorageClass suitable for the billing database, you can override the default StorageClass by adding the following flag to the helm install mmai command:
Configuring the Installation to Use a Predefined PVC¶
If the cluster administrator wants to manually define a PVC for the billing database, disable automatic PVC creation by setting the StorageClass to an empty string:
Configuring the Installation to Use a HostPath Mount¶
The billing database can be configured to use hostPath storage, which directly creates and mounts a directory on the host node to the billing database pod. To enable hostPath storage, add the following flag to the helm install mmai command:
By default, the directory /data/memverge/mmai/mysql-billing is used. This path can be overridden with the following flag: