From 16ae848701d4b8f401dd726805f33eeee7a5b6c5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Thomas=20G=C3=BCttler?= Date: Wed, 30 Mar 2022 08:32:23 +0200 Subject: [PATCH] Link to 'Guaranteed' pods. related to #32619 --- .../tasks/administer-cluster/reserve-compute-resources.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/en/docs/tasks/administer-cluster/reserve-compute-resources.md b/content/en/docs/tasks/administer-cluster/reserve-compute-resources.md index 0dd24d3f6e..f3c73ee01a 100644 --- a/content/en/docs/tasks/administer-cluster/reserve-compute-resources.md +++ b/content/en/docs/tasks/administer-cluster/reserve-compute-resources.md @@ -182,8 +182,9 @@ respectively. ## General Guidelines -System daemons are expected to be treated similar to 'Guaranteed' pods. System -daemons can burst within their bounding control groups and this behavior needs +System daemons are expected to be treated similar to +['Guaranteed' pods](/docs/tasks/configure-pod-container/quality-service-pod/#create-a-pod-that-gets-assigned-a-qos-class-of-guaranteed). +System daemons can burst within their bounding control groups and this behavior needs to be managed as part of kubernetes deployments. For example, `kubelet` should have its own control group and share `kube-reserved` resources with the container runtime. However, Kubelet cannot burst and use up all available Node