Pods with namespace 'kube-system', or labeled with
'app.starlingx.io/component=platform' are identified as
'platform'. These have isolated cpu affinity cpuset when
kubelet cpu-manager 'static' policy is configured. This
decouples performance of application pods from the platform.
Currently, for static CPU allocation, pods are identified
as platform pods using a hard-coded list of namespaces.
New method identifies a pod as a platform pod using label
assigned to it or its namespace.
This will also assign the pods with kube-system
namespace as platform pod.
This change will introduce a new patch
"Identify-platform-pods-based-on-pod-or-namespace-labels.patch"
to use a new method to identify the platform pods and to
remove the hardcoded list of namespaces.
This will also fix the Kubernetes make test fail issue after merging
the review https://review.opendev.org/c/starlingx/integ/+/907637
This change also include the missed out patch
kubeadm-reduce-UpgradeManifestTimeout.patch for k8s 1.29.
Test Plan:
PASS: Run all Kubelet, kubeadm, kubectl make tests for affected code.
PASS: All affected versions of kubernetes package build successfully.
PASS: Create a pod with the platform label. Pod is classified as
a platform pod.
PASS: Create a pod without the platform label but in a namespace with
the platform label. Pod is classified as a platform pod.
PASS: Create a pod without the platform label and in a namespace
without the platform label. Pod is not classified as a platform
pod.
Closes-Bug: 2058042
Story: 2010612
Task: 49910
Change-Id: I0cc05c2e9057b64f9191317e72a1bf4d7b8d0771
Signed-off-by: Boovan Rajendran <boovan.rajendran@windriver.com>
1542fdea18