Upgrade MSR

To use Mirantis Secure Registry (MSR) 3.0.x, you must perform a fresh installation, as it is not currently possible to upgrade to MSR 3.0.x from any MSR 2.x.x version. You can, though, upgrade from MSR 3.0.x to a later 3.0.x patch version.

Schedule your upgrade outside of peak hours to avoid any business impact, as brief interruptions may occur.

Note

Before upgrading from MSR 3.0.0 to a later patch version, you must confirm that the cert-manager component is version 1.7.2 or later:

helm history cert-manager

To upgrade cert-manager to version 1.7.2:

helm upgrade cert-manager jetstack/cert-manager \
  --version 1.7.2 \
  --set installCRDs=true

Important

Mirantis has transitioned to an OCI-based Helm registry for registry.mirantis.com. As a result, Helm repository management is no longer required. Commands that rely on Helm repository operations, such as helm repo update and helm upgrade, will fail with HTTP 4xx errors.

For both new installations and upgrades, use the OCI-based registry URL directly. To check for available upgrades, run helm upgrade --dry-run without specifying a version.

For more details, see the Helm documentation.

To upgrade to a new patch version:

  1. Run the following command: helm upgrade command:

    helm upgrade msr oci://registry.mirantis.com/msr/helm/msr --version <helm-chart-version> --set-file license=path/to/file/license.lic
    MSR version compatibility with Helm charts

    MSR 3.1 version

    Chart version

    3.1.12

    1.1.16

    3.1.11

    1.1.15

    3.1.10

    1.1.12

    3.1.9

    1.1.11

    3.1.8

    1.1.10

    3.1.7

    1.1.9

    3.1.6

    1.1.8

    3.1.5

    1.1.6

    3.1.4

    1.1.5

    3.1.3

    1.1.4

    3.1.2

    1.1.3

    3.1.1

    1.1.2

    3.1.0

    1.1.0

    3.0.12

    1.0.14

    3.0.11

    1.0.13

    3.0.10

    1.0.12

    3.0.9

    1.0.10

    3.0.8

    1.0.9

    3.0.7

    1.0.8

    3.0.6

    1.0.7

    3.0.5

    1.0.6

    3.0.4

    1.0.5

    3.0.3

    1.0.4

    3.0.2

    1.0.2

    3.0.1

    1.0.1

    3.0.0

    1.0.0

  2. Verify the installation of all MSR components.

    1. Verify that each Pod is in the Running state:

      kubectl get pods

    2. Troubleshoot any failing Pods by running the following command on each failed Pod:

      kubectl describe <pod-name>

    3. Review the Pod logs for more detailed results:

      kubectl logs <pod-name>