From 2975fd3137b9647f2e72bb007949ebb273fb247c Mon Sep 17 00:00:00 2001 From: mohamed chiheb ben jemaa Date: Fri, 27 Sep 2019 20:11:37 +0100 Subject: [PATCH] delete outdated section (#16332) --- .../manage-compute-resources-container.md | 20 ------------------- 1 file changed, 20 deletions(-) diff --git a/content/en/docs/concepts/configuration/manage-compute-resources-container.md b/content/en/docs/concepts/configuration/manage-compute-resources-container.md index 98ff861dd7..bb81405d3b 100644 --- a/content/en/docs/concepts/configuration/manage-compute-resources-container.md +++ b/content/en/docs/concepts/configuration/manage-compute-resources-container.md @@ -587,27 +587,7 @@ spec: example.com/foo: 1 ``` -## Planned Improvements -Kubernetes version 1.5 only allows resource quantities to be specified on a -Container. It is planned to improve accounting for resources that are shared by -all Containers in a Pod, such as -[emptyDir volumes](/docs/concepts/storage/volumes/#emptydir). - -Kubernetes version 1.5 only supports Container requests and 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](https://github.com/kubernetes/community/blob/{{< param "githubbranch" >}}/contributors/design-proposals/scheduling/resources.md). - -Kubernetes supports overcommitment of resources by supporting multiple levels of -[Quality of Service](http://issue.k8s.io/168). - -In Kubernetes version 1.5, one unit of CPU means different things on different -cloud providers, and on different machine types within the same cloud providers. -For example, on AWS, the capacity of a node is reported in -[ECUs](http://aws.amazon.com/ec2/faqs/), while in GCE it is reported in logical -cores. We plan to revise the definition of the cpu resource to allow for more -consistency across providers and platforms. {{% /capture %}}