Enhancements¶
This section outlines new features and enhancements introduced in the Mirantis Container Cloud release 2.16.0. For the list of enhancements in the Cluster releases 11.0.0 and 7.6.0 that are introduced by the Container Cloud release 2.16.0, see the Cluster releases (managed).
License management using the Container Cloud web UI¶
Implemented a mechanism for the Container Cloud and MKE license update using the Container Cloud web UI. During the automatic license update, machines are not cordoned and drained and user workloads are not interrupted for all clusters starting from Cluster releases 7.6.0, 8.6.0, and 11.0.0. Therefore, after your management cluster upgrades to Container Cloud 2.16.0, make sure to update your managed clusters to the latest available Cluster releases.
Caution
Only the Container Cloud web UI users with the
m:kaas@global-admin role can update the Container Cloud license.
Scheduling of a management cluster upgrade using web UI¶
TechPreview
Implemented initial Technology Preview support for management cluster upgrade scheduling through the Container Cloud web UI. Also, added full support for management cluster upgrade scheduling through CLI.
Learn more
Automatic renewal of internal TLS certificates¶
Implemented automatic renewal of self-signed TLS certificates for internal Container Cloud services that are generated and managed by the Container Cloud provider.
Note
Custom certificates still require manual renewal. If applicable, the information about expiring custom certificates is available in the Container Cloud web UI.
Ubuntu 20.04 for greenfield bare metal managed clusters¶
TechPreview
Implemented initial Technology Preview support for Ubuntu 20.04 (Focal Fossa) on bare metal non-MOSK-based greenfield deployments of managed clusters. Now, you can optionally deploy Kubernetes machines with Ubuntu 20.04 on bare metal hosts. By default, Ubuntu 18.04 is used.
Caution
Upgrading to Ubuntu 20.04 on existing deployments initially created before Container Cloud 2.16.0 is not supported.
Note
Support for Ubuntu 20.04 on MOSK-based Cluster releases will be added in one of the following Container Cloud releases.
Learn more
Additional regional cluster on bare metal¶
Extended the regional clusters support by implementing the ability to deploy an additional regional cluster on bare metal. This provides an ability to create baremetal-based managed clusters in bare metal regions in parallel with managed clusters of other private-based regional clusters within a single Container Cloud deployment.
MOSK on local RAID devices¶
TechPreview
Implemented the initial Technology Preview support for Mirantis OpenStack for Kubernetes (MOSK) deployment on local software-based Redundant Array of Independent Disks (RAID) devices to withstand failure of one device at a time. The feature is available in the Cluster release 8.5.0 after the Container Cloud upgrade to 2.16.0.
Using a custom bare metal host profile, you can configure and create
an mdadm-based software RAID device of type raid10 if you have
an even number of devices available on your servers. At least four
storage devices are required for such RAID device.
Any interface name for bare metal LCM network¶
Implemented the ability to use any interface name instead of the k8s-lcm
bridge for the LCM network traffic on a bare metal cluster. The Subnet
objects for the LCM network must have the ipam/SVC-k8s-lcm label.
For details, see Service labels and their life cycle.
Keepalived for built-in load balancing in standalone containers¶
For the Container Cloud managed clusters that are based on vSphere, Equinix Metal, or bare metal, moved Keepalived for the built-in load balancer to run in standalone Docker containers managed by systemd as a service. This change ensures version consistency of crucial infrastructure services and reduces dependency on a host operating system version and configuration.
Learn more
Reworked ‘Reconfigure’ phase of LCMMachine¶
Reworked the Reconfigure phase applicable to LCMMachine that now can
apply to all nodes. This phase runs after the Deploy phase to apply
stateItems that relate to this phase without affecting workloads
running on the machine.
Learn more