koordinator-sh / charts Goto Github PK

apply the latest koordlet image, koordlet fails to start. After analysis, the startup parameters of koordlet daemonset have changed

I0901 15:54:25.653850  293522 feature.go:58] starting github.com/koordinator-sh/koordinator/pkg/util.RunFeature.func1 feature init module
I0901 15:54:25.653854  293522 feature.go:64] starting github.com/koordinator-sh/koordinator/pkg/koordlet/resmanager.(*MemoryEvictor).memoryEvict-fm feature dependency module, interval seconds 1
I0901 15:54:25.653860  293522 feature.go:58] starting github.com/koordinator-sh/koordinator/pkg/koordlet/resmanager.(*resmanager).Run.func3 feature init module
I0901 15:54:25.653865  293522 feature.go:64] starting github.com/koordinator-sh/koordinator/pkg/koordlet/resmanager.(*ResctrlReconcile).reconcile-fm feature dependency module, interval seconds 1
I0901 15:54:25.653872  293522 resmanager.go:148] Starting resmanager successfully
E0901 15:54:25.653890  293522 koordlet.go:193] Unable to run the runtimeHook: %!(EXTRA *fs.PathError=open /host-etc-hookserver/koordlet.json: no such file or directory)

the latest version, the koord-scheduler cannot start since missing PodGroup CRD.

There are multiple endpoints such as Interference Detection Metrics added in koordlet, and they are evicted by Prometheus for further usages. We need to add service monitor for Koordlet in helm charts at the next Koordinator version 1.1.

Koordlet use arg -runtime-hooks-addr to run runtime hooks server. After runtime hooks auto register to runtime proxy feature added in v0.7.0, this endpoint needs to be written in koordlet.json so that runtime proxy can gets hooks configuration. While -runtime-hooks-addr provide a path inside container, runtime proxy can only understand path outside so another arg runtime-hooks-host-endpoint is introduced to solve this problem.

Considering that this arg is consistent with mount volume path it's better to put this in values.yaml.