Merge pull request #30261 from marosset/windows-limits-updates
Remove outdated section stating Windows does not support CPU limits
This commit is contained in:
@@ -499,13 +499,6 @@ passed from the Kubernetes components (kubelet, kube-proxy) are unchanged.
|
|||||||
The following list documents differences between how Pod container specifications
|
The following list documents differences between how Pod container specifications
|
||||||
work between Windows and Linux:
|
work between Windows and Linux:
|
||||||
|
|
||||||
* `limits.cpu` and `limits.memory` - Windows doesn't use hard limits
|
|
||||||
for CPU allocations. Instead, a share system is used.
|
|
||||||
The fields based on millicores are scaled into
|
|
||||||
relative shares that are followed by the Windows scheduler
|
|
||||||
See [`kuberuntime/helpers_windows.go`](https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/kuberuntime/helpers_windows.go),
|
|
||||||
and [Implementing resource controls for Windows containers](https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/resource-controls)
|
|
||||||
in Microsoft's virtualization documentation.
|
|
||||||
* Huge pages are not implemented in the Windows container
|
* Huge pages are not implemented in the Windows container
|
||||||
runtime, and are not available. They require [asserting a user
|
runtime, and are not available. They require [asserting a user
|
||||||
privilege](https://docs.microsoft.com/en-us/windows/desktop/Memory/large-page-support)
|
privilege](https://docs.microsoft.com/en-us/windows/desktop/Memory/large-page-support)
|
||||||
|
|||||||
Reference in New Issue
Block a user