Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Karpenter Node Creation Fails with "Node not registered with cluster" on Azure AKS with Azure CNI and Calico #571

Closed
amirfatemiichoosr opened this issue Nov 11, 2024 · 2 comments
Labels
area/networking Issues or PRs related to networking

Comments

@amirfatemiichoosr
Copy link

Version

Karpenter Version: v0.7.0

Kubernetes Version: v1.30.5

Expected Behavior

Karpenter should successfully create and register new nodes in the AKS cluster, bringing them to a "Ready" state for workloads.

Actual Behavior

Karpenter creates new nodes, but they remain in an "Initialized" state and fail to register with the cluster. The status for "Ready" displays UnhealthyDependents, and messages indicate "Node not registered with cluster."

Steps to Reproduce the Problem

  1. Configure an AKS cluster with the following settings:
  • OS: AzureLinux
  • Network configuration: Azure CNI Node Subnet
  • Network policy: Calico
  1. Deploy Karpenter on the AKS cluster using Terraform.
  2. Create an AKSNodeClass and a NodePool.
    4 Request a node through a NodeClaim.
  3. Observe the status of the new node.

Resource Specs and Logs

Node Logs:

- lastTransitionTime: '2024-11-11T18:25:14Z'
  message: Node not registered with cluster
  reason: NodeNotFound
  status: Unknown
  type: Initialized
- lastTransitionTime: '2024-11-11T18:25:14Z'
  message: ''
  reason: Launched
  status: 'True'
  type: Launched
- lastTransitionTime: '2024-11-11T18:25:14Z'
  message: Initialized=Unknown, Registered=Unknown
  reason: UnhealthyDependents
  status: Unknown
  type: Ready

Karpenter log pod:

{"level":"info","ts":1731348521.1395092,"logger":"fallback","caller":"instance/instance.go:152","msg":"launched new instance","launched-instance":"/subscriptions/***/resourceGroups/****/providers/Microsoft.Compute/virtualMachines/aks-general-purpose-79mc9","hostname":"aks-general-purpose-79mc9","type":"Standard_D4ls_v5","zone":"3","capacity-type":"on-demand"}
{"level":"INFO","time":"2024-11-11T18:08:41.139Z","logger":"controller","caller":"lifecycle/launch.go:61","message":"launched nodeclaim","commit":"d83a94c","controller":"nodeclaim.lifecycle","controllerGroup":"karpenter.sh","controllerKind":"NodeClaim","NodeClaim":{"name":"general-purpose-79mc9"},"namespace":"","name":"general-purpose-79mc9","reconcileID":"***","provider-id":"azure:///subscriptions/***/resourceGroups/****/providers/Microsoft.Compute/virtualMachines/aks-general-purpose-79mc9","instance-type":"Standard_D4ls_v5","zone":"","capacity-type":"on-demand","allocatable":{"cpu":"3860m","ephemeral-storage":"128G","memory":"5226731929","pods":"110"}}

Community Note

  • 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
@Bryce-Soghigian
Copy link
Collaborator

We do not support calico at this time.

@Bryce-Soghigian Bryce-Soghigian added the area/networking Issues or PRs related to networking label Nov 11, 2024
@Bryce-Soghigian
Copy link
Collaborator

Don't support calico

@Bryce-Soghigian Bryce-Soghigian closed this as not planned Won't fix, can't repro, duplicate, stale Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/networking Issues or PRs related to networking
Projects
None yet
Development

No branches or pull requests

2 participants