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
❯ helm ls -A --all -o json | jq '.[] | select(.name=="karpenter") | .app_version' -r
0.5.0
❯ kubectl version | grep Server
Server Version: v1.28.5
Expected Behavior
The pods on the nodes should be able to get the IP.
Actual Behavior
Karpenter can spin up a new node and register it to the cluster but pods are unable to get the IP.
Steps to Reproduce the Problem
Create an AKS cluster with a different subnet for host and pods
The resource groups of vNet and AKS are also different
Follow the README and deploy the application
Resource Specs and Logs
All the pods that land on the node spun up by Karpenter throw this error. I think, I need a way to define the subnet ID for Pods, maybe an environment variable POD_SUBNET_ID?
plugin type="azure-vnet" failed (add): IPAM Invoker Add failed with error: Failed to allocate pool: Failed to delegate: Failed to allocate address: No available addresses
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
The text was updated successfully, but these errors were encountered:
spaceiq-vk
changed the title
Karpenter node is unable to join the k8s cluster
Ability to define a subnet for pods?
Jul 10, 2024
Hi,
Are you using Azure CNI Pod Subnet network configuration?
I'm facing the same issue with karpenter nodes. I have separate subnets for nodes and pods. But does karpender not support such a configuration or I'm wrong?
Version
Expected Behavior
The pods on the nodes should be able to get the IP.
Actual Behavior
Karpenter can spin up a new node and register it to the cluster but pods are unable to get the IP.
Steps to Reproduce the Problem
Resource Specs and Logs
All the pods that land on the node spun up by Karpenter throw this error. I think, I need a way to define the subnet ID for Pods, maybe an environment variable
POD_SUBNET_ID
?Community Note
The text was updated successfully, but these errors were encountered: