This section outlines new features and enhancements introduced in the Mirantis Container Cloud release 2.7.0. For the list of enhancements in the Cluster release 5.14.0 and Cluster release 6.14.0 that are supported by the Container Cloud release 2.7.0, see the 5.14.0 and 6.14.0 sections.
Full support for the VMware vSphere provider¶
Introduced general availability support for the VMware vSphere provider after completing full integration of the vSphere provider on RHEL with Container Cloud.
During the Container Cloud 2.6.0 - 2.7.0 release cycle, added the following improvements:
Removed the StackLight limitations
Completed the integration of proxy support for the vSphere-based managed clusters
Completed the integration of the non-DHCP support for regional clusters
Addressed a number of critical and major issues
Universal SSH user¶
Implemented a universal SSH user
mcc-user to replace the existing
default SSH user names. The
mcc-user user name is applicable
to any Container Cloud provider and node type, including Bastion.
The existing SSH user names are deprecated as of Container Cloud 2.7.0.
SSH keys will be managed only for
mcc-user as of one of the following
Container Cloud releases.
Configuration of SSH keys on existing clusters using web UI¶
Implemented the possibility to configure SSH keys on existing clusters using the Container Cloud web UI. You can now add or remove SSH keys on running managed clusters using the Configure cluster web UI menu.
After the update of your Cluster release to the latest version supported by 2.7.0 for the OpenStack and AWS-based managed clusters, a one-time redeployment of the Bastion node is required to apply the first configuration change of SSH keys. For this purpose, the Allow Bastion Redeploy one-time check box is added to the Configure Cluster wizard in the Container Cloud web UI.
After the Bastion node redeploys on the AWS-based clusters, its public IP address changes.
Cluster and machines live statuses in web UI¶
Implemented the possibility to monitor live status of a cluster and machine deployment or update using the Container Cloud web UI. You can now follow the deployment readiness and health of essential cluster components, such as Helm, Kubernetes, kubelet, Swarm, OIDC, StackLight, and others. For machines, you can monitor nodes readiness reported by kubelet and nodes health reported by Swarm.
Enabling of proxy access using web UI for vSphere, AWS, and bare metal¶
Extended the Container Cloud web UI with the parameters that enable proxy access on managed clusters for the remaining cloud providers: vSphere, AWS, and bare metal.
Created a separate QuickStart guides section in the Container Cloud documentation with a set of QuickStart guides that contain only essential lightweight instructions with no additional options to quickly get started with Container Cloud on the AWS, OpenStack, or vSphere providers.