With the upcoming end-of-life (EOL) of MSR 3.1.x, Mirantis encourages you to upgrade to the latest supported version to ensure continued support and security updates.

Upgrade on Kubernetes using the MSR Operator¶

To upgrade from MSR 3.0.x to 3.1.x, use the Mirantis Migration Tool (MMT).

Tip

Third-party components are not upgraded alongside MSR, which means they can become vulnerable to security breaches and exploits. To mitigate this risk, Mirantis strongly recommends upgrading cert-manager and Postgres Operator before proceeding with the MSR upgrade.

Run the following command to upgrade cert-manager and Postgres Operator:

helm upgrade cert-manager cert-manager \
     --repo https://charts.jetstack.io \
     --version <version> \
     --set installCRDs=true

helm upgrade postgres-operator postgres-operator \
     --repo https://opensource.zalando.com/postgres-operator/charts/postgres-operator/ \
     --version <version> \
     --set configKubernetes.spilo_runasuser=101 \
     --set configKubernetes.spilo_runasgroup=103 \
     --set configKubernetes.spilo_fsgroup=103

To upgrade to a new patch version:

Edit the custom resource manifest to include the MSR version to which you plan to upgrade:
```
spec:
  image:
    tag: <3.1.x>
```

Apply the changes to the custom resource:

kubectl apply -f cr-sample-manifest.yaml

Verify completion of the reconciliation process for the custom resource:

kubectl get msrs.msr.mirantis.com
kubectl get rethinkdbs.rethinkdb.com