CAPZ creates a vnet, subnet while creating an AKS cluster.

[LochanRn]

/kind bug

What steps did you take and what happened:
[A clear and concise description of what the bug is.]
Create an AKS cluster from capz, without specifying vnet and subnet details

What did you expect to happen:
An aks cluster is created along with a vnet and subnet.

By default when a user creates an AKS cluster from az cli or the azure portal without specifying vnet and subnet details, AKS generates a vnet and subnet and manages it internally. The below image clearly shows VNET and SUBNET are Managed and user, has no access to the vnet and subnet created by AKS.

When an AKS cluster is created by CAPZ without specifying BYO vnet and subnet, CAPZ creates a VNET and a SUBNET.
As shown in the image below and user can access the subnet, vnet.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
The defaulting webhooks defined for vnet and subnet creates a default subnet and default vnet.

Environment:

• cluster-api-provider-azure version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):

[LochanRn]

@CecileRobertMichon @jackfrancis thoughts ??

[CecileRobertMichon]

@alexeldeib do you recall why the AKS implementation was done this way?

[alexeldeib]

at the time was there was no way to predict/extract the generated vnet name if you wanted to use it later (#1009 implemented the vnet behavior). What I’m struggling to remember, is if there was an issue with the *AKS* API with that, or if I was mostly preparing for #826 and never finished. I’m not sure if that behavior of the AKS api still exists, I can certainly check.

…

On Wed, Jan 18, 2023 at 1:13 PM Cecile Robert-Michon < ***@***.***> wrote: @alexeldeib <https://github.com/alexeldeib> do you recall why the AKS implementation was done this way? — Reply to this email directly, view it on GitHub <#3051 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABT4LWMIQC4U2P2XCQBVRF3WTAXF3ANCNFSM6AAAAAAT64GI3A> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[CecileRobertMichon]

#929 (comment) :D

[CecileRobertMichon]

/close

this is by design, no plans to fix currently

[k8s-ci-robot]

@CecileRobertMichon: Closing this issue.

In response to this:

/close

this is by design, no plans to fix currently

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.