github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-09-09 05:01:46 +00:00
Code Issues Projects Releases Wiki Activity

Auto-fixed docs

Browse Source
This commit is contained in:
Daniel Smith
2015-07-09 18:02:10 -07:00
parent c4aab16b04
commit c03a788c67
43 changed files with 86 additions and 89 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/compute_resources.md
View File

@@ -9,7 +9,7 @@
- [Troubleshooting](#troubleshooting)
- [Planned Improvements](#planned-improvements)
When specifying a [pod](./pods.md), you can optionally specify how much CPU and memory (RAM) each
When specifying a [pod](pods.md), you can optionally specify how much CPU and memory (RAM) each
container needs. When containers have resource limits, the scheduler is able to make better
decisions about which nodes to place pods on, and contention for resources can be handled in a
consistent manner.
@@ -19,8 +19,8 @@ in units of cores. Memory is specified in units of bytes.
CPU and RAM are collectively refered to as *compute resources*, or just *resources*. Compute
resources are measureable quantities which can be requested, allocated, and consumed. They are
distinct from [API resources](./working_with_resources.md). API resources, such as pods and
[services](./services.md) are objects that can be written to and retrieved from the Kubernetes API
distinct from [API resources](working_with_resources.md). API resources, such as pods and
[services](services.md) are objects that can be written to and retrieved from the Kubernetes API
server.
## Container and Pod Resource Limits
@@ -136,7 +136,7 @@ Here are some example command lines that extract just the necessary information:
- `kubectl get nodes -o yaml | grep '\sname\|cpu\|memory'`
- `kubectl get nodes -o json | jq '.items[] | {name: .metadata.name, cap: .status.capacity}'`
The [resource quota](./resource_quota_admin.md) feature can be configured
The [resource quota](resource_quota_admin.md) feature can be configured
to limit the total amount of resources that can be consumed. If used in conjunction
with namespaces, it can prevent one team from hogging all the resources.
@@ -144,11 +144,11 @@ with namespaces, it can prevent one team from hogging all the resources.
The current system only allows resource quantities to be specified on a container.
It is planned to improve accounting for resources which are shared by all containers in a pod,
such as [EmptyDir volumes](./volumes.md#emptydir).
such as [EmptyDir volumes](volumes.md#emptydir).
The current system only supports container limits for CPU and Memory.
It is planned to add new resource types, including a node disk space
resource, and a framework for adding custom [resource types](./design/resources.md#resource-types).
resource, and a framework for adding custom [resource types](design/resources.md#resource-types).
The current system does not facilitate overcommitment of resources because resources reserved
with container limits are assured. It is planned to support multiple levels of [Quality of