In VMware Telco Cloud Automation, you can scale up or scale down the number of primary control plane node replicas. You can add or remove labels on control plane nodes and configure POD Security Default Policy, along with vertically scaling the control plane nodes by increasing or decreasing vCPUs count and memory, and disk size for Classy Standard cluster. You can configure Machine Health Check on control plane nodes and also relocate the vCenter resource on control plane nodes for Classy Standard cluster. Moreover, you can configure Topology Variable on control plane nodes for Classy Standard cluster.

Note:
  • When you initiate vertical scaling of the control plane node, it caused a rolling update.
  • When you relocate the vCenter resource on control plane node, it caused a rolling update.
  • When you configure the Topology Variable on control plane node, it caused a rolling update.

Prerequisites

The Workload Cluster status should reflect as Processing or Provisioned.

Procedure

  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 that you want to edit.
  4. Click Edit Cluster Configuration.
  5. Under Cluster Info, click Add Variable under Topology Variable.
    Note:

    Different Topology variables are applicable to standard clusters and classy clusters.

  6. Select the required variable from the drop-down list. Enter the value for the variable. To know more, see Topology Variable Reference.
    Note: Ensure that you have selected BOM to populate variables in the drop-down menu.
  7. Under Control Plane Info, click the configuration icon.
  8. In the Configuration tab, select one setting under VM Placement.
    1. Edit the Resource Pool to relocated control plane's node VM to other vCenter Resource Pool.
    2. Edit the VM Folder to relocated control plane's node VM to other vCenter VM folder.
    3. Edit the Datastore to relocated control plane's node VM to other vCenter Datastore.
    4. Edit the VM Template to relocated control plane's node VM to other vCenter VM Template.
    Note: You can update Resource Pool, VM Folder, Datastore only for Classy Standard Cluster. Once updated, the control plane node is redeployed due to rollout. Control Plane's Datastore will not update if the Persistent Volumes (PV) are deployed.
  9. In the Configuration tab, select one setting under VM Size. The Control Plane Node Info window appears. Edit the Number of replicas to scale down or scale up the Control Plane nodes. Edit the number of vCPUs, memory and disk size as required for the control plane node.
    Note:
    • You can increase or decrease the memory and disk size as required for the control plane.
    • If the underlying ESXi host has hyperthreading enabled and the network function requires NUMA alignment or supports SMT or CPU reservation, the count of CPUs must be even. This ensures that the physical CPU core is used by the same node.
    • If you update the number of vCPUs, memory, and disk size, the control plane node is redeployed due to rollout.
  10. In the Configuration tab, click Add Label to configure the node labels. You can add/delete label or udpate the value of the label on control plane node.
  11. In the Configuration tab, select Advanced Options.

    • Configure Machine Health Check. Select the check box to configure machine health check. For more information, see MachineHealthChecks.

      • Node Start Up Timeout (Optional): This option controls the amount of time that the MachineHealthCheck controller waits for a machine to join the cluster before considering the machine unhealthy.
      • Node Unhealthy Conditions: This option can set the Ready, MemoryPressure, DiskPressure, PIDPressure, and NetworkUnavailable conditions. The MachineHealthCheck controller uses the conditions that you set to monitor the health of your control plane and worker nodes.
      • Type: Ready, MemoryPressure, DiskPressure, PIDPressure, and NetworkUnavailable.
      • Status: To set the status of a condition, add True, False, or Unknown.
      • Timeout: Specify the timeout duration for the node condition. If the condition is met for the duration of the timeout, the machine will be remediated. Long timeouts can result in long periods of downtime for a workload on an unhealthy machine.
        Note: You will not be able to change Certificates Expiry Days during update operation.
  12. Click Apply to apply the configurations.
  13. Click Next > Update Cluster Config.

Results

You have successfully edited the Kubernetes Cluster and its Control Plane configuration.