-
Notifications
You must be signed in to change notification settings - Fork 43
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
BYO Custom VNET #199
Comments
I encountered the same issue as well. |
Going to keep this open until we have fully rolled out custom vnet support. We are working on cutting the release right now. |
The release has reached eastus. I tested today with the makefile commands posted in #326 to validate that bringing your own custom vnet works. Note for NAP has one extra step for BYO vnet which is to assign an RBAC role the cluster needs(see #326). Applying this role on existing clusters with the latest nap release should bring the karpenter pod out of crashloopbackoff and it will start provisioning nodes within 5 minutes of that role being applied. |
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: