Mirantis Container Cloud (MCC) becomes part of Mirantis OpenStack for Kubernetes (MOSK)!
Starting with MOSK 25.2, the MOSK documentation set covers all product layers, including MOSK management (formerly Container Cloud). This means everything you need is in one place. Some legacy names may remain in the code and documentation and will be updated in future releases. The separate Container Cloud documentation site will be retired, so please update your bookmarks for continued easy access to the latest content.
Verify the management cluster status before MOSK update¶
Before you start updating your managed clusters, Mirantis recommends verifying that the associated management cluster is upgraded successfully.
To verify that the management cluster is upgraded successfully:
Using
kubeconfig
of the management cluster, verify the Cluster release version of the management cluster machines:for i in $(kubectl get lcmmachines | awk '{print $1}' | sed '1d'); do echo $i; kubectl get lcmmachines $i -o yaml | grep release | tail -1; done
Example of system response:
master-0 release: 14.0.0+3.6.5 master-1 release: 14.0.0+3.6.5 master-2 release: 14.0.0+3.6.5
Obtain the name of the latest available MOSK management release object:
kubectl get kaasrelease
Example of system response:
NAME AGE kaas-2-15-0 63m kaas-2-14-0 40d
Using the name of the latest MOSK management release object, obtain the latest available Cluster release version:
kubectl get -o yaml clusterrelease $(kubectl get kaasrelease kaas-2-15-0 -o yaml | egrep "^ +clusterRelease:" | cut -d: -f2 | tr -d ' ') | egrep "^ version:"
Example of system response:
version: 14.0.0+3.6.4
Compare the output obtained in the previous step with the output from the first step. The Cluster releases must match. If this is not the case, contact Mirantis support for further details.
Proceed to Step 2. Initiate MOSK cluster update.