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
Tell us about your request
Ability to provide custom resources when deploying Karpenter through helm chart
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
A lot of users will do POCs with Karpenter on temporary clusters which might consist of small instances with 2-4 vCPU, the default resources for the controller is 1 vCPU and 1Gi memory, which they might want to change for their use-cases.
Are you currently working around this issue?
I will be raising a PR for fixing this issue in a few minutes.
Additional context
Webhook deployment too has fixed resources, which too needs to be forwarded from values.yaml
Community Note
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:
Tell us about your request
Ability to provide custom resources when deploying Karpenter through helm chart
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
A lot of users will do POCs with Karpenter on temporary clusters which might consist of small instances with 2-4 vCPU, the default resources for the controller is 1 vCPU and 1Gi memory, which they might want to change for their use-cases.
Are you currently working around this issue?
I will be raising a PR for fixing this issue in a few minutes.
Additional context
Webhook deployment too has fixed resources, which too needs to be forwarded from values.yaml
Community Note
The text was updated successfully, but these errors were encountered: