IssueRaiser

Enhanced autoscaler capabilities (Karpenter support)

<p>As customer I would like to be able to use a node autoscaler so that I can create new node that better match resource requirement in terms of CPU or RAM and define more advanced scaling policies than with the existing Kubernetes Cluster Autoscaler. An idea would be to rely on Karpenter autoscaler (<a class="external-link" href="https://karpenter.sh/)" target="_blank" rel="nofollow noopener">https://karpenter.sh/)</a> </p> <p>&nbsp;</p> <p>Karpenter is an AWS project that has been donated to CNCF/Kube project in nov. 2023 (<a class="external-link" href="https://twitter.com/dims/status/1727388443595137348)" target="_blank" rel="nofollow noopener">https://twitter.com/dims/status/1727388443595137348)</a></p> <p>&nbsp;</p> <div class="table-wrap"> Feature | Cluster Autoscaler | Karpenter -- | -- | -- Resource Management | Based on the resource utilization of existing nodes, Cluster Autoscaler takes a reactive approach to scale nodes. | Based on the current resource requirements of unscheduled pods, Karpenter takes a proactive approach to provisioning nodes. Node management | Cluster Autoscaler manages nodes based on the resource demands of the present workload, using predefined autoscaling groups. | Karpenter scales, provisions, and manages nodes based on the configuration of custom Provisioners. Scaling | Cluster Autoscaler is more focused on node-level scaling, which means it can effectively add more nodes to meet any increase in demand. But this also means it may be less e

Posted by antonin-a on Mar 25, 2024, 10:19 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments

support (Sysadmin)

Enhanced autoscaler capabilities (Karpenter support)

antonin-aMar 25, 2024, 10:19 AM

<p>As customer I would like to be able to use a node autoscaler so that I can create new node that better match resource requirement in terms of CPU or RAM and define more advanced scaling policies than with the existing Kubernetes Cluster Autoscaler. An idea would be to rely on Karpenter autoscaler (<a class="external-link" href="https://karpenter.sh/)" target="_blank" rel="nofollow noopener">https://karpenter.sh/)</a> </p> <p>&nbsp;</p> <p>Karpenter is an AWS project that has been donated to CNCF/Kube project in nov. 2023 (<a class="external-link" href="https://twitter.com/dims/status/1727388443595137348)" target="_blank" rel="nofollow noopener">https://twitter.com/dims/status/1727388443595137348)</a></p> <p>&nbsp;</p> <div class="table-wrap"> Feature | Cluster Autoscaler | Karpenter -- | -- | -- Resource Management | Based on the resource utilization of existing nodes, Cluster Autoscaler takes a reactive approach to scale nodes. | Based on the current resource requirements of unscheduled pods, Karpenter takes a proactive approach to provisioning nodes. Node management | Cluster Autoscaler manages nodes based on the resource demands of the present workload, using predefined autoscaling groups. | Karpenter scales, provisions, and manages nodes based on the configuration of custom Provisioners. Scaling | Cluster Autoscaler is more focused on node-level scaling, which means it can effectively add more nodes to meet any increase in demand. But this also means it may be less e

Comments (0)

No comments yet. Start the discussion.

Comment on this issue