You can scale out a cluster to add more node resources as needed.
Insufficient node resources can cause operations, such as creating workloads, to fail. You can scale out a cluster in two ways:
Prerequisites
A cluster is created or a cluster is imported.
Create new nodes
Log on to the LHC console. In the navigation pane on the left, click Cluster Management > Cluster Details.
On the card for the destination cluster, click Scale Out Cluster.
On the Scale Out Cluster page, configure the following node information:
Virtual Switch: Select the vSwitch to associate with the ECS instances.
Billing Method: The supported billing methods are Pay-as-you-go and Subscription. If you select Subscription, configure the following parameters.
Subscription Duration: Select a duration of 1, 2, 3, or 6 months, or 1 to 5 years.
Auto-renewal: Specify whether to enable auto-renewal.
Number of Instances to Add: Enter the number of instances to add. The default value is 1.
Instance Type: Select one or more instance types. For more information, see Instance families.
System Disk: Standard SSDs and ultra disks are supported. The minimum size is 40 GB.
Data Disk: Standard SSDs and ultra disks are supported. The minimum size is 40 GB.
Password: Set the logon password for the nodes. The password must be 8 to 30 characters long and contain at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters. If you forget the password, you can log on to the ECS console to reset it.
CloudMonitor Agent: Specify whether to install the CloudMonitor agent on the ECS nodes. After installation, you can view monitoring information for the created ECS instances in the CloudMonitor console.
Tags: Attach tags to the nodes to help you filter them. To add a tag, click Add Row and then enter a key and value.
Taints: Add taints to the worker nodes. Click Add Row, and in the dialog box that appears, enter a key, a value, and select an effect. For more information, see the official documentation.
Deployment Unit: Keep the default configurations.
Unified Ingress Node: If you select this option, the new nodes are configured for unified network access to cluster resources.
After you complete the configuration, click Submit.
On the cluster details page, the cluster status changes to Scaling Up while the nodes are added. After the scale-out is complete, the cluster status changes to Running.
Add existing nodes
You can add existing Elastic Compute Service (ECS) instances from your workspace to the cluster. The instances must be in the Running state. The system provides a list of eligible instances. This list includes qualified instances from the current workspace and instances that were previously removed from a cluster using the Purge Environment method.
Make sure to add the ECS instances to the node security group that was automatically created for the cluster.
Log on to the LHC console. In the navigation pane on the left, click Cluster Management.
On the Cluster Details page, click the Nodes tab.
Click Add Existing Node and configure the following parameters.
Method: The default method is Automatic. This method lists the available ECS instances in your account. You can then install, deploy, and automatically add them to the cluster from the web interface.
Select Existing ECS Instances: Select the checkboxes of the ECS instances that you want to add.
Click Next and enter the following instance information.
Mount Data Disk: Specify whether to store containers and images on the data disk.
NoteIf an ECS instance has a data disk attached and its file system is not initialized, the system automatically formats the data disk to ext4. The disk is then used to store content in /var/lib/docker and /var/lib/kubelet. Any existing data on the data disk will be lost. Make sure to back up your data.
If the ECS instance does not have a data disk attached, a new data disk is not attached.
CPU Policy: Select the CPU policy.
none: The default policy. This policy uses the default CPU affinity scheme.
static: This policy allows pods with certain resource characteristics on the node to receive enhanced CPU affinity and exclusivity.
Password: Set the logon password for the nodes.
Confirm Password: Confirm the password.
Deployment Unit: Use the default configurations.
Tags: Attach tags to the nodes. To add a tag, click Add and then enter a Key and Value.
After you complete the configuration, click Submit.