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
What problem are you trying to solve?
This feature aims to improve pod density capabilities for Windows EKS nodes launched with Karpenter. Currently, by default, Karpenter launches Windows pods with a setting of --max-pods=110 meaning a node cannot scale beyond 110 pods.
How important is this feature to you?
This is an important capability because using prefix delegation will offer improved cost savings, since more pods can be scheduled on a node.
Description
What problem are you trying to solve?
This feature aims to improve pod density capabilities for Windows EKS nodes launched with Karpenter. Currently, by default, Karpenter launches Windows pods with a setting of
--max-pods=110
meaning a node cannot scale beyond 110 pods.How important is this feature to you?
This is an important capability because using prefix delegation will offer improved cost savings, since more pods can be scheduled on a node.
References
The text was updated successfully, but these errors were encountered: