Release Notes

This document describes the latest changes, enhancements, known issues, and fixes for Mirantis Secure Registry (MSR) for versions 2.9.x.

• 2.9.22
• 2.9.21
• 2.9.20
• 2.9.19
• 2.9.18
• 2.9.17
• 2.9.16
• 2.9.15
• 2.9.14
• 2.9.13
• 2.9.12
• 2.9.11
• 2.9.10
• 2.9.9
• 2.9.8
• 2.9.7
• 2.9.6
• 2.9.5
• 2.9.4
• 2.9.3
• 2.9.2 (discontinued)
• 2.9.1
• 2.9.0

Considerations

• 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.

• CentOS 8 entered EOL status as of 31-December-2021. For this reason, Mirantis no longer supports CentOS 8 for all versions of MSR. We encourage customers who are using CentOS 8 to migrate onto any one of the supported operating systems, as further bug fixes will not be forthcoming.

• In developing MSR 2.9.x, Mirantis has been transitioning from legacy Docker Hub-issued licenses to JWT licenses, as detailed below:

  • Versions 2.9.0 to 2.9.3: Docker Hub licenses and JWT licenses

  • Versions 2.9.4 and later: JWT licenses only

• When malware is present in customer images, malware scanners operating on MSR nodes at runtime can wrongly report MSR as a bad actor. If your malware scanner detects any issue in a running instance of MSR, refer to Scan images for vulnerabilities.

Note

The Mirantis Migration Tool (MMT) release notes are included within the Migration Guide.