-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
KEP Pid Limiting #755
KEP Pid Limiting #755
Conversation
/sig node /cc @dashpole @dchen1107 @dims |
this captures the output of the discussion 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.
Proposed changes and content look great. Adding a couple links to give more context to the proposal.
/lgtm
gate is proposed. If enabled, pid reservations may be supported at the node | ||
allocatable and eviction manager subsystem configurations. | ||
|
||
Node allocatable is a well-established feature concept in the kubelet that |
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.
Link to https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/ for node allocatable.
- basic support integrated via eviction manager and/or node allocatable level | ||
|
||
Beta | ||
- ensure proper node e2e testing coverage to ensure a pod is unable to fork-bomb |
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.
You can link to the fork-bomb test I wrote here: https://github.com/kubernetes/kubernetes/blob/master/test/e2e_node/eviction_test.go#L397.
Although, we should ideally have separate tests for node-level thresholds and allocatable-level thresholds.
/lgtm |
/approve |
992a3e9
to
f62c349
Compare
messed up rebase /hold |
f62c349
to
63d361a
Compare
/hold cancel |
Looks like y'all should be able to check this in as it is in the sig-node directory with OWNERS. If you need approval stuff or questions about the KEP process please reach out (I can answer and/or connect). |
/lgtm per #755 (comment) |
@derekwaynecarr: you cannot LGTM your own PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/gtm |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bgrant0607, dashpole, dchen1107, derekwaynecarr 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 |
The following captures what was discussed in SIG Node on Dec 18, 2018.
See:
https://github.com/kubernetes/community/blob/master/sig-node/archive/meeting-notes-2018.md#dec-18
The KEP is aligned with latest state of code, what is not yet implemented or merged is the NodeAllocatable enforcement that we would like to tackle time-permitting.