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

Kuma-cp - Possible memory leak #7488

Closed
NorbertGajda8 opened this issue Aug 8, 2023 · 3 comments
Closed

Kuma-cp - Possible memory leak #7488

NorbertGajda8 opened this issue Aug 8, 2023 · 3 comments
Labels
kind/bug A bug triage/pending This issue will be looked at on the next triage meeting

Comments

@NorbertGajda8
Copy link

What happened?

Hi, I turn to the community after not being able to resolve an issue that seems to be a bug rather than a configuration problem.

We observed a memory leak after we upgraded the kuma version to a newer one.

The last version, which we have no issue is: 2.1.5.
We are facing with the memory leak with both 2.2.x and 2.3.x .
We are using it with Kong Gateway Enterprise v. 3.3.x

I have tried to add more memory limit for the container (512Mi), but the result is the same, the container consumes more and more memory, and the pod is restarting, when the limit has been reached.

image
image

Any additional information needed can be provided, but since the configuration is large, I am unsure what parts I should be posting. Ask away for clarifications.

Thank you for your help, in advance!
Best Regards,
Norbert Gajda

@NorbertGajda8 NorbertGajda8 added kind/bug A bug triage/pending This issue will be looked at on the next triage meeting labels Aug 8, 2023
@michaelbeaumont
Copy link
Contributor

@NorbertGajda8 have you tried 2.3.2/2.2.4?

@NorbertGajda8
Copy link
Author

@michaelbeaumont
Thank you for your advice, 2.3.2 seems to be working. (We have tried 2.3.1 and 2.2.3 a little while ago.)
Reading the changelogs again, this might have been the issue causing the leak: #7351 , but I am not sure.

@michaelbeaumont
Copy link
Contributor

@NorbertGajda8 that is indeed very likely the cause :) glad it's working!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug triage/pending This issue will be looked at on the next triage meeting
Projects
None yet
Development

No branches or pull requests

2 participants