Mirantis Container Cloud (MCC) becomes part of Mirantis OpenStack for Kubernetes (MOSK)!
Starting with MOSK 25.2, the MOSK documentation set will cover all product layers, including MOSK management (formerly MCC). This means everything you need will be in one place. The separate MCC documentation site will be retired, so please update your bookmarks for continued easy access to the latest content.
Cluster update known issues¶
This section lists the cluster update known issues with workarounds for the Mirantis OpenStack for Kubernetes release 22.5.
[29438] Cluster update gets stuck during the Tungsten Fabric operator update
[27797] Cluster ‘kubeconfig’ stops working during MKE minor version update
[29438] Cluster update gets stuck during the Tungsten Fabric operator update¶
If the tungstenfabric-operator-metrics service was present on the cluster
in MOSK 22.4, the update to 22.5 can stuck due to absence
of correct labels for this service. As a workaround, delete the service
manually:
kubectl -n tf delete svc tungstenfabric-operator-metrics
[27797] Cluster ‘kubeconfig’ stops working during MKE minor version update¶
During update of a Container Cloud management cluster, if the MKE minor
version is updated from 3.4.x to 3.5.x, access to the cluster using the
existing kubeconfig fails with the You must be logged in to the server
(Unauthorized) error due to OIDC settings being reconfigured.
As a workaround, during the Container Cloud cluster update, use the
admin kubeconfig instead of the existing one. Once the update
completes, you can use the existing cluster kubeconfig again.
To obtain the admin kubeconfig:
kubectl --kubeconfig <pathToMgmtKubeconfig> get secret -n <affectedClusterNamespace> \
-o yaml <affectedClusterName>-kubeconfig | awk '/admin.conf/ {print $2}' | \
head -1 | base64 -d > clusterKubeconfig.yaml