Boovan Rajendran d8c3451959 Identify platform pods based on pod/namespace labels ... This is new changes for the reverted commit 3c6672b7a4 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, it 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>		2024-04-22 10:36:43 -04:00
..
deb_folder	Identify platform pods based on pod/namespace labels	2024-04-22 10:36:43 -04:00
meta_data.yaml	tox: fixed warnings	2023-09-06 17:54:55 -03:00