Description
What problem are you trying to solve?
The current deployment template for helm sets a non-tunable MEMORY_LIMIT which is not the default for karpenter.
Setting it to the full limits.memory (readers: divisor=0 does this) causes a static 90% GOMEMLIMIT which isn't always desirable for some environments.
It would be great if another divisor were able to be set or MEMORY_LIMIT/GOMEMLIMIT could be overridden.
How important is this feature to 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
Description
What problem are you trying to solve?
The current deployment template for helm sets a non-tunable MEMORY_LIMIT which is not the default for karpenter.
Setting it to the full limits.memory (readers: divisor=0 does this) causes a static 90% GOMEMLIMIT which isn't always desirable for some environments.
It would be great if another divisor were able to be set or MEMORY_LIMIT/GOMEMLIMIT could be overridden.
How important is this feature to you?