Update nodes to show the system reserved resources (#11908)
Signed-off-by: Suraj Deshmukh <surajd.service@gmail.com>
This commit is contained in:
committed by
Kubernetes Prow Robot
parent
129328d05d
commit
4eb78ea11a
@@ -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
|
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.
|
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
|
If you want to explicitly reserve resources for non-Pod processes, follow this tutorial to
|
||||||
pod. Use the following template:
|
[reserve resources for system daemons](/docs/tasks/administer-cluster/reserve-compute-resources/#system-reserved).
|
||||||
|
|
||||||
```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.
|
|
||||||
|
|
||||||
|
|
||||||
## API Object
|
## API Object
|
||||||
|
|||||||
Reference in New Issue
Block a user