-
Notifications
You must be signed in to change notification settings - Fork 38.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add resource types for ingress and egress bandwidth #12187
Conversation
GCE e2e build/test passed for commit e95270c89c1220196c77476c3cc82f169742706d. |
@rajatchopra @dcbw @danwillians |
Is there a proposal somewhere? |
@@ -1391,7 +1391,10 @@ const ( | |||
ResourceMemory ResourceName = "memory" | |||
// Volume size, in bytes (e,g. 5Gi = 5GiB = 5 * 1024 * 1024 * 1024) | |||
ResourceStorage ResourceName = "storage" | |||
// Number of Pods that may be running on this Node: see ResourcePods | |||
// Bandwidth available for egress from a pod (bits/second) | |||
ResourceEgressBandwidth = "egress_bandwidth" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, documentation? Issue number? |
I've added documentation, the implementation details are in #11988 Comments addressed as well, please re-check. |
GCE e2e build/test passed for commit e98dc9ac3f298cd26d2570b86725d8a19f75ee07. |
egress: "2Mi" | ||
``` | ||
|
||
## How Pods with Resource Limits are Scheduled |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Curious To Know Why There Are So Many Capitals Here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed.
cc @erictune |
@@ -74,7 +74,7 @@ configured. | |||
|
|||
Although limits can only be specified on individual containers, it is convenient to talk about pod | |||
resource limits. A *pod resource limit* for a particular resource type is the sum of the resource | |||
limits of that type for each container in the pod, with unset values treated as zero. | |||
requests of that type for each container in the pod, with unset values treated as zero. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why did you change this to requests?
Labelling this PR as size/L |
Another reference: http://research.microsoft.com/apps/pubs/default.aspx?id=244865 |
GCE e2e build/test passed for commit 6971267. |
## How pods with resource limits are scheduled | ||
|
||
When a pod is created, the Kubernetes scheduler selects a node for the pod to | ||
run on. Each node has a maximum capacity for each of the resource types: the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How does the node report bandwidth capacity? This alludes to CPU and memory, but does not discuss how ingress, and egress are expressed. Does it require the operator to define this?
Brendan: it looks like this feature is active in kubelet by default. So, suggest either: flag default off in kubelet or update doc to reflect the "alpha" status of the feature and the use of annotation, and then merge this doc. |
GCE e2e build/test failed for commit 6971267. |
Without adding the new-added resource names to the |
GCE e2e build/test failed for commit 6971267. |
Adding label:do-not-merge because PR changes docs prohibited to auto merge |
Idle for several months. Closing. |
@bgrant0607 @johnwilkes
The code to implement this is in #11988
The basic intent is to use the
tc
utility to limit bandwidth on the Pod's IP address on thecbr0
bridge