Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Cap dead containers at a global max #5457

Closed
vmarmol opened this issue Mar 13, 2015 · 1 comment
Closed

Cap dead containers at a global max #5457

vmarmol opened this issue Mar 13, 2015 · 1 comment
Assignees
@vmarmol
Labels
area/kubelet priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/node Categorizes an issue or PR as relevant to SIG Node.
Milestone
v1.0

Comments

@vmarmol
Copy link
Contributor

vmarmol commented Mar 13, 2015

From @bgrant0607:

User on IRC just reported OOD due to too many dead containers from different dead pods:
http://paste.kismatic.io/view/a13c5e16#t15QhxeWR8MVIHhEKle50JpFhJjA9op4

@brendandburns @dchen1107
@vmarmol vmarmol added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. area/kubelet sig/node Categorizes an issue or PR as relevant to SIG Node. labels Mar 13, 2015
@vmarmol vmarmol self-assigned this Mar 13, 2015
@vmarmol vmarmol added this to the v1.0 milestone Mar 13, 2015
@vmarmol vmarmol mentioned this issue Mar 13, 2015
Closed
@dchen1107
Copy link
Member

Yes, there is a known issue. If I remembered correctly, there is even a TODO for this.

akram pushed a commit to akram/kubernetes that referenced this issue Apr 7, 2015
@vmarmol @akram
Use containerGC in the Kubelet.
45df4aa 
New policy default is 100 containers max.

Fixes kubernetes#5457.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vmarmol vmarmol

Labels
area/kubelet priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet
Milestone
v1.0
Development

No branches or pull requests
2 participants
@vmarmol @dchen1107