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
Just want to understand how karpenter works with azure AKS
I saw microsoft documentation which says below that there is limitation while working with AKS, we can not create virtual machine scaleset with karpenter while Karpenter is not designed to directly create Virtual Machine Scale Sets (VMSS) in Azure; instead, it focuses on automatically provisioning individual nodes within a Kubernetes cluster based on pod requirements, essentially bypassing the need to manage VMSS explicitly, allowing for more granular scaling and cost optimization by launching only the necessary nodes.
we also found some issue related to it while we were trying to create internal azure LB, it was showing error Error syncing load balancer: failed to ensure load balancer: can not extract scale set name from ipConfigurationID (/subscriptions/xxxxxxx/resourceGroups/xxxxxx/providers/Microsoft.Network/networkInterfaces/aks-karpenter-nodepool-xxxx/ipConfigurations/aks-karpenter-nodepool-xxxx)
let me know if there is something wrong with our service below
This Karpenter provider creates standalone VMs that are compatible with AKS cluster; AKS documentation is a but outdated in that respect. At this point there is no corresponding AKS agentpool representation for Karpenter NodePools, but it is likely to change in the future. At the same time, AKS is also developing first class support for Virtual Machine nodepools, see https://learn.microsoft.com/en-us/azure/aks/virtual-machines-node-pools.
Is an existing page relevant?
No response
What karpenter features are relevant?
Hi team,
Just want to understand how karpenter works with azure AKS
I saw microsoft documentation which says below that there is limitation while working with AKS, we can not create virtual machine scaleset with karpenter while Karpenter is not designed to directly create Virtual Machine Scale Sets (VMSS) in Azure; instead, it focuses on automatically provisioning individual nodes within a Kubernetes cluster based on pod requirements, essentially bypassing the need to manage VMSS explicitly, allowing for more granular scaling and cost optimization by launching only the necessary nodes.
The AKS cluster must use Virtual Machine Scale Sets for the nodes.
reference: https://learn.microsoft.com/en-gb/azure/aks/create-node-pools#limitations
we also found some issue related to it while we were trying to create internal azure LB, it was showing error
Error syncing load balancer: failed to ensure load balancer: can not extract scale set name from ipConfigurationID (/subscriptions/xxxxxxx/resourceGroups/xxxxxx/providers/Microsoft.Network/networkInterfaces/aks-karpenter-nodepool-xxxx/ipConfigurations/aks-karpenter-nodepool-xxxx)
let me know if there is something wrong with our service below
How should the docs be improved?
Please update the doc which inform more details on this limitation and this issue in some troubleshooting doc
Community Note
The text was updated successfully, but these errors were encountered: