-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
Mention how requests are inferred from limits #44861
Conversation
in the example for pod overhead - we need to have requests section instead of limits
Welcome @suhasadhav! |
/sig node |
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.
If you specify a limit and not request, what does the kubelet infer about the request for that resource?
If the kubelet infers the request from the limit, then this change might not be helpful. We could instead add a YAML comment to explain what happens.
yes kubelet infers request from limits and pod overhead is added correctly to the pod. I will add YAML comment to have more clarity. |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
@sftim could you please check the comment or you want me to elaborate more in the comment? |
@tallclair @dchen1107 - can you please have a look at this change |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
@kubernetes/sig-node-pr-reviews : Please could you take a look? |
/retitle Mention how requests are inferred from limits |
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.
/lgtm
/approve
Hope this isn't a problem!
LGTM label has been added. Git tree hash: 3e4c18eb6676e5b442836859ade233d2d64b14a1
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sftim The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
it's totally fine Tim :) |
In the example section for pod overhead - we need to have requests instead of limits. As sum of requests(not limits) is considered while admitting a pod with pod overhead