mirror of https://github.com/k3s-io/k3s
b9b875f0d7
Automatic merge from submit-queue (batch tested with PRs 49488, 50407, 46105, 50456, 50258) Add UpdateContainerResources method to CRI This is first step toward support for opinionated cpu pinning for certain guaranteed pods. In order to do this, the kubelet needs to be able to dynamically update the cpuset at the container level, which is managed by the container runtime. Thus the kubelet needs a method to communicate over the CRI so the runtime can then modify the container cgroup. This is used in the situation where a core is added or removed from the shared pool to become a exclusive core for a new G pod. The cpuset for all containers in the shared pool will need to be updated to add or remove that core. Opening this up now so we can start discussion. The need for a change to the CRI might be unexpected. @derekwaynecarr @vishh @ConnorDoyle ```release-note NONE ``` |
||
|---|---|---|
| .. | ||
| BUILD | ||
| doc.go | ||
| fake_kuberuntime_manager.go | ||
| helpers.go | ||
| helpers_test.go | ||
| instrumented_services.go | ||
| instrumented_services_test.go | ||
| kuberuntime_container.go | ||
| kuberuntime_container_test.go | ||
| kuberuntime_gc.go | ||
| kuberuntime_gc_test.go | ||
| kuberuntime_image.go | ||
| kuberuntime_image_test.go | ||
| kuberuntime_logs.go | ||
| kuberuntime_logs_test.go | ||
| kuberuntime_manager.go | ||
| kuberuntime_manager_test.go | ||
| kuberuntime_sandbox.go | ||
| kuberuntime_sandbox_test.go | ||
| labels.go | ||
| labels_test.go | ||
| legacy.go | ||
| legacy_test.go | ||
| security_context.go | ||
| security_context_test.go | ||