The following key components must be in place before you can install MSR on Kubernetes using the online method:

  • cert-manager

  • Postgres Operator

  • RethinkDB Operator

  • MSR Operator

To ensure that all of the key prerequisites are present:

  1. Install cert-manager:


    The cert-manager version must be 1.7.2 or later.

    helm upgrade --install cert-manager cert-manager \
         --repo \
         --version 1.12.3 \
         --set installCRDs=true
  2. Install Postgres Operator:


    The Postgres Operator version you install must be 1.9.0 or later, as all versions up through 1.8.2 use the PodDisruptionBudget policy/v1beta1 Kubernetes API, which is no longer served as of Kubernetes 1.25. This being the case, various MSR features may not function properly if a Postgres Operator prior to 1.9.0 is installed alongside MSR on Kubernetes 1.25 or later.

    helm upgrade --install postgres-operator postgres-operator \
         --repo \
         --version 1.10.0 \
         --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 add the following to the MSR custom resource manifest to provide the new instance with the name of the associated PersistentVolumeClaim:

          backend: 'persistentVolume'
            existingClaim: '<pre-existing-msr-pvc>'

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

  3. Install RethinkDB Operator:

    helm upgrade --install rethinkdb-operator rethinkdb-operator \
         --repo \
         --version 1.0.0
  4. Install MSR Operator:

    helm upgrade --install msr-operator msr-operator \
         --repo \
         --version 1.0.0