Add a machine¶
After you create a new AWS-based managed cluster as described in Create a managed cluster, proceed with adding machines to this cluster using the Mirantis Container Cloud web UI.
You can also use the instruction below to scale up an existing managed cluster.
To add a machine to an AWS-based managed cluster:
Log in to the Container Cloud web UI with the
Switch to the required project using the Switch Project action icon located on top of the main left-side navigation panel.
In the Clusters tab, click the required cluster name. The cluster page with the Machines list opens.
Click Create Machine.
Fill out the form with the following parameters as required:
Specify the number of machines to create.
The required minimum number of machines is three for the manager nodes HA and two for the Container Cloud workloads.
Select Manager or Worker to create a Kubernetes manager or worker node.
From the drop-down list, select the required AWS instance type. For production deployments, Mirantis recommends:
c5d.2xlargefor worker nodes
c5d.4xlargefor manager nodes
r5.4xlargefor nodes where the StackLight server components run
For more details about requirements, see Requirements for an AWS-based cluster.
From the drop-down list, select the required AMI ID of Ubuntu 18.04. For example,
Root device size
Select the required root device size,
Select the required node labels for the worker machine to run certain components on a specific node. For example, for the StackLight nodes that run Elasticsearch and require more resources than a standard node, select the StackLight label. The list of available node labels is obtained from your current
If you deploy StackLight in the HA mode (recommended):
Add the StackLight label to minimum three worker nodes. Otherwise, StackLight will not be deployed until the required number of worker nodes is configured with the StackLight label.
Removal of the StackLight label from worker nodes along with removal of worker nodes with StackLight label can cause the StackLight components to become inaccessible. It is important to correctly maintain the worker nodes where the StackLight local volumes were provisioned. For details, see Delete a machine.
To obtain the list of nodes where StackLight is deployed, refer to Upgrade managed clusters with StackLight deployed in HA mode.
You can add node labels after deploying a worker machine. On the Machines page, click the More action icon in the last column of the required machine field and select Configure machine.
Repeat the steps above for the remaining machines.
Monitor the deploy or update live status of the machine:
- Quick status
On the Clusters page, in the Managers or Workers columns. The green status icon indicates that the machine is Ready, the orange status icon indicates that the machine is Updating.
- Detailed status
In the Machines section of a particular cluster page, in the Status column. Hover over a particular machine status icon to verify the deploy or update status of a specific machine component.
You can monitor the status of the following machine components:
Readiness of a node in a Kubernetes cluster, as reported by kubelet
Health and readiness of a node in a Docker Swarm cluster
LCM readiness status of a node
Readiness of a node in the underlying infrastructure (virtual or bare metal, depending on the provider type)
The machine creation starts with the Provision status. During provisioning, the machine is not expected to be accessible since its infrastructure (VM, network, and so on) is being created.
Other machine statuses are the same as the LCMMachine object states described in LCM controller.
Once the status changes to Ready, the deployment of the managed cluster components on this machine is complete.
Verify the status of the cluster nodes as described in Connect to a Mirantis Container Cloud cluster.
An operational managed cluster deployment must contain a minimum of 3 Kubernetes manager nodes and 2 Kubernetes worker nodes. The deployment of the cluster does not start until the minimum number of nodes is created.
To meet the etcd quorum and to prevent the deployment failure, deletion of the manager nodes is prohibited.
A machine with the manager node role is automatically deleted during the managed cluster deletion.