Configuring the internal database

The Helm chart provides a PostgreSQL internal database to persist the data.

An internal database can use a predefined persistent volume claim (PVC) or Kubernetes dynamic provisioning.

Predefined PVC

The default configuration. The Kubernetes binding process selects a volume based on the accessMode and size.

  • internalDatabase.persistence.enabled: true (default)
  • internalDatabase.persistence.useDynamicProvisioning: false (default)
  • internalDatabase.secretCredentials (required). The database uses the credentials of the secret.

In this case, one PersistentVolume (PV) needs to be created before you install the chart. For more information, see Preparing to install Operational Decision Manager.

Kubernetes dynamic provisioning
Dynamic provisioning uses the default storageClass defined by the Kubernetes admin or by using a custom storageClass that overrides the default. You must change the default value for dynamic provisioning from false to true.
  • internalDatabase.persistence.enabled: true (default)
  • internalDatabase.persistence.useDynamicProvisioning: true
  • internalDatabase.secretCredentials (required). The database uses the credentials of the secret.
  • Specify a custom storageClassName per volume or leave the value empty for the internalDatabase.persistence.storageClassName parameter to use the default storageClass.