777b7d8863
The normal mechanisms for allocating isolated CPUs do not allow a mix of isolated and exclusive CPUs in the same container. In order to allow this in *very* limited cases where the pod spec is known in advance we will add the ability to disable the normal isolcpus behaviour. If the file "/etc/kubernetes/ignore_isolcpus" exists, then kubelet will basically forget everything it knows about isolcpus and just treat them like regular CPUs. The admin user can then rely on the fact that CPU allocation is deterministic to ensure that the isolcpus they configure end up being allocated to the correct pods. Story: 2008760 Task: 42164 Change-Id: Ie38c81209ee407ac98b4882f2581fc14622b3af1 Signed-off-by: Chris Friesen <chris.friesen@windriver.com> |
||
|---|---|---|
| .. | ||
| files | ||
| Readme.rst | ||
| build_srpm.data | ||
| kubernetes.spec | ||
| kubernetes.spec.orig | ||
Readme.rst
The spec file used here was from the kubernetes 1.10.0 src rpm. The orig file is included to help show modifications made to that spec file, to help understand which changes were needed and to assist with future upversioning.
The contrib tarball does not have the same versioning as kubernetes and there is little activity in that repo.
The version for the contrib tarball is arbitrary.