From 010374113893b178910f1599f3b76bccaa9fda33 Mon Sep 17 00:00:00 2001 From: Steven Pitts <25968054+makusu2@users.noreply.github.com> Date: Wed, 19 May 2021 17:23:05 -0400 Subject: [PATCH] Update content/en/docs/tasks/configure-pod-container/quality-service-pod.md Co-authored-by: Tim Bannister --- .../tasks/configure-pod-container/quality-service-pod.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/content/en/docs/tasks/configure-pod-container/quality-service-pod.md b/content/en/docs/tasks/configure-pod-container/quality-service-pod.md index 93204b86e0..ca74cf2a47 100644 --- a/content/en/docs/tasks/configure-pod-container/quality-service-pod.md +++ b/content/en/docs/tasks/configure-pod-container/quality-service-pod.md @@ -45,7 +45,12 @@ kubectl create namespace qos-example For a Pod to be given a QoS class of Guaranteed: -* Every Container, including init containers, in the Pod must have a memory limit and a memory request, and the two values must be the same. +* Every Container in the Pod must have a memory limit and a memory request. +* For every Container in the Pod, the memory limit must equal the memory request. +* Every Container in the Pod must have a CPU limit and a CPU request. +* For every Container in the Pod, the CPU limit must equal the CPU request. + +These restrictions apply to init containers and app containers equally. * Every Container, including init containers, in the Pod must have a CPU limit and a CPU request, and the two values must be the same. Here is the configuration file for a Pod that has one Container. The Container has a memory limit and a @@ -273,4 +278,3 @@ kubectl delete namespace qos-example -