Upgrade Mission Control using the embedded runtime
You can upgrade Mission Control to the latest version using the embedded runtime to take advantage of new features and improvements.
Upgrading Mission Control is an incremental process designed to minimize downtime of components.
Run an upgrade only on a single Control Plane or a Data Plane at any given time. You must upgrade all Data Plane clusters first, and then proceed to upgrade the Control Plane. |
After you select your environment to upgrade, select a Management node for the coordination of upgrade tasks.
Choose one of the following two modes to upgrade the core runtime for Mission Control:
- Online upgrade
-
Upgrades are performed with internet access available to the hosts.
- Offline upgrade
-
Upgrades are performed without internet access. This is also known as an airgap upgrade.
-
Online upgrade
-
Offline (airgap) upgrade
-
An existing embedded cluster installation.
-
Internet access on the nodes.
Download assets and run the upgrade script on the upgrade coordinator.
Choose one of the Management nodes in your Mission Control installation to be the upgrade coordinator. Initiate and run the upgrade process on this host.
-
Download the installation assets to all the nodes in your cluster:
curl -f https://replicated.app/embedded/mission-control/stable/VERSION_NUMBER -H "Authorization: LICENSE_ID" -o mission-control-stable.tgz
Replace the following:
-
VERSION_NUMBER
: Mission Control version number, for examplev1.7.0
. By default, uselatest
, or specify a version number, such asv1.7.0
, if you need to install a specific version. -
LICENSE_ID
: License ID to authenticate the download. The ID is available in your Mission Control license file.
-
-
Extract the installation assets:
tar xvzf mission-control-stable.tgz
-
Run the following upgrade script on the Management node:
sudo ./mission-control update
This script pushes images to the registry and creates a new version for deployment.
Results
✔ Application images are ready! ✔ Finished!
After you upgrade the core runtime, you can update the Mission Control application.
-
In the KOTS Admin Console, click Cluster Management. On the Dashboard tab under Version, the system displays the new update version as available.
-
Click Version history to view the available versions, and then click Deploy.
-
Complete the options in the Config step, and then click Next.
-
Complete the options in the Preflight checks step, and then click Next: Confirm and deploy.
-
Review the changes in the Review and Deploy step, and then click Deploy.
With all nodes and the core runtime upgraded, you can continue with accessing Mission Control.
-
An existing embedded cluster-based installation.
-
The airgap installer, which you can download from mission-control.tar.gz.
Choose one of the Management nodes in your Mission Control installation to be the upgrade coordinator. Download the assets and run the upgrade script on the upgrade coordinator.
Initiate and run the upgrade process on this host until the entire cluster is upgraded.
-
Download the upgrade assets:
curl -f 'https://replicated.app/embedded/mission-control/stable/VERSION_NUMBER?airgap=true' -H "Authorization: LICENSE_ID" -o mission-control-stable.tgz
Replace the following:
-
VERSION_NUMBER
: By default, uselatest
, or specify a version number, such asv1.7.0
, if you need to install a specific version. -
LICENSE_ID
: Your license ID. The ID is available in your Mission Control license file.
-
-
Extract the assets:
tar xvzf mission-control-stable.tgz
The
mission-control.tar.gz
tarball contains the following files:-
mission-control: Mission Control installer
-
license.yaml: Mission Control license file
-
mission-control.airgap: Mission Control airgap bundle
-
-
Run the upgrade script on the Management node:
sudo ./mission-control update --airgap mission-control.airgap
This script pushes images to the registry and creates a new version for deployment.
Results
✔ Application images are ready! ✔ Finished!
After you upgrade the core runtime, you can update the Mission Control application.
-
In the KOTS Admin Console, click Cluster Management. On the Dashboard tab under Version, the system displays the new update version as available.
-
Click Version history to view the available versions, and then click Deploy.
-
Complete the options in the Config step, and then click Next.
-
Complete the options in the Preflight checks step, and then click Next: Confirm and deploy.
-
Review the changes in the Review and Deploy step, and then click Deploy.
With all nodes and the core runtime upgraded, you can continue with accessing Mission Control.