Enhancements¶
This section outlines new features and enhancements introduced in the Container Cloud release 2.29.0.
For the list of enhancements delivered with the Cluster releases introduced by Container Cloud 2.29.0, see 17.4.0 and 16.4.0.
For the list of enhancements delivered with MOSK 25.1 introduced together with Container Cloud 2.29.0, see MOSK release notes 25.1: New features.
BareMetalHostInventory instead of BareMetalHost¶
To allow the operator use the gitops approach, implemented the
BareMetalHostInventory resource that must be used instead of
BareMetalHost for adding and modifying configuration of bare metal servers.
The BareMetalHostInventory resource monitors and manages the state of a
bare metal server and is created for each Machine with all information
about machine hardware configuration.
Each BareMetalHostInventory object is synchronized with an automatically
created BareMetalHost object, which is now used for internal purposes of
the Container Cloud private API.
Caution
Any change in the BareMetalHost object will be overwitten by
BareMetalHostInventory.
For any existing BareMetalHost object, a BareMetalHostInventory object
is created automatically during cluster update.
Caution
While the Cluster release the management cluster is 16.4.0,
BareMetalHostInventory operations are allowed to
m:kaas@management-admin only. Once the management cluster is updated
to the Cluster release 16.4.1 (or later), this limitation will be lifted.
Validation of the Subnet object changes against allocated IP addresses¶
Implemented a validation of the Subnet object changes against already
allocated IP addresses. This validation is performed by the Admission
Controller. The controller now blocks changes in the Subnet object
containing allocated IP addresses that are out of the allocatable IP address
space, which is formed by a CIDR address and include/exclude address ranges.
Improvements in calculation of update estimates using ClusterUpdatePlan¶
Improved calculation of update estimates for a managed cluster that is managed
by the ClusterUpdatePlan object. Each step of ClusterUpdatePlan now has
more precise estimates that are based on the following calculations:
The amount and type of components updated between releases during patch updates
The amount of nodes with particular roles in the OpenStack cluster
The number of nodes and storage used in the Ceph cluster
Also, the ClusterUpdatePlan object now contains the releaseNotes field
that links to MOSK release notes of the target release.
Switch of the default container runtime from Docker to containerd¶
Switched the default container runtime from Docker to containerd on greenfield management and managed clusters. The use of containerd allows for better Kubernetes performance and component update without pod restart when applying fixes for CVEs.
On existing clusters, perform the mandatory migration from Docker to containerd in the scope of Container Cloud 2.29.x. Otherwise, the management cluster update to Container Cloud 2.30.0 will be blocked.
Important
Container runtime migration involves machine cordoning and draining.