Run install command

Important

The default credentials for MSR are:

  • User name: admin

  • password: password

As the Helm chart values include the default MSR credentials information, Mirantis strongly recommends that you change these credentials immediately following installation.

Beginning with MSR 3.1.10, you can set your password during installation using the enzi.adminPassword parameter. Alternatively, you can define the enzi.adminPassword parameter in the values.yaml file in advance of MSR installation. Be aware that the enzi.adminPassword parameter is only used during MSR installation and does not affect upgrades.

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.

  1. Use a Helm chart to install MSR:

    helm install msr oci://registry.mirantis.com/msr/helm/msr \
    --version <helm-chart-version> \
    --set-file license=path/to/file/license.lic \
    --set enzi.adminPassword=<my-password> \
    -f my_msr_values.yaml
    

    Note

    If the installation fails and MSR Pods continue to run in your cluster, it is likely that MSR failed to complete the initialization process, and thus you must reinstall MSR. To delete the Pods and completely uninstall MSR:

    1. Delete any running msr-initialize Pods:

      kubectl delete job msr-initialize
      
    2. Delete any remaining Pods:

      helm uninstall msr
      
  2. Verify the success of your MSR installation.

    1. Verify that all msr-* Pods are in the running state. For more detail, refer to check-the-pods-offline-helm

    2. Log into the MSR web UI.

    3. Log into MSR from the command line:

      docker login <private-ip>
      
    4. Push an image to MSR using docker push.

  3. Optional. Disable outgoing connections in the MSR web UI Admin Settings. MSR offers outgoing connections for the following tasks:

    • Analytics reporting

    • New version notifications

    • Online license verification

    • Vulnerability scanning database updates

See also

Helm official documentation: Helm Install