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.

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

kubelet memory leak v1.18.1 #101724

Closed
danisafta opened this issue May 4, 2021 · 3 comments · Fixed by #100326
Closed

kubelet memory leak v1.18.1 #101724

danisafta opened this issue May 4, 2021 · 3 comments · Fixed by #100326
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/node Categorizes an issue or PR as relevant to SIG Node.

Comments

@danisafta
Copy link

danisafta commented May 4, 2021

What happened:

kubelet increased more than 100MB in memory in 4 days.

What you expected to happen:

kubelet to not used that amount of RAM

How to reproduce it (as minimally and precisely as possible):

I have reproduced it using 3 cronjobs which create hello world pods each minute
and another cronjob that writes a line to a file each minute.

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version):
    v1.18.1

  • Cloud provider or hardware configuration
    happens on both virtualbox and baremetal

  • OS (e.g: cat /etc/os-release):
    centos 7

  • Kernel (e.g. uname -a):
    4.18.0-147.3.1

I have seen some existing issues like #64137 but I do not have any dangling resources associated with the cgroup.

@danisafta danisafta added the kind/bug Categorizes issue or PR as related to a bug. label May 4, 2021
@k8s-ci-robot k8s-ci-robot added needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 4, 2021
@k8s-ci-robot
Copy link
Contributor

@danisafta: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@pacoxu
Copy link
Member

pacoxu commented May 6, 2021

/sig node

@k8s-ci-robot k8s-ci-robot added sig/node Categorizes an issue or PR as relevant to SIG Node. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels May 6, 2021
@wzshiming
Copy link
Member

/assign

This is a duplicate issue, there has been a fixed PR but it has not been merged. #100326

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants