This section outlines new features and enhancements introduced in the Mirantis Container Cloud release 2.3.0. For the list of enhancements in the Cluster release 5.10.0 and Cluster release 6.10.0 introduced by the Container Cloud release 2.3.0, see the 5.10.0 and 6.10.0 sections.
Updated versions of Mirantis Kubernetes Engine and Container Runtime
Automated setup of an OVF template for the VMWare vSphere provider
Support of multiple host-specific L2 templates per a bare metal cluster
Updated the Mirantis Kubernetes Engine (MKE) version to 3.3.4 and the Mirantis Container Runtime (MCR) version to 19.03.13 for the Container Cloud management and managed clusters.
For the MKE release highlights and components versions, see MKE, MSR, and MCR documentation: Mirantis Kubernetes Engine release notes.
For the Mirantis Container Runtime release highlights, see MKE, MSR, and MCR documentation: Mirantis Container Runtime release notes.
Caution
Due to the development limitations, the MCR upgrade to version 19.03.13 or 19.03.14 on existing Container Cloud clusters is not supported.
Technical Preview
In scope of Technology Preview support for the VMWare vSphere provider, added the capability to deploy an additional regional vSphere-based cluster on top of the vSphere management cluster to create managed clusters with different configurations if required.
Technical Preview
Automated the process of an OVF template setup for the vSphere-based
management and managed clusters deployments.
The OVF template is now set up by Packer using the vsphere_template
flag
that is integrated into bootstrap.sh.
Learn more
Technical Preview
Added the capability to deploy StackLight on management clusters. However, such deployment has the following limitations:
The Kubernetes Nodes and Kubernetes Cluster Grafana dashboards may have empty panels.
The DockerNetworkUnhealthy
and etcdGRPCRequestsSlow
alerts may fail
to raise.
The CPUThrottlingHigh
, CalicoDatapaneIfaceMsgBatchSizeHigh
,
KubeCPUOvercommitPods
, KubeMemOvercommitPods
alerts, and the
TargetDown
alert for the prometheus-node-exporter
and
calico-node
pods may be constantly firing.
Added support of multiple host-specific L2 templates to be applied to different nodes of the same bare metal cluster. Now, you can use several independent host-specific L2 templates on a cluster to support different hardware configurations. For example, you can create L2 templates with a different number and layout of NICs to be applied to the specific machines of a cluster.
Improved user experience with the Container Cloud resources logs collection by implementing collecting of logs on the Mirantis Kubernetes Engine cluster and on all Kubernetes pods, including the ones that were previously removed or failed.