MSR 2.9 Compatibility Matrix

Mirantis Secure Registry (MSR, and formerly Docker Trusted Registry) provides an enterprise grade container registry solution that can be easily integrated to provide the core of an effective secure software supply chain.

Support for MSR is defined in the Mirantis Cloud Native Platform Subscription Services agreement.

Operating system compatibility

MSR functionality is dependent on MKE, and MKE functionality is dependent on MCR. As such, MSR operating system compatibility is contingent on the operating system compatibility of the MCR versions with which your particular MKE version is compatible.

To determine MSR operating system compatibility:

  1. Access the MKE compatibility matrix and locate the version of MKE that you are running with MSR.

  2. Note the MCR versions with which that MKE version is compatible.

  3. Access the MCR compatibility matrix and locate the MCR versions that are compatible with your version of MKE to determine operating system compatibility.

Upgrade detail

MSR versions 2.9.0 through 2.9.16 are compatible only with MCR 23.x. Therefore, users running MSR version 2.9.16 or earlier must upgrade to MSR version 2.9.17 or later before upgrading to MCR 25.0.

Only perform the MSR upgrade once any correlating upgrades to Mirantis Kubernetes Engine (MKE) and/or Mirantis Container Runtime (MCR) have completed.

Mirantis recommends the following upgrade sequence:

  1. MCR

  2. MKE

  3. MSR

MSR

Kubernetes required

Compatible MKE versions

Compatible MCR versions

2.9.22

1.24 - 1.31 1

3.6.x, 3.7.x, 3.8.x

23.x, 25.x

2.9.21

1.24 - 1.27 1

3.6.x, 3.7.x, 3.8.x

23.x, 25.x

2.9.20

1.24 - 1.27 1

3.6.x, 3.7.x, 3.8.x

23.x, 25.x

2.9.19

1.24 - 1.27 1

3.6.x, 3.7.x, 3.8.x

23.x, 25.x

2.9.18

1.24 - 1.27 1

3.6.x, 3.7.x, 3.8.x

23.x, 25.x

2.9.17

1.24 - 1.27 1

3.6.x, 3.7.x, 3.8.x

23.x, 25.x

2.9.16

1.24 - 1.27 1

3.6.x, 3.7.x, 3.8.x

23.x

2.9.15

1.24 - 1.27 1

3.6.x, 3.7.x, 3.8.x

23.x

2.9.14

1.24 - 1.27 1

3.6.x, 3.7.x, 3.8.x

23.x

2.9.13

1.24 - 1.27 1

3.6.x, 3.7.x, 3.8.x

23.x

2.9.12

1.24 - 1.27 1

3.6.x, 3.7.x, 3.8.x

23.x

2.9.11

1.24 - 1.27 1

3.6.x, 3.7.x, 3.8.x

23.x

2.9.10

1.24 - 1.27 1

3.6.x, 3.7.x, 3.8.x

23.x

2.9.9

1.24 - 1.27 1

3.6.x, 3.7.x, 3.8.x

23.x

2.9.8

1.24 - 1.27 1

3.6.x, 3.7.x, 3.8.x

23.x

2.9.7

1.24 - 1.27 1

3.6.x, 3.7.x, 3.8.x

23.x

2.9.6

1.24 - 1.27 1

3.6.x, 3.7.x, 3.8.x

23.x

2.9.5

1.24 - 1.27 1

3.6.x, 3.7.x, 3.8.x

23.x

2.9.4

1.24 - 1.27 1

3.6.x, 3.7.x, 3.8.x

23.x

2.9.3

1.24 - 1.27 1

3.6.x, 3.7.x, 3.8.x

23.x

2.9.2 2

Not applicable

Not applicable

Not applicable

2.9.1

1.24 - 1.27 1

3.6.x, 3.7.x, 3.8.x

23.x

2.9.0

1.24 - 1.27 1

3.6.x, 3.7.x, 3.8.x

23.x
1(1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22)

Postgres Operator up through 1.8.2 uses the PodDisruptionBudget policy/v1beta1 Kubernetes API, which is no longer served as of Kubernetes 1.25. As such, various features of MSR may not function properly if Postgres Operator 1.8.2 or earlier is installed alongside MSR on Kube v1.25 or later.

2

MSR 2.9.2 was discontinued shortly after release due to an issue wherein bootstrapper panicked when performing manual operations in an unhealthy environment. The product enhancements and bug fixes planned for MSR 2.9.2 are a part of MSR 2.9.3, which also resolves the bootstrapper issue. Mirantis strongly recommends that customers who deployed MSR 2.9.2 upgrade to MSR 2.9.3 (or later).

Storage backends

MSR supports the following storage systems:

Persistent volume

  • NFS (v3 and v4)

  • Bind mount

  • Volume

Cloud storage providers

  • Amazon S3

  • Microsoft Azure

  • Google Cloud Storage

  • Alibaba Cloud Object Storage Service

Note

MSR cannot be deployed to Windows nodes.