BYO Custom VNET #199
Labels
area/nap
Issues or PRs related to Node Auto Provisioning (NAP)
area/networking
Issues or PRs related to networking
kind/feature
Categorizes issue or PR as related to a new feature.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Tell us about your request
Today, karpenter doesn't support specifying a custom vnet. We should implement the basic functionality to allow users to specify a custom vnet in the AKS API, then propagate those settings and configurations to be used by karpenter.
Step one of this work would be to modify handleVNET. We should fetch the VNETSubnetID from the AKS Agentpool. If it is unset on the default systempool, then we should just use the standard VNET here.
This issue should solve the case of karpenter crashing when a custom
vnetSubnetID
is specifed on the managed clusterAre you currently working around this issue?
No.
Additional Context
No response
Attachments
No response
Community Note
The text was updated successfully, but these errors were encountered: