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.

Sign up for GitHub

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

Jump to bottom

[Feature request]: Support of node pool spread across different Vnets #2595

Open
ARD92 opened this issue Oct 13, 2021 · 46 comments
Open

[Feature request]: Support of node pool spread across different Vnets #2595

ARD92 opened this issue Oct 13, 2021 · 46 comments
Labels
feature-request Requested Features networking/azcni

Comments

@ARD92
Copy link

ARD92 commented Oct 13, 2021

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.
@ghost ghost added the triage label Oct 13, 2021
@ghost
Copy link

ghost commented Oct 13, 2021

Hi ARD92, AKS bot here 👋
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:

  1. If this case is urgent, please open a Support Request so that our 24/7 support team may help you faster.
  2. Please abide by the AKS repo Guidelines and Code of Conduct.
  3. If you're having an issue, could it be described on the AKS Troubleshooting guides or AKS Diagnostics?
  4. Make sure your subscribed to the AKS Release Notes to keep up to date with all that's new on AKS.
  5. 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.
  6. If you have a question, do take a look at our AKS FAQ. We place the most common ones there!

@ARD92 ARD92 changed the title Support of node pool spread across different Vnets [Feature request]: Support of node pool spread across different Vnets Oct 13, 2021
@ghost ghost removed the triage label Oct 14, 2021
@ghost
Copy link

ghost commented Oct 14, 2021

@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:

networking/azcni, triage
Milestone: -

@ghost ghost added the action-required label Nov 8, 2021
@ghost
Copy link

ghost commented Nov 13, 2021

Action required from @Azure/aks-pm

@ghost ghost added the Needs Attention 👋 Issues needs attention/assignee/owner label Nov 13, 2021
@ghost
Copy link

ghost commented Nov 28, 2021

Issue needing attention of @Azure/aks-leads

20 similar comments
@ghost
Copy link

ghost commented Dec 14, 2021

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Dec 29, 2021

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Jan 13, 2022

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Jan 28, 2022

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Feb 13, 2022

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Feb 28, 2022

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Mar 15, 2022

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Mar 30, 2022

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Apr 14, 2022

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Apr 30, 2022

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented May 15, 2022

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented May 30, 2022

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Jun 14, 2022

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Jun 29, 2022

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Jul 14, 2022

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Jul 29, 2022

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Aug 13, 2022

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Aug 29, 2022

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Sep 13, 2022

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Sep 28, 2022

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Oct 13, 2022

Issue needing attention of @Azure/aks-leads

19 similar comments
@ghost
Copy link

ghost commented Oct 29, 2022

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Nov 13, 2022

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Nov 28, 2022

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Dec 13, 2022

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Dec 29, 2022

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Jan 13, 2023

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Jan 28, 2023

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Feb 12, 2023

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Feb 27, 2023

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Mar 15, 2023

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Mar 30, 2023

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Apr 14, 2023

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Apr 29, 2023

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented May 14, 2023

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented May 30, 2023

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Jun 14, 2023

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Jun 29, 2023

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Jul 14, 2023

Issue needing attention of @Azure/aks-leads

@ghost
Copy link

ghost commented Jul 30, 2023

Issue needing attention of @Azure/aks-leads

@microsoft-github-policy-service microsoft-github-policy-service bot added the stale Stale issue label Feb 2, 2024
@microsoft-github-policy-service Microsoft GitHub Policy Service
Copy link
Contributor

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.

@microsoft-github-policy-service Microsoft GitHub Policy Service
Copy link
Contributor

Issue needing attention of @Azure/aks-leads

@AllenWen-at-Azure AllenWen-at-Azure added the feature-request Requested Features label Feb 9, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot removed Needs Attention 👋 Issues needs attention/assignee/owner action-required labels Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature-request Requested Features networking/azcni
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hieumoscow @ARD92 @AllenWen-at-Azure