2.25.0

The Mirantis Container Cloud major release 2.25.0:

• Introduces support for the Cluster release 17.0.0 that is based on the Cluster release 16.0.0 and represents Mirantis OpenStack for Kubernetes (MOSK) 23.3.

• Introduces support for the Cluster release 16.0.0 that is based on Mirantis Container Runtime (MCR) 23.0.7 and Mirantis Kubernetes Engine (MKE) 3.7.1 with Kubernetes 1.27.

• Introduces support for the Cluster release 14.1.0 that is dedicated for the vSphere provider only. This is the last Cluster release for the vSphere provider based on MKE 3.6.6 with Kubernetes 1.24.

• Does not support greenfield deployments on deprecated Cluster releases of the 15.x and 14.x series. Use the latest available Cluster releases of the series instead.

  Caution

  Make sure to update the Cluster release version of your managed cluster before the current Cluster release version becomes unsupported by a new Container Cloud release version. Otherwise, Container Cloud stops auto-upgrade and eventually Container Cloud itself becomes unsupported.

This section outlines release notes for the Container Cloud release 2.25.0.

• Enhancements
  • Container Cloud Bootstrap v2
  • General availability for ‘MetalLBConfigTemplate’ and ‘MetalLBConfig’ objects
  • Manual IP address allocation for bare metal hosts during PXE provisioning
  • Status of infrastructure health for bare metal and OpenStack providers
  • General availability for RHEL 8.7 on vSphere-based clusters
  • Automatic cleanup of old Ubuntu kernel packages
  • Configuration of a custom OIDC provider for MKE on managed clusters
  • The admin role for management cluster
  • General availability for graceful machine deletion
  • General availability for parallel update of worker nodes
• Addressed issues
• Known issues
  • Bare metal
    • [35089] Calico does not set up networking for a pod
    • [33936] Deletion failure of a controller node during machine replacement
    • [24005] Deletion of a node with ironic Pod is stuck in the Terminating state
  • OpenStack
    • [37634] Cluster deployment or upgrade is blocked by all pods in ‘Pending’ state
  • IAM
    • [37766] Sign-in to the MKE web UI fails with ‘invalid parameter: redirect_uri’
  • LCM
    • [31186,34132] Pods get stuck during MariaDB operations
    • [32761] Node cleanup fails due to remaining devices
    • [30294] Replacement of a master node is stuck on the calico-node Pod start
    • [5782] Manager machine fails to be deployed during node replacement
    • [5568] The calico-kube-controllers Pod fails to clean up resources
  • Ceph
    • [34820] The Ceph ‘rook-operator’ fails to connect to RGW on FIPS nodes
    • [26441] Cluster update fails with the MountDevice failed for volume warning
  • Update
    • [37268] Container Cloud upgrade is blocked by a node in ‘Prepare’ or ‘Deploy’ state
    • [36928] The helm-controller Deployment is stuck during cluster update
    • [33438] ‘CalicoDataplaneFailuresHigh’ alert is firing during cluster update
• Components versions
• Artifacts
  • Bare metal artifacts
  • Core artifacts
  • IAM artifacts
• Security notes
• Update notes
  • Pre-update actions
    • Upgrade to Ubuntu 20.04 on baremetal-based clusters
    • Configure managed clusters with the etcd storage quota set
    • Allow the TCP port 12392 for management cluster nodes
  • Post-update actions
    • Migrate Ceph cluster to address storage devices using by-id
    • Point DHCP relays on routers to the new dhcp-lb IP address

See also

• Cluster releases (managed)

• Releases summary

• Deprecation notes

• Patch releases