This section also outlines still valid known issues from previous Container Cloud releases.
 A cluster deployment or update fails with not ready compose deployments¶
A managed cluster deployment, attachment, or update to a Cluster release with
MKE versions 3.3.13, 3.4.6, 3.5.1, or earlier may fail with the
compose pods flapping (
ready > terminating > pending) and with the
following error message appearing in logs:
'not ready: deployments: kube-system/compose got 0/0 replicas, kube-system/compose-api got 0/0 replicas' ready: false type: Kubernetes
Disable Docker Content Trust (DCT):
Access the MKE web UI as admin.
Navigate to Admin > Admin Settings.
In the left navigation pane, click Docker Content Trust and disable it.
Restart the affected deployments such as
coredns, and so on:
kubectl -n kube-system delete deployment <deploymentName>
Once done, the cluster deployment or update resumes.
 Deletion of a node with ironic Pod is stuck in the Terminating state¶
During deletion of a manager machine running the
ironic Pod from a bare
metal management cluster, the following problems occur:
All Pods are stuck in the
ironicPod fails to start
The related bare metal host is stuck in the
As a workaround, before deletion of the node running the
cordon and drain the node using the kubectl cordon <nodeName> and
kubectl drain <nodeName> commands.
 Region deletion failure after regional deployment failure¶
If a baremetal-based regional cluster deployment fails before pivoting is done, the corresponding region deletion fails.
Using the command below, manually delete all possible traces of the failed
regional cluster deployment, including but not limited to the following
objects that contain the
kaas.mirantis.com/region label of the affected
kubectl delete <objectName> -l kaas.mirantis.com/region=<regionName>
Do not use the same region name again after the regional cluster deployment failure since some objects that reference the region name may still exist.
Container Cloud web UI¶
 Inability to set a custom value for a predefined node label¶
During machine creation using the Container Cloud web UI, a custom value for a node label cannot be set.
As a workaround, manually add the value to