Skip to content
Permalink
Browse files

delete outdated section (#16332)

  • Loading branch information...
medmedchiheb authored and k8s-ci-robot committed Sep 27, 2019
1 parent 764a485 commit 2975fd3137b9647f2e72bb007949ebb273fb247c
Showing with 1 addition and 21 deletions.
  1. +1 −21 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 %}}

0 comments on commit 2975fd3

Please sign in to comment.
You can’t perform that action at this time.