7 Commits

Author SHA1 Message Date
Mark Rossetti
3c9380c449 Memory manager support for Windows nodes (#128560) 2024-11-07 23:32:49 +00:00
James Sturtevant
0c2357710a respond to feedback
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
2024-10-25 15:55:05 -07:00
James Sturtevant
2c5a8c2618 Add Windows Affinity Featuregate
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
2024-10-25 09:14:54 -07:00
James Sturtevant
4d25c25eb0 Support CPU and Memory manager on Windows
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
2024-10-25 09:14:53 -07:00
Sascha Grunert
de37b9d293 Make CRI v1 the default and allow a fallback to v1alpha2
This patch makes the CRI `v1` API the new project-wide default version.
To allow backwards compatibility, a fallback to `v1alpha2` has been added
as well. This fallback can either used by automatically determined by
the kubelet.

Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
2021-11-17 11:05:05 -08:00
Stephen Augustus
481cf6fbe7 generated: Run hack/update-gofmt.sh
Signed-off-by: Stephen Augustus <foo@auggie.dev>
2021-08-24 15:47:49 -04:00
Artyom Lukianov
38dc7509f8 cpu manager: specify the container CPU set during the creation
We can set the container cpuset.cpus diring the creation and it
will not need to call to update resources after the container creation.

Additional side effect of the change, that the runc process that responsible
to create the container will run with the same CPU affinity because the
runc runs on the cpuset provided in the config.json arg.

It will allow to prevent undesirable interupts on isolated CPUs.

Signed-off-by: Artyom Lukianov <alukiano@redhat.com>
2021-01-20 17:53:33 +02:00