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

Memory leak in livenessprobe v2.1.0 #35

Closed
nimoalr opened this issue Apr 8, 2021 · 1 comment · Fixed by #36
Closed

Memory leak in livenessprobe v2.1.0 #35

nimoalr opened this issue Apr 8, 2021 · 1 comment · Fixed by #36
Labels
bug Something isn't working

Comments

@nimoalr
Copy link

nimoalr commented Apr 8, 2021

Describe the bug
Livenessprobe is slowly leaking memory on my Rancher cluster that use scaleway-csi. Memory on nodes is slowly being eaten up until the node run out of memory.
The issue was reported and acknowledged in livenessprobe repository for v2.1.0 (that you're using here and here) and fixed in livenessprobe v2.2.0

To Reproduce
Steps to reproduce the behavior:
Apply 0.1.5 yml and wait a few days. In about a week, livenessprobe will slowly eat all the available memory on a 4gb node
image

Expected behavior
Livenessprobe to not leak memory, obviously. :P

Details (please complete the following information):

  • Scaleway CSI version: 0.1.5
  • Platform:
  • Orchestrator and its version: Rancher v2.5.5 + k8s v1.19.6

Additional context
Add any other context about the problem here.

@nimoalr nimoalr added the bug Something isn't working label Apr 8, 2021
@Sh4d1 Sh4d1 closed this as completed in #36 Apr 9, 2021
@Sh4d1
Copy link
Contributor

Sh4d1 commented Apr 9, 2021

Hey @nimoalr ! Thanks for raising the issue, the v0.1.5 manifest is now fixed :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants