cri-resource-manager
cri-resource-manager copied to clipboard
intel
Kubernetes Container Runtime Interface proxy service with hardware resource aware workload placement policies
If workloads in a balloon are allowed to use idle CPUs through `SharedIdleCpusInSame: ` option, the frequencies of the idle CPUs remains to be configured according to the idle CPU...
When new cri-resmgr configuration is applied through cri-resmgr-agent, changes in AvailableResources, ReservedResources or AllocatorTopologyBalancing do not trigger realignment of workloads yet it should. As a consequence, workloads may continue to...
**Describe the solution you'd like** More unit tests for cpuallocator. To get good coverage, preferably initialize cpuallocator against different mocked sysfs'es, verifying e.g. cpu prioritization and allocation of whole packages,...
**Describe the bug** When I remove cri-rm cache (/var/lib/cri-rm/cache) and restart cri-rm the mechanism for restoring list of containers misses some information - one of them is the resources requests/limits...
**Describe the solution you'd like** E.g. --metrics-interval is not possible to be setup in config file and needs command line flag to be specified. **Why this is needed** When deploying...
**Describe the solution you'd like** with following config: ``` policy: Active: balloons AvailableResources: CPU: cpuset:1-63 ReservedResources: CPU: cpuset:63 ``` after I scheduled new pod I got an error ``` unable...
**Describe the bug** It requires patched kerenl which almost nowhere avaiable: I mean those two logs: * https://github.com/intel/cri-resource-manager/blob/2ce10b0922852c7ff413db14c17fdd83c77e2860/pkg/cri/resource-manager/control/memory/memory.go#L122 * https://github.com/intel/cri-resource-manager/blob/2ce10b0922852c7ff413db14c17fdd83c77e2860/pkg/cri/resource-manager/control/memory/memory.go#L132 **Expected behavior** Disable memory controller or print this warning only...
**Describe the bug** when run like this: ``` ./cri-resmgr --force-config config.yaml ``` with no intetion of using cri-regmgr-agent I'm getting such warnings in output: ``` W1116 15:10:52.288077 680245 log/ratelimit.go:97] [core]grpc:...
**Describe the bug** `cri-resmgr-agent` periodically pushes the existing configuration to `cri-resmgr` as new one. The current assumption is that this happens regularly, every time one of the watches (ConfigMap or...
update required SECURITY.md file for OSSF Scorecard compliance
