MSR 3.0.0 is a significant step forward, as you can now install the software to run on any Kubernetes distro 1.20 and above and deploy it using standard Helm techniques. As such, MSR now offers greater flexibility, as the orchestrator allocates compute resources and administers persistent storage rather than the MSR product itself.
This section outlines the most significant changes introduced to the product in the MSR 3.0.0 release.
MSR on Kubernetes¶
MSR 3.0.0 runs on any standard Kubernetes 1.20 and above distributions being deployed from a Helm chart.
While MSR 3.0.0 is not integrated with Mirantis Kubernetes Engine (MKE) as has been the case with previous versions, MSR continues running just as well on MKE as on any supported Kubernetes distribution.
MSR 3.0.0 has far greater flexibility than previous versions, as many resources such as storage are administered by the orchestrator rather than by the registry itself.
No dedicated nodes required¶
MSR 3.0.0 does not require deployment onto dedicated nodes, as was the case with previous versions.
Jobrunner workers are grouped into deployments¶
Jobrunner workers are grouped into deployments so that each worker in the deployment is configured with the same job capacity. This allows for easy scaling without needing to configure each worker individually. The number of jobrunner deployments can be customized as needed.
TLS certificates are configurable¶
By default, MSR 3.0.0 uses cert-manager to issue and rotate its server TLS certificate. Operators of the software can customize the certificate configuration, thus allowing a certificate from Let’s Encrypt to be automatically issued and rotated. Operators with more specialized requirements can take full control over management of the TLS certificate, using any tooling that can write the certificate and private key into a Kubernetes Secret.
MSR 3.0.0 watches for alterations to the certificate data and automatically reloads when it detects any change.
MSR Operations Guide: Use your own TLS certificates
The MSR CLI has undergone marked changes with the release of MSR 3.0.0. Chief
among the MSR CLI changes is the transition to the
msr executable name from
the previously used
dtr. In addition, due to the significant changes put
forward in MSR 3.0.0, the CLI introduces several new commands while also
removing a numberof legacy commands that are now unnecessary.
CLI commands that are new in MSR 3.0.0 include:
msr db-emergency-repair (formerly dtr emergency-repair)
The legacy MSR CLI commands that are no longer available are: