This topic describes how to scale out the worker nodes in a cluster of Container Service for Kubernetes (ACK) that runs sandboxed containers in the ACK console.

Prerequisites

You cannot scale out the master nodes in an ACK cluster that runs sandboxed containers.

To expand an ACK cluster that runs sandboxed containers, you must set the following parameters as required in the following table. Otherwise, the added nodes cannot run sandboxed containers.

Procedure

  1. Log on to the ACK console.
  2. In the left-side navigation pane, click Clusters.
  3. On the Clusters page, find the cluster that you want to expand and select Expand from the More drop-down list in the Actions column.
  4. Go to the Expand page and set the parameters.

    In this example, the number of worker nodes in the cluster is increased from three to five. The following table describes the required parameters.

    Parameter Description
    Region The region where the cluster is deployed.
    Container Runtime By default, Sandboxed-Container is displayed.
    VPC Set the network for the nodes. You can select a virtual private cloud (VPC) from the drop-down list. If no VPC network is available, click Create VPC. For more information, see Create a VPC.
    VSwitch Select one or more VSwitches for the cluster.

    You can select up to three VSwitches deployed in different zones. If no VSwitch is available, click Create VSwitch to create one. For more information, see Create a VSwitch.

    Billing Method ACK supports the pay-as-you-go and subscription billing methods. If you select the subscription billing method,
    • you must set the duration. Duration: You can select 1, 2, 3, or 6 months. If you require a longer duration, you can select 1 to 5 years.
    • Specify whether to enable auto renewal.
    Instance Type Select ECS Bare Metal Instance.
    Selected Types The selected instance types are displayed here.
    System Disk SSDs, ESSDs, and ultra disks are supported.
    Mount Data Disk SSDs, ESSDs, and ultra disks are supported.
    Note You can specify whether to encrypt the mounted data disks. Data disks are used to store the root file systems of containers on the nodes. Therefore, you must mount a data disk of at least 200 GiB. We recommend that you mount a data disk of at least 1 TB.
    Nodes to Add The number of nodes that you want to add to the cluster.
    Logon Type
    • Key pair:

      If no key pair is available, you can click create a key pair to create one in the Elastic Compute Service (ECS) console. For more information, see Create an SSH key pair. After the key pair is created, set it as the credentials to log on to the cluster.

    • Password:
      • Password: Enter a password for logging on to the added nodes.
      • Confirm Password: Enter the password again.
    Key Pair
    ECS Label Attach labels to the added ECS instances.
    Note
    • Key is required. Value is optional.
    • Keys are not case-sensitive. A key must be 1 to 64 characters in length and cannot start with aliyun, http://, or https://.
    • Values are not case-sensitive. A value must be 1 to 128 characters in length and cannot start with http:// or https://.
    • The keys of labels that are attached to the same resource must be unique. If you add a label with a used key, the label overwrites the one using the same key.
    • You can attach up to 20 labels to each resource. If you attach more than 20 labels to a resource, all labels become invalid. You must detach unused labels for the remaining labels to take effect.
    Node Label Attach labels to the added nodes.
    Note
    • Key is required. Value is optional.
    • Keys are not case-sensitive. A key must be 1 to 64 characters in length and cannot start with aliyun, http://, or https://.
    • Values are not case-sensitive. A value must be 1 to 128 characters in length and cannot start with http:// or https://.
    • The keys of labels that are attached to the same resource must be unique. If you add a label with a used key, the label overwrites the one using the same key.
    • You can attach up to 20 labels to each resource. If you attach more than 20 labels to a resource, all labels become invalid. You must detach unused labels for the remaining labels to take effect.
    Taints Add taints to the added nodes.
    RDS whitelist Set the RDS whitelist. Add the IP addresses of cluster nodes to the RDS whitelist.
    User Data For more information, see Prepare user data.
  5. Click OK.

What to do next

After the expansion is complete, go to the details page of the cluster. In the left-side navigation pane, click Node Pools. You can find that the number of the worker nodes is increased from 3 to 5.