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
Going through this Issue #4296, it mentions that there is a memory leak in Karpenter v0.29.1 which was fixed in v0.29.2. Someone also mentions within that ticket that rolling back to v0.29.0 actually resolves this issue.
Karpenter v0.29.0 contains a file descriptor and memory leak bug that leads to Karpenter getting OOMKilled and restarting at the point that it hits its memory or file descriptor limit. Karpenter >v0.29.1 fixes this leak.
My current assumption/understanding is that the information within the ticket is correct (i.e. bug is found in v0.29.1 and fixed in v0.29.2) and that this is just a small mistake within the documentation.
But please do let me know If my assumption/understanding is incorrect.
Thank you!
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
The text was updated successfully, but these errors were encountered:
Description
How can the docs be improved?
Going through this Issue #4296, it mentions that there is a memory leak in Karpenter v0.29.1 which was fixed in v0.29.2. Someone also mentions within that ticket that rolling back to v0.29.0 actually resolves this issue.
However, going through the Upgrade guide for v0.29.0+, the warning says the follows:
My current assumption/understanding is that the information within the ticket is correct (i.e. bug is found in v0.29.1 and fixed in v0.29.2) and that this is just a small mistake within the documentation.
But please do let me know If my assumption/understanding is incorrect.
Thank you!
The text was updated successfully, but these errors were encountered: