diff options
| author | Kubernetes Submit Queue <k8s-merge-robot@users.noreply.github.com> | 2017-11-08 00:20:52 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-11-08 00:20:52 -0800 |
| commit | 0f099cb68b9e0065b068e243e25e4f8a060f316e (patch) | |
| tree | 89eff3898cb12ec8c5261d108178e6896a6f746e | |
| parent | 4d82ba353964062efd16fd5504812c35d0bbeea5 (diff) | |
| parent | 8fcf8c3e153e322e8b3613986bfe59ccd8bf0ac4 (diff) | |
Merge pull request #1375 from phinoceslee/patch-3
Automatic merge from submit-queue.
Update pod-resource-management.md
| -rw-r--r-- | contributors/design-proposals/node/pod-resource-management.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/node/pod-resource-management.md b/contributors/design-proposals/node/pod-resource-management.md index 0716788e..a7d517f3 100644 --- a/contributors/design-proposals/node/pod-resource-management.md +++ b/contributors/design-proposals/node/pod-resource-management.md @@ -341,7 +341,7 @@ we are not enabling this function by default, but would like operators that want to value resource priority over resource utilization to gather real-world feedback on its utility. -As a best practice, oeprators that want to provide a similar resource +As a best practice, operators that want to provide a similar resource reservation model for Guaranteed pods as we offer via enforcement of node allocatable are encouraged to schedule their Guaranteed pods first as it will ensure the Burstable and BestEffort tiers have had their QoS |