zwzhang

Results 81 comments of zwzhang

[proposal]Collect metrics data from the kubelet instead of the cgroup.

metrics from cAdvisor is limited both on precision and type strategies in koordlet need more fine-grained metric, so instead of using cadvisor, we should consider the adaption of cgroup v2.

[proposal] cpu burst strategy should use cpu share pool for threshold ratio comparing

/area koordlet /assign zwzhang0107

[proposal] CPUSet injections to container runtime for fine-grained CPU orchestration

/assign zwzhang0107

[proposal] CPUSet injections to container runtime for fine-grained CPU orchestration

/area koordlet

[proposal] Essential QoS Enhancement Features of Koordlet

1、features * cpu evict strategy v0.4 * network qos v0.4 * blkio qos -v0.5/v0.6 * AMD pqos support（x86 LLC/MBA）- v0.5 * Kernel and environment adaptivity（cgroup v1/v2） - v0.5 * observability...

[proposal]cgroup v2 support of koordlet

/area koordlet

[BUG] cpu supress should exclude k8s guaranteed pod

also, we need to avoid all be cpusets bind to one LSR pod.

[proposal] support fine-grained GPU management

> > * [x] [api: add device CRD in scheduling group #376](https://github.com/koordinator-sh/koordinator/pull/376) > > * [x] [api: add device info into NodeMetric CRD #378](https://github.com/koordinator-sh/koordinator/pull/378) > > hello, I am confused...

[support request] The Compatibility Problem of Koordinator in KIND Scenario.

current koordlet only support cgroup v1 `cgroup path` configuration has been supported, consider adding a feature-gate for KinD to support cgroup path prefix

[proposal] plugins in `resmgr` module should be moved to `runtimehooks` or `qos-manager`

/area koordlet