Azure / karpenter-provider-azure

AKS Karpenter Provider
Apache License 2.0
308 stars 46 forks source link

Node claim status not Ready: Node not launched (creating instance, failed to get next loadbalancer page) #386

Open tospe opened 4 weeks ago

tospe commented 4 weeks ago

Version

Kubernetes Version: v1.28.9

Expected Behavior

The Node Claim should be in the "Ready" status.

Actual Behavior

The node claim never reaches the ready status, nor does it launch the node.

When looking into the noclaim the message is "creating instance, failed to get next loadbalancer page"

Steps to Reproduce the Problem

Start a new aks with auto provisioning. In the begining everything works, after sometime something happens not longer able to connect.

Resource Specs and Logs

Status: Conditions: Last Transition Time: 2024-06-06T13:20:21Z Message: Node not launched Reason: NotLaunched Status: False Type: Initialized Last Transition Time: 2024-06-06T13:20:21Z Message: creating instance, failed to get next loadbalancer page: GET https://management.azure.com/subscriptions/******/resourceGroups/*****/providers/Microsoft.Network/loadBalancers -----------------------------------------------------... Reason: LaunchFailed Status: False Type: Launched Last Transition Time: 2024-06-06T13:20:21Z Message: Node not launched Reason: NotLaunched Status: False Type: Ready Last Transition Time: 2024-06-06T13:20:21Z Message: Node not launched Reason: NotLaunched Status: False Type: Registered Events:

Community Note