Workflow and configuration of management cluster upgrade

This section describes specifics of automatic upgrade workflow of a management cluster as well as provides configuration procedures that you may apply before and after automatic upgrade.

Automatic upgrade workflow

A management cluster upgrade to a newer version is performed automatically once a new Container Cloud version is released. For more details about the Container Cloud release upgrade mechanism, see: Container Cloud Reference Architecture: Release Controller.

The Operator can delay the Container Cloud automatic upgrade procedure for a limited amount of time or schedule upgrade to run at desired hours or weekdays. For details, see Schedule Mirantis Container Cloud updates.

Container Cloud remains operational during the management cluster upgrade. Managed clusters are not affected during this upgrade. For the list of components that are updated during the Container Cloud upgrade, see the Components versions section of the corresponding major Container Cloud release in Container Cloud Release Notes: Container Cloud releases.

When Mirantis announces support of the newest versions of Mirantis Container Runtime (MCR) and Mirantis Kubernetes Engine (MKE), Container Cloud automatically upgrades these components as well. For the maintenance window best practices before upgrade of these components, see MKE Documentation.

Since Container Cloud 2.23.2 (Cluster releases 12.7.1 and 11.7.1), the release update train includes patch release updates being delivered between major releases. Patch release updates also involve automatic upgrade of a management cluster. For details on the currently available patch releases, see Container Cloud Release Notes: Latest supported patch releases.

See also

• Container Cloud Reference Architecture: Upgrade workflow of a bare metal host operating system

• Inspect the history of a cluster and machine deployment or update

Update the bootstrap tarball after automatic cluster upgrade

Once the management cluster is upgraded to the latest version, update the original bootstrap tarball for successful cluster management, such as collecting logs and so on.

Select from the following options:

• For clusters deployed using Container Cloud 2.11.0 (Cluster releases 7.1.0 and 6.18.0) or later:

  ./container-cloud bootstrap download --management-kubeconfig <pathToMgmtKubeconfig> \
  --target-dir <pathToBootstrapDirectory>
  

• For clusters deployed using the Container Cloud release earlier than 2.11.0 (7.0.0, 6.16.0, or earlier), or if you deleted the kaas-bootstrap folder, download and run the Container Cloud bootstrap script:

  wget https://binary.mirantis.com/releases/get_container_cloud.sh
  
  chmod 0755 get_container_cloud.sh
  
  ./get_container_cloud.sh