Renaming strict policy to restricted policy

Restricted policy will fail admission of guaranteed pods where
all requested resources are not available on a single NUMA Node

Kubernetes-commit: 2fb94231d0950fb0bc1d054a70f356d22e337a3e
This commit is contained in:
Louise Daly 2019-08-22 07:57:55 +01:00 committed by Kubernetes Publisher
parent e7ef558aba
commit ec5113d257
1 changed files with 5 additions and 5 deletions

View File

@ -54,12 +54,12 @@ const (
// WatchChangeDetectionStrategy is a mode in which kubelet uses
// watches to observe changes to objects that are in its interest.
WatchChangeDetectionStrategy ResourceChangeDetectionStrategy = "Watch"
// StrictTopologyManagerPolicy is a mode in which kubelet only allows
// RestrictedTopologyManagerPolicy is a mode in which kubelet only allows
// pods with a single NUMA alignment of CPU and device resources.
RestrictedTopologyManagerPolicy = "restricted"
// BestEffortTopologyManagerPolicy is a mode in which kubelet will favour
// pods with NUMA alignment of CPU and device resources.
StrictTopologyManagerPolicy = "strict"
// PreferredTopologyManagerPolicy is a mode in which kubelet will favour
// pods with NUMA alignment of CPU and device resources.
PreferredTopologyManagerPolicy = "preferred"
BestEffortTopologyManagerPolicy = "best-effort"
// NoneTopologyManager Policy is a mode in which kubelet has no knowledge
// of NUMA alignment of a pod's CPU and device resources.
NoneTopologyManagerPolicy = "none"