You can add a node pool to your Kubernetes Workload cluster.


  1. Log in to the VMware Telco Cloud Automation web interface.
  2. Go to Infrastructure > CaaS Infrastructure > Cluster Instances.
  3. Click the Options () symbol against the Kubernetes cluster where you want to add the node pool.
  4. Click Edit Worker Node Configuration and click Add.
    In Add Node Pool, enter the following information:
    • Name - Enter the name of the node pool. The node pool name cannot be greater than 36 characters.
    • CPU - Select the number of virtual CPUs in the node pool.
    • Memory - Select the amount of memory for the node pool.
    • Storage - Select the storage size. Minimum disk size required is 50 GB.
    • Replica - Select the number of controller node virtual machines.
    • vSphere Cluster (Optional) - To use a different vSphere Cluster, select the vSphere cluster from here.
    • Resource Pool (Optional) - To use a different resource pool, select the resource pool from here.
    • Datastore (Optional) - To use a different datastore, select the datastore from here.
    • Labels - Add key-value pair labels to your nodes. You can use these labels as node selectors when instantiating a network function.
    • Networks - You can add the network details.
      • Label - Enter the labels to group the networks. Networks use these labels to provide network inputs during a cluster deployment. Add additional labels for network types such as IPvlan, MacVLAN, and Host-Device. Meaningful network labels such as N1, N2, N3, and so on, help users provide the correct network preferences during deployment. It is mandatory to include a management interface label. SR-IOV interfaces are added to the Worker nodes when deploying the network functions.
        Note: A label length must not exceed 15 characters.
        Apart from the management network, which is always the first network, the other labels are used as interface names inside the Worker nodes. For example, when you deploy a cluster using the template with the labels MANAGEMENT, N1, and N2, the Worker nodes interface names are eth0, N1, N2. To add more labels, click Add.
      • Network - Select the network that you want to associate with the label.
      • (Optional) MTU - Provide the MTU value for the network. The minimum MTU value is 1500. The maximum MTU value depends on the configuration of the network switch.
    • Domain Name Servers - Enter a valid DNS IP address. These DNS servers are configured in the guest operating system of each node in the cluster. You can override this option on the Master node and each node pool of the Worker node. To add a DNS, click Add.
    • CPU Manager Policy - Set CPU reservations on the Worker nodes as Static or Default. For information about controlling CPU Management Policies on the nodes, see the Kubernetes documentation at
      Note: For CPU-intensive workloads, use Static as the CPU Manager Policy.
    • Configure Machine Health Check - Click the corresponding button to enable the machine health check. When you enable the Configure Machine Health Check, you can configure the health check related options under Advanced Configuration. For details on Machine Health Check, see Machine Health Check
    • Under Advanced Configuration, you can configure the Node Start Up Timeout duration and set the unhealthy conditions.
      Note: Node Start Up Timeout is applicable when the Machine Health Check is enabled.
      1. (Optional) Enter the Node Start Up Timeout time duration for Machine Health Check to wait for a node to join the cluster. If a node does not join during the specified time, Machine Health Check considers it unhealthy.
      2. Set unhealthy conditions for the nodes. If the nodes meet any of these conditions, Machine Health Check considers them as unhealthy and starts the remediation process.
    • To use the vSphere Linked Clone feature for creating linked clones for the Kubernetes nodes, select Use Linked Cloning for Cloning the VMs.
  5. Click Add.


You have successfully added the node pool to your Workload cluster.