Filter the Pods reported in KCNR
zhy76 opened this issue · comments
What would you like to be added?
The results returned by the pod resources server are not filtered, so anything returned by the pod resources server will be reported to KCNR. This may also need to be considered in conjunction with the scheduler to determine if we need to filter out only non-NUMA binding Pods.
Why is this needed?
The Pods currently reported by KCNR may need filtering
According to the discussion before, for the problem of kcnr exception monitoring, special treatment is taken for the monitoring logic, that is, only care about the numabinding pod, for other numabinding types of Pods that may be implemented in the future, only need to adapt the corresponding monitoring logic. So, turn off this first.