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

Procedure

  1. Log in to the VMware Telco Cloud Automation web interface.
  2. Go to Infrastructure > CaaS Infrastructure > Cluster Instances.
  3. Click the Kubernetes cluster name that you want to configure.
  4. Select the Node Pools tab, click Add Node Pool.
  5. There will show a Node Pool Details Dialog, edit node pool 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.

    • Destination Cloud - Select the cloud for the node pool.

    • Datacenter - Select the datacenter for the node pool.

    • Resource Pool - Select the resource pool for the node pool.

    • VM Folder - Select the folder for the node pool machines.

    • Datastore - To use a different datastore, select the datastore from here.

    • VM Template - Select the template for the node pool machines.

    • Replica - Select the number of controller node virtual machines.

    • CPU - Select the number of virtual CPUs in the node pool.

    • Cores per Socket (Optional) - Select the number of cores per socket in the node pool.

    • Memory - Select the amount of memory for the node pool.

    • Disk Size - Select the disk size. Minimum disk size required is 50 GB.

    • Labels - Add key-value pair labels to your nodes, which to be used as node selectors when instantiating a network function.

    • Networks - You can add the network details.

      • 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.

      • (Optional)

        DNS - Enter a valid DNS IP address as Domain Name Servers. 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. Multiple DNS servers can be separated by commas.

    • Labels - Add key-value pair labels to your nodes, which to be used as node selectors when instantiating a network function.

    • Expand Advanced Options, user could configure Maintenance Mode/Clone Mode/Machine Health Check/Kubeadmin Config Template.

      • Enable or disable Maintenance Mode.

      • Select the Clone Mode, enable clone mode will use the vSphere linked clone feature to create machines for Kubernetes nodes.

      • To enable Machine Health Check, select Configure Machine Health Check. For more information, see Machine Health Check.

        • (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.

        • Select the node unhealthy conditions, which support Ready/MemoryPressure/DiskPressure/PIDPressure/NetworkUnavailable. Select the Status, such as False/Unknown/True. Then select Timeout. If any of these conditions are met, Machine Health Check considers these nodes as unhealthy and starts the remediation process.

      • Kubeadmin Config Template - 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 https://kubernetes.io/docs/tasks/administer-cluster/cpu-management-policies/.

        Note:

        For CPU-intensive workloads, use Static as the CPU Manager Policy.

  6. Click Apply.
  7. After the Node Pool dialog close, click Next jump to Ready to Deploy, Click Deploy.

Results

You have successfully added the node pool of a Kubernetes cluster instance.