Create a node pool for your Kubernetes cluster provisioned through VMware Tanzu Mission Control.

For clusters that you create in Tanzu Mission Control, you can define a pool of worker nodes on which your workloads can run. Because Tanzu Mission Control cannot provision additional resources in a cluster that is created elsewhere and subsequently attached, you cannot create a node pool in an attached cluster.

This procedure describes how to create a node pool for an existing provisioned cluster. You can also define a node pool when creating a cluster, and the steps are essentially the same.

Prerequisites

Before you start this procedure, log in to the Tanzu Mission Control console and make sure you have the appropriate permissions.
  • To define a node pool, you must be associated with the cluster.edit role for the cluster.
  • To create a cluster, you must also be associated with the clustergroup.edit role for the cluster group.

For more information about adding permissions to custom roles, see Create a Custom Access Role.

Procedure

  1. Navigate to the cluster in which you want to create a node pool.
  2. On the cluster detail page, click the Node pools tab, and then click New node pool.
  3. Provide a name for the node pool.
    The name must be unique within the cluster.
  4. Specify the number of nodes to create for this node pool.
  5. Select the instance type for the worker nodes.
  6. For Tanzu Kubernetes clusters running in vSphere, you can specify the storage class for the worker nodes.
  7. Select the availability zone in which to create the nodes or, when running on vSphere 8.0, select the failure domain.

    In vSphere 8.0, vSphere with Tanzu allows you to provision guest cluster worker nodes across multiple failure domains (vSphere zones) for clusters deployed in high availability mode.

    You can select the failure domain from the dropdown list, which lists the domains that are retrieved from the Supervisor Cluster.

    Note:
    • The failure domain is required in highly available clusters, and optional in single node clusters.
    • The failure domain can not be modified after it the node pool is configured.
  8. You can optionally create additional volumes for the node pool.
    1. To create a volume, click Add Volume.
    2. Specify the name, mount path, and capacity for the volume.
    3. To create additional volumes, click Add Volume again.
    4. If necessary, you can click the delete icon to remove a volume that you have added.
    Make sure your volume definitions are correct before proceeding. You cannot edit the configured volumes after creating the node pool.
  9. You can optionally provide a description, and labels for the node and cloud.
    • The node labels that you add here are applied to the Kubernetes worker nodes in this node pool. To see the node labels in your cluster, use the following command:
      kubectl get nodes --show-labels
    • The cloud labels that you add here are applied to resources that are provisioned for this node pool in your cloud provider account (for example, AWS tags on EC2 instances).
  10. Click Save.

Results

When you click Save, Tanzu Mission Control provisions the necessary resources and then launches the requested nodes.