Description
What problem are you trying to solve?
In order to support latency-critical and high-throughput workloads, kubelet Topology Manager policy options prefer-closest-numa-nodes and max-allowable-numa-nodes need to be supported in Karpenter.
Bottlerocket supports settings.kubernetes.topology-manager-policy-options since v1.60.0.
We need to Topology Manager policy options in pkg/providers/amifamily/bootstrap/bottlerocketsettings.go,
Current behaviour is Karpenter does not pass-through this setting, but simply ignores it.
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?
In order to support latency-critical and high-throughput workloads, kubelet Topology Manager policy options
prefer-closest-numa-nodesandmax-allowable-numa-nodesneed to be supported in Karpenter.Bottlerocket supports
settings.kubernetes.topology-manager-policy-optionssince v1.60.0.We need to Topology Manager policy options in pkg/providers/amifamily/bootstrap/bottlerocketsettings.go,
Current behaviour is Karpenter does not pass-through this setting, but simply ignores it.
How important is this feature to you?