With a couple of our projects we started to provision small vnets. Only fitting one or two subnets. What do you think. Now I think of it it would make sense that vnet becomes "dumb" and just becomes a group of subnets for routing purposes.
I think that would work for you and I. Because we’re both app dev people 😁 but I'm almost certain I just heard a bunch of networking/security guys audibly cringe.. 🤣🥴
@@azure-terraformer why? There is almost zero config on vnet level besides dns server and connected private zones. Nsg, routing, service endpoints etc. are all on subnet level
![🔴 ฟุตบอลแชมป์กีฬา 7HD แชมเปียน คัพ 2024 [รอบรองชนะเลิศ]](http://i.ytimg.com/vi/zPm8ClLVhoE/mqdefault.jpg)
With a couple of our projects we started to provision small vnets. Only fitting one or two subnets. What do you think. Now I think of it it would make sense that vnet becomes "dumb" and just becomes a group of subnets for routing purposes.
I think that would work for you and I. Because we’re both app dev people 😁 but I'm almost certain I just heard a bunch of networking/security guys audibly cringe.. 🤣🥴
@@azure-terraformer why? There is almost zero config on vnet level besides dns server and connected private zones. Nsg, routing, service endpoints etc. are all on subnet level
Oh I think I see what you are saying. This is almost how GCP virtual networks work. The VNet is just a logical container for subnets
Interesting idea. Might require some structural changes to the underlying RP. Not sure.