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

Ability to define a subnet for pods? #428

Open
spaceiq-vk opened this issue Jul 10, 2024 · 3 comments
Open

Ability to define a subnet for pods? #428

spaceiq-vk opened this issue Jul 10, 2024 · 3 comments
Labels
area/networking Issues or PRs related to networking

Comments

@spaceiq-vk
Copy link

spaceiq-vk commented Jul 10, 2024

Version

❯ 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

2024-07-10_22-32-24

2024-07-10_22-32-49

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
@spaceiq-vk spaceiq-vk changed the title Karpenter node is unable to join the k8s cluster Ability to define a subnet for pods? Jul 10, 2024
@bwodecki-lf
Copy link

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?

@Bryce-Soghigian
Copy link
Collaborator

Karpenter does not yet support pod subnet.

@Bryce-Soghigian Bryce-Soghigian added the area/networking Issues or PRs related to networking label Nov 14, 2024
@spaceiq-vk
Copy link
Author

Are you using Azure CNI Pod Subnet network configuration?

I am using Cilium.

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

3 participants