[BUG] koordlet supports detecting kubelet v1.28 configuration #1801
Labels
area/koordlet
good first issue
Good for newcomers
help wanted
Extra attention is needed
kind/bug
Create a report to help us improve
Milestone
What happened:
During the NodeResourceResource reporting, the koordlet uses Kubelet's
/configz
to detect the current configurations like cpu manager policy and topology manager policy.It unmarshals the Kubelet configurations as the imported version. So the configuration detection is constrained to a certain version API of the Kubelet.
In the Kubernetes 1.28, the Kubelet configuration introduces an API change that is not backward-compatible:
This API change of the Kubelet configuration can fail the koordlet's detection and the NodeResourceResource reporting. So the current koordlet cannot work well with Kubelet v1.28 when
--disable-query-kubelet-config=false
.What you expected to happen:
The koordlet's NRT reporting should be more robust and might tolerate the API change of the Kubelet.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
The koordlet's dependencies for the kubelet configurations are due to the collaboration with the kubelet against the CPU manager and topology manager. If you do not need this feature, you can set
--disable-query-kubelet-config=true
for the koordlet to avoid this issue.Environment:
kubectl version
): v1.28.3The text was updated successfully, but these errors were encountered: