Deploy a v2 Workload cluster using the VMware Telco Cloud Automation user interface.

Prerequisites

  • You require a role with Infrastructure Lifecycle Management privileges.
  • You must have uploaded the Virtual Machine template to VMware Telco Cloud Automation.
  • You must have onboarded a vSphere VIM.
  • You must have created a Management cluster or uploaded a Workload cluster template.
  • A network must be present with a DHCP range and a static IP of the same subnet.
  • When you enable multi-zone, ensure that:
    • For region: vSphere data center has tags attached for the selected category.
    • For zone: vSphere Cluster or hosts under the vSphere cluster has tags attached for the selected category. Ensure that vSphere Cluster and hosts under vSphere cluster does not share the same tags.

Procedure

  1. Log in to the VMware Telco Cloud Automation web interface.
  2. Go to Infrastructure > CaaS Infrastructure and click Deploy Cluster.
  3. From the drop-down menu, select Workload Cluster.
  4. In the Workload Cluster Deployment wizard, enter information for each of the sub-categories:
  5. 1. Destination Info
    • Management Cluster - Select the Management cluster from the drop-down menu. You can also select a Management cluster deployed in a different vCenter.
    • Destination Cloud - Select a cloud on which you want to deploy the Kubernetes cluster.
    • Datacenter - Select a data center that is associated with the cloud.
    Advanced Options - Provide the secondary cloud information here. These options are applicable when creating stretch clusters.
    • (Optional) Secondary Cloud - Select the secondary cloud. It is required for stretched cluster creation.
    • (Optional) Secondary Data Center - Select the secondary data center.
    • (Optional) NF Orchestration VIM - Provide the details of the VIM. VMware Telco Cloud Automation uses this VIM and associated Control Planes for NF life cycle management.
  6. Click Next.
  7. 2. Cluster Info
    • Name - Enter a name for the Workload cluster. The cluster name must be compliant with DNS hostname requirements as outlined in RFC-952 and amended in RFC-1123.
    • TCA BOM Release - The TCA BOM Release file contain information about the Kubernetes version and add-on versions. You can select multiple BOM release files.
    • CNI - Select a Container Network Interface (CNI) such as Antrea or Calico.
    • Proxy Repository Access - Available only when the selected management cluster uses a proxy repository. Select the proxy repository from the drop-down list.
    • Airgap Repository Access - Available only when the selected management cluster uses a airgap repository. Select the airgap repository from the drop-down list.
    • IP Version - The IP version specified in the Management cluster is displayed here.
    • Cluster End Point - Enter the IP of the API server loadbalancer.
    • Cluster (pods) CIDR - Enter the IP for clusters. VMware Telco Cloud Automation uses the CIDR pool to assign IP addresses to pods in the cluster.
    • Service CIDR - Enter the IP for clusters. VMware Telco Cloud Automation uses the CIDR pool to assign IP addresses to the services in the cluster.
  8. Click Next.
  9. 3. Control Plane Info
    • To configure Control Plane node placement, click the Settings icon in the Control Plane Node Placement table.
      • Name - Enter the name of the Control Plane node.
      • Destination Cloud - The destination cloud is selected by default. To make a different selection, use the drop-down menu.
      VM Placement
      • Datacenter - Select a data center for the Control Plane node.
      • Resource Pool - Select the default resource pool on which the Control Plane node is deployed.
      • VM Folder - Select the virtual machine folder on which the Control Plane node is placed.
      • Datastore - Select the default datastore for the Control Plane node.
      • VM Template - Select a VM template.
      VM Size
      • Number of Replicas - Number of controller node VMs to be created. The ideal number of replicas for production or staging deployment is 3.
      • Number of vCPUs - To ensure that the physical CPU core is used by the same node, provide an even count of vCPUs if the underlying ESXi host is hyper threading-enabled, and if the network function requires NUMA alignment and CPU reservation.
      • Cores Per Socket (Optional) - Enter the number of cores per socket if you require more that 64 cores.
      • Memory - Enter the memory in GB.
      • Disk Size - Enter the disk size in GB.
      Network
      • Management Network - Select the Management network.
      • MTU - Enter the maximum transmission unit in bytes.
      • DNS - Provide comma-separated primary and secondary DNS servers.
      Labels
      • To add the appropriate labels for this profile, click Add Label. These labels are added to the Kubernetes node.
      Advanced Options
      • Clone Mode - Specify the type of clone operation. Linked Clone is supported on templates that have at least one snapshot. Otherwise, the clone mode defaults to Full Clone.
      • Kubeadmin Config Template (YAML) - Enable or deactivate the Kubeadmin Config Template YAML.
    • Click Apply.
  10. 4. Add-Ons
    To deploy an add-on such as NFS Client or Harbor, click Deploy Add-on.
    1. From the Select Add-On wizard, select the add-on and click Next.
    2. For add-on configuration information, see Add-On Configuration Reference.
  11. Click Next.
  12. 5. Node Pools
    • A node pool is a set of nodes that have similar properties. Pooling is useful when you want to group the VMs based on the number of CPUs, storage capacity, memory capacity, and so on. You can add one node pool to a Management cluster and multiple node pools to a Workload cluster, with different groups of VMs. To add a Worker node pool, click Add Worker Node Pool.
      • Name - Enter the name of the node pool.
      • Destination Cloud - The destination cloud is selected by default. To make a different selection, use the drop-down menu.
      VM Placement
      • Datacenter - Select a data center for the node pool.
      • Resource Pool - Select the default resource pool on which the node pool is deployed.
      • VM Folder - Select the virtual machine folder on which the node pool is placed.
      • Datastore - Select the default datastore for the node pool.
      • VM Template - Select a VM template.
      VM Size
      • Number of Replicas - Number of node pool VMs to be created. The ideal number of replicas for production or staging deployment is 3.
      • Number of vCPUs - To ensure that the physical CPU core is used by the same node, provide an even count of vCPUs if the underlying ESXi host is hyper threading-enabled, and if the network function requires NUMA alignment and CPU reservation.
      • Cores Per Socket (Optional) - Enter the number of cores per socket if you require more that 64 cores.
      • Memory - Enter the memory in GB.
      • Disk Size - Enter the disk size in GB.
      Network
      • Management Network - Select the Management network.
      • MTU - Enter the maximum transmission unit in bytes.
      • DNS - Provide comma-separated primary and secondary DNS servers.
      Labels
      • To add the appropriate labels for this profile, click Add Label. These labels are added to the Kubernetes node.
      Advanced Options
      • Clone Mode - Specify the type of clone operation. Linked Clone is supported on templates that have at least one snapshot. Otherwise, the clone mode defaults to Full Clone.
      • To enable Machine Health Check, select Configure Machine Health Check
      • Kubeadmin Config Template (YAML) - Enable or deactivate the Kubeadmin Config Template YAML.
    • Click Apply.
  13. 6. Ready to Deploy - Click Deploy.

Results

The cluster details page displays the status of the overall deployment and the deployment status of each component.