You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Koordlet supports two features CPUBurst and CPUNormalization which can change the cpu.cfs_quota_us/cpu.max of the LS pods and containers. However, these features can not co-work for the cfs_quota adjustment. When both features are enabled, the QoS plugin of the CPUBurst modifies the cfs_quota due to the cfs throttled ratio of pods. In contrast, the runtime hook plugin of the CPUNormalization may overwrite the cfs_quota according to the CPU-normalisation ratio of the node. Then neither of them can achieve their reconciliation.
What you expected to happen:
To make the CPUBurst feature co-work with the CPUNormalization, the CPUBurst QoS plugin should be aware of the CPU-normalization ratio of the node. When both features are enabled, the CPUBurst QoS plugin is responsible for adjusting the cpu.cfs_quota_us/cpu.max according to the scaling ratio and the CPU-normalization ratio, and the runtime hook of the CPUNormalization should stop its reconciliation to avoid conflicts.
How to reproduce it (as minimally and precisely as possible):
What happened:
Koordlet supports two features CPUBurst and CPUNormalization which can change the
cpu.cfs_quota_us
/cpu.max
of the LS pods and containers. However, these features can not co-work for the cfs_quota adjustment. When both features are enabled, the QoS plugin of the CPUBurst modifies the cfs_quota due to the cfs throttled ratio of pods. In contrast, the runtime hook plugin of the CPUNormalization may overwrite the cfs_quota according to the CPU-normalisation ratio of the node. Then neither of them can achieve their reconciliation.What you expected to happen:
To make the CPUBurst feature co-work with the CPUNormalization, the CPUBurst QoS plugin should be aware of the CPU-normalization ratio of the node. When both features are enabled, the CPUBurst QoS plugin is responsible for adjusting the
cpu.cfs_quota_us
/cpu.max
according to the scaling ratio and the CPU-normalization ratio, and the runtime hook of the CPUNormalization should stop its reconciliation to avoid conflicts.How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version
):The text was updated successfully, but these errors were encountered: