From 4eb78ea11a92b9c4c349345ffc4224dd76b70def Mon Sep 17 00:00:00 2001 From: Suraj Deshmukh Date: Fri, 28 Dec 2018 21:27:05 +0530 Subject: [PATCH] Update nodes to show the system reserved resources (#11908) Signed-off-by: Suraj Deshmukh --- .../en/docs/concepts/architecture/nodes.md | 23 ++----------------- 1 file changed, 2 insertions(+), 21 deletions(-) diff --git a/content/en/docs/concepts/architecture/nodes.md b/content/en/docs/concepts/architecture/nodes.md index f82c271345..b6d79fd115 100644 --- a/content/en/docs/concepts/architecture/nodes.md +++ b/content/en/docs/concepts/architecture/nodes.md @@ -272,27 +272,8 @@ The Kubernetes scheduler ensures that there are enough resources for all the pod checks that the sum of the requests of containers on the node is no greater than the node capacity. It includes all containers started by the kubelet, but not containers started directly by the [container runtime](/docs/concepts/overview/components/#node-components) nor any process running outside of the containers. -If you want to explicitly reserve resources for non-pod processes, you can create a placeholder -pod. Use the following template: - -```yaml -apiVersion: v1 -kind: Pod -metadata: - name: resource-reserver -spec: - containers: - - name: sleep-forever - image: k8s.gcr.io/pause:0.8.0 - resources: - requests: - cpu: 100m - memory: 100Mi -``` - -Set the `cpu` and `memory` values to the amount of resources you want to reserve. -Place the file in the manifest directory (`--config=DIR` flag of kubelet). Do this -on each kubelet where you want to reserve resources. +If you want to explicitly reserve resources for non-Pod processes, follow this tutorial to +[reserve resources for system daemons](/docs/tasks/administer-cluster/reserve-compute-resources/#system-reserved). ## API Object