cri-resource-manager
cri-resource-manager copied to clipboard
intel
Kubernetes Container Runtime Interface proxy service with hardware resource aware workload placement policies
Allow optional unix socket qualifier for runtime, image and relay socket paths (by stripping any `unix://`-prefix).
Make the image socket default to the current value of the runtime socket instead of the default value of the runtime socket. With this in place, changing only the value...
This patch introduces a memory moving daemon. The lower levels of the daemon are based on the topology aware memory demoter with few optimizations.
**Describe the bug** Use `curl --silent http://localhost:8891/metrics` to fetch cri-rm balloon information but it failed to get new create balloon information. **Expected behavior** [root@PUE01 Mon Jul 04 16:31:19 ~]# curl...
**Describe the bug** According to https://intel.github.io/cri-resource-manager/stable/docs/setup.html#setting-up-cri-resource-manager setting --image-socket is optional, while from my experience for cri-o it is mandatory and one needs both --image-socket and --runtime-socket to point to cri-o...
**Describe the bug** There are a lot of messages in the cri logs stating: ``` cri-resmgr[]: W: [resource-manager] UpdateContainerResources: XXX TODO: we probably should reallocate the container instead... cri-resmgr[]: W:...
- Rename PreferSpreadingDifferentNamespaces to PreferPerNamespaceBalloon. - Add CPU class configuration section.
Install CRI-RM as Gardener extension using ControllerDeployment/ControllerRegistation as generic Extension of type "cri-resource-manager" TODO: I. PoC/research phase - [x] 1. **P** ~No operator, just using ManagedResource with shoot namespace is...
Switch to talking CRI v1 to the CRI runtime/server. Bridge any pre-v1 (only CRI v1alpha2) client requests, unless this is explicitly disabled on the command line.