From 75456274f92acd1c1e2b5d16a1a3d3e58391ea67 Mon Sep 17 00:00:00 2001 From: ruiwen-zhao Date: Fri, 6 Nov 2020 19:19:38 +0000 Subject: [PATCH] Explicitly mention init containers in the QoS doc --- .../docs/tasks/configure-pod-container/quality-service-pod.md | 4 ++-- 1 file changed, 2 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 ce39aa01a5..0e6a02af37 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,8 +45,8 @@ kubectl create namespace qos-example For a Pod to be given a QoS class of Guaranteed: -* Every Container in the Pod must have a memory limit and a memory request, and they must be the same. -* Every Container in the Pod must have a CPU limit and a CPU request, and they must be the same. +* Every Container, including init containers, in the Pod must have a memory limit and a memory request, and they must be the same. +* Every Container, including init containers, in the Pod must have a CPU limit and a CPU request, and they must be the same. Here is the configuration file for a Pod that has one Container. The Container has a memory limit and a memory request, both equal to 200 MiB. The Container has a CPU limit and a CPU request, both equal to 700 milliCPU: