How to set Parameter cpu-manager-policy to static in the TCA Manager UI

Products

• VMware Telco Cloud Automation

Issue/Introduction

•  Parameter cpu-manager-policy is set to static in the TCA Manager UI but not enforced in the cluster TKG Nodes.
  
  
  
  
• The cat command inside the TKG Node shows the Policy as None
  cat /var/lib/kubelet/cpu_manager_state
{"policyName": "none", "defaultCpuSet":"","checksum": xxxxxxxxxx}

Environment

TCA SW Version 3.2 

Workload Kubernetes SW Version 1.24.10

Cluster Type: Standard cluster

Cause

The root cause is related to the 'Kubeadm Config Template' not being enabled during node pool creation as part of Day0 configuration.Once enabled, users can configure the cpuManagerPolicy to static and adjust kube-reserved and system-reserved resources accordingly.

Resolution

1. For Standard Cluster type the kubeadm day1 configuration (e.g.  change in cpu-manager-policy) is not supported and gets completely greyed out in TCA UI after cluster is successfully deployed.
2. For Day 0 deployment the configuration is supported but its a 2 step process:
   • Paste the configuration lines in the provided box in UI
   • On top right corner of the configuration input box turn on the configuration
     

Additional Information

1. In Classy Standard clusters, the 'Kubeadm Config Template' can be updated post-provisioning to change the CPU manager policy parameter. Please note that such updates will trigger a node rollout update
2. This change is not permitted in Standard Cluster Types.If it was not set while deploying the cluster initially then only solution is to deploy a new Node Pool with the setting ON.
3. For definition of classy & standard cluster types please refer to below links:
   TCA Description of Cluster Types
   TKG Description of Cluster Types