Overview
This document describes how to manually or automatically scale a cluster to meet the resource requirements of the applications. You can scale a cluster in one of the following ways:
Manually adding/removing a node
Automatically adding/removing a node via auto scaling
Completing scaling of application layer via supernode (without scaling node)
Prerequisites
Directions
Manually adding/removing a node
To scale out a cluster, you can manually add a node by creating a node or adding an existing node. To scale in a cluster, you can remove a node.
Creating a node
When creating a node, you can configure a new CVM on the Create Node page for cluster scale-out.
For details, see Adding a Node. Adding an existing node
Note:
Currently, you can only add CVMs in the same VPC.
If you choose to add an existing node to the cluster, the operating system of the CVM will be reinstalled according to your settings.
If you choose to add an existing node to the cluster, the project of the CVM will be migrated to the project set for the cluster.
When adding a node with only one data disk to the cluster, you can choose to set the related parameters of data disk mounting.
Removing a node
Automatically adding/removing a node via auto scaling
Auto scaling relies on the community component Cluster Autoscaler (CA), which can dynamically adjust the number of nodes in a cluster to meet your resource requirements. For details on auto scaling, see Node Pool Overview. Scaling out via supernode
Supernode is a kind of scheduling capability. It supports scheduling the Pods in a standard Kubernetes cluster to a supernode that does not occupy the cluster server resource to implement dynamic scaling out when resources are insufficient. For more information, see supernode Overview. FAQs