You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered:
@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.
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.
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
The text was updated successfully, but these errors were encountered: