You must have the following key components in place before you can install MSR using the online method: a Kubernetes platform, cert-manager, and the Postgres Operator.

  1. Install and configure your Kubernetes distribution.

  2. Ensure that the default StorageClass on your cluster supports the dynamic provisioning of volumes. If necessary, refer to the Kubernetes documentation Change the default StorageClass.

    If no default StorageClass is set, you can specify a StorageClass for MSR to use by providing the following additional parameters to MSR when running the helm install command:

    --set postgresql.volume.storageClass=<my-storageclass>
    --set rethinkdb.cluster.persistentVolume.storageClass=<my-storageclass>

    The first of these three parameters is only applicable when you install MSR with a persistentVolume back end, the default setting:


    MSR creates PersistentVolumeClaims with either the ReadWriteOnce or the ReadWriteMany access modes, depending on the purpose for which they are created. Thus the StorageClass provisioner that MSR uses must be able to provision PersistentVolumes with at least the ReadWriteOnce and ReadWriteMany access modes.

    The <release-name> PVC is created by default with the ReadWriteMany access mode. If you choose to install MSR with a persistentVolume back end, you can override this default access mode with the following parameter when running the helm install command:

  3. Install cert-manager:

    helm repo add jetstack
    helm repo update
    helm install cert-manager jetstack/cert-manager \
       --version 1.7.2 \
       --set installCRDs=true
  4. Install Postgres Operator, including spilo_* parameters:

    helm repo add postgres-operator \
    helm repo update
    helm install postgres-operator postgres-operator/postgres-operator \
      --version 1.7.1 \
      --set configKubernetes.spilo_runasuser=101 \
      --set configKubernetes.spilo_runasgroup=103 \
      --set configKubernetes.spilo_fsgroup=103


By default, MSR uses the persistent volume claims detailed in Volumes.

If you have a pre-existing PersistentVolume that contains image blob data that you intend to use with a new instance of MSR, you can use Helm to provide the new instance with the name of the associated PersistentVolumeClaim:


This setting indicates the <release-name> PVC referred to in volumes.

See also