Azure
[Feature request]: Support of node pool spread across different Vnets
Currently when we create an AKS cluster, the node pool is within a single vnet. Issue #1338 allows one to create the node pool members with different subnets but not spread across vnets.
One will have to use vnet peering but the AKS cluster being managed is only within scope of the single vnet it was created. if multiple vnets have to be managed each will be its own cluster.
This is an enhancement request for supporting the AKS to have its node pool across different vnets. The underlying VMSS used would have vms in different vnets accordingly.
Hi ARD92, AKS bot here :wave: Thank you for posting on the AKS Repo, I'll do my best to get a kind human from the AKS team to assist you.
I might be just a bot, but I'm told my suggestions are normally quite good, as such:
- If this case is urgent, please open a Support Request so that our 24/7 support team may help you faster.
- Please abide by the AKS repo Guidelines and Code of Conduct.
- If you're having an issue, could it be described on the AKS Troubleshooting guides or AKS Diagnostics?
- Make sure your subscribed to the AKS Release Notes to keep up to date with all that's new on AKS.
- Make sure there isn't a duplicate of this issue already reported. If there is, feel free to close this one and '+1' the existing issue.
- If you have a question, do take a look at our AKS FAQ. We place the most common ones there!
@aanandr, @palma21 would you be able to assist?
Issue Details
Currently when we create an AKS cluster, the node pool is within a single vnet. Issue #1338 allows one to create the node pool members with different subnets but not spread across vnets.
One will have to use vnet peering but the AKS cluster being managed is only within scope of the single vnet it was created. if multiple vnets have to be managed each will be its own cluster.
This is an enhancement request for supporting the AKS to have its node pool across different vnets. The underlying VMSS used would have vms in different vnets accordingly.
| Author: | ARD92 |
|---|---|
| Assignees: | - |
| Labels: |
|
| Milestone: | - |