azurerm kubernetes resource shows vnet clash

[ghost]

This issue was originally opened by @sibh8 as hashicorp/terraform#17494. It was migrated here as a result of the provider split. The original body of the issue is below.

---

Hello,

Azurerm kubernetes cluster resource shows a vnet clash between default 10.0.0.0/8 vnet and the my custom vnet specified in vnet_subnet_id. Please can you help me understand if the AKS is getting created in custom VNET??

Thanks

[tombuildsstuff]

hi @sibh8

Thanks for opening this issue

So that we can take a look into this issue - would it be possible for you to post the Terraform Configuration that you're using? AKS actually deploys its resources in a separate Resource Group - so I'm wondering if they're being deployed in a separate network

Thanks!

[tombuildsstuff]

ping @sibh8 :)

[sibh8]

Hello Tom,

Yes, a separate network is getting created. I have used exactly he same template as mentioned in the example on the terraform website just adding my custom Vnetsubnetid parameter

Thanks.

[tombuildsstuff]

hi @sibh8

This issue was caused by a behavioural change in the Azure API which Terraform now documents - as such I'm going to close this issue for the moment. Would you be able to upgrade to v1.13.0 of the AzureRM Provider and let us know if this is still an issue?

Thanks!

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!