2.24.0

Important

Container Cloud 2.24.0 has been successfully applied to a certain number of clusters. The 2.24.0 related documentation content fully applies to these clusters.

If your cluster started to update but was reverted to the previous product version or the update is stuck, you automatically receive the 2.24.1 patch release with the bug fixes to unblock the update to the 2.24 series.

There is no impact on the cluster workloads. For details on the patch release, see 2.24.1.

The Mirantis Container Cloud GA release 2.24.0:

• Introduces support for the Cluster release 14.0.0 that is based on Mirantis Container Runtime 20.10.17 and Mirantis Kubernetes Engine 3.6.5 with Kubernetes 1.24.

• Supports the latest major and patch Cluster releases of the 12.7.x series that supports Mirantis OpenStack for Kubernetes (MOSK) 23.1 series.

• Does not support greenfield deployments on deprecated Cluster releases 12.7.3, 11.7.4, or earlier patch releases, 12.5.0, or 11.7.0. 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.24.0.

• Enhancements
  • Automated upgrade of operating system on bare metal clusters
  • Support for WireGuard on bare metal clusters
  • MetalLB configuration changes for bare metal and vSphere
  • Support for RHEL 8.7 on the vSphere provider
  • Custom flavors for Octavia on OpenStack-based clusters
  • Deletion of persistent volumes during an OpenStack-based cluster deletion
  • Support for Keycloak Quarkus
  • Custom host names for cluster machines
  • Parallel update of worker nodes
  • Cache warm-up for managed clusters
  • Support for auditd
  • Enhancements for TLS certificates configuration
  • Graceful cluster reboot using web UI
  • Creation and deletion of bare metal host credentials using web UI
  • Node labeling improvements in web UI
  • Documentation enhancements
• Addressed issues
• Known issues
  • Bare metal
    • [36131] Changes in ‘IpamHost’ are not propagated to ‘LCMMachine’
    • [35429] The WireGuard interface does not have the IPv4 address assigned
    • [34280] No reconcile events generated during cluster update
    • [34210] Helm charts installation failure during cluster update
    • [33936] Deletion failure of a controller node during machine replacement
    • [24005] Deletion of a node with ironic Pod is stuck in the Terminating state
    • [20736] Region deletion failure after regional deployment failure
  • LCM
    • [31186,34132] Pods get stuck during MariaDB operations
    • [32761] Node cleanup fails due to remaining devices
    • [34247] MKE backup fails during cluster update
    • [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
    • [34599] Ceph ‘ClusterWorkloadLock’ blocks upgrade from 2.23.5 to 2.24.1
    • [26441] Cluster update fails with the MountDevice failed for volume warning
  • Update
    • [33438] ‘CalicoDataplaneFailuresHigh’ alert is firing during cluster update
• Components versions
• Artifacts
• Security notes
• Update notes
  • Pre-update actions
    • Update L2 templates on existing bare metal clusters

See also

• Cluster releases (managed)

• Releases summary

• Deprecation notes

• Patch releases