we also need this feature. And I think it's necessary. For example, our node may only support limited count 'vpc port', we will store this capacity in node.status.allocatable["vpcPort"]. And In our design, vpc network is pod-level instead of container-level, we should not store this vpc request in pod.Spec.Containers[].resourcerequest.
在 2017年5月4日星期四 UTC+8上午1:47:55，Ahmet Alp Balkan写道： > > Hello, I am trying to understand the Resource Limits/Requests for Pods > and Containers > <https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/> > document. > In multiple places, the document implies that users can specify > ResourceRequirements *at pod-level**. *(I don't mean > pod.spec.containers.resources.) Most relevantly the doc says: > > A Pod resource request/limit for a particular resource type* is the sum *of >> the resource requests/limits of that type for each Container in the Pod. > > > However I can’t find any examples or any fields on the API (kubectl > explain pod.spec) to specify resource requirements on the pod level. > > Any ideas if this is possible at all? This particular document is > particularly gives the strong impression that this feature exists today. I > opened this docs issue > <https://github.com/kubernetes/kubernetes.github.io/issues/3608> to track > this. > > -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
