-
Notifications
You must be signed in to change notification settings - Fork 215
Support Address space update on peered VNET - Update VirtualNetwork from v1api20201101 #4224
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.
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
Comments
Latest stable version appears to be 2023-11-01. |
I think there's a 2024-01-01. I noticed this was way out of date when doing work on #4119. I can take this one and try to get it in for 2.10. I think Networking has changed the way they version their APIs so that every resource is in every API version, which makes it way easier to keep things up to date because you can just update everything to the latest version rather than having to manually figure out if there was a new version published for every resource type. |
Begrudgingly pushing this to 2.11, I meant to get it in to 2.10 but we're past due and I haven't had time yet. It should make 2.11 though as I have it partially done locally... 2.11 will be a short release cycle too (sometime mid Nov is current thinking) |
Updated the following resources API versions: Updated to v1api20240301 * BastionHost * NatGateway * PublicIPPrefix * PrivateEndpoint * PrivateLinkService * PrivateEndpoints_PrivateDnsZoneGroup * LoadBalancers_InboundNatRule * LoadBalancer * NetworkInterface * NetworkSecurityGroup * NetworkSecurityGroups_SecurityRule * PublicIPAddress * RouteTable * RouteTables_Route * VirtualNetwork * VirtualNetworkGateway * VirtualNetworks_Subnet * VirtualNetworks_VirtualNetworkPeering Updated to v1api20240601 * PrivateDnsZone * PrivateDnsZones_VirtualNetworkLink * PrivateDnsZones_A * PrivateDnsZones_AAAA * PrivateDnsZones_CNAME * PrivateDnsZones_MX * PrivateDnsZones_SRV * PrivateDnsZones_PTR * PrivateDnsZones_TXT This fixes Azure#4224.
Updated the following resources API versions: Updated to v1api20240301 * BastionHost * NatGateway * PublicIPPrefix * PrivateEndpoint * PrivateLinkService * PrivateEndpoints_PrivateDnsZoneGroup * LoadBalancers_InboundNatRule * LoadBalancer * NetworkInterface * NetworkSecurityGroup * NetworkSecurityGroups_SecurityRule * PublicIPAddress * RouteTable * RouteTables_Route * VirtualNetwork * VirtualNetworkGateway * VirtualNetworks_Subnet * VirtualNetworks_VirtualNetworkPeering Updated to v1api20240601 * PrivateDnsZone * PrivateDnsZones_VirtualNetworkLink * PrivateDnsZones_A * PrivateDnsZones_AAAA * PrivateDnsZones_CNAME * PrivateDnsZones_MX * PrivateDnsZones_SRV * PrivateDnsZones_PTR * PrivateDnsZones_TXT This fixes #4224.
Describe the current behavior
adding addressPrefixes in an existing VNet with peerings results in an error
MinimumApiVersionNotSpecifiedForAddressSpaceUpdateInPeeredVnet
Address space update operation on virtual network can not be performed as the minimum required API version for working with Vnet Peering is 2021-01-01, and the provided client API version is 2020-11-01.: PUT https://management.azure.com/subscriptions/.../resourceGroups/rg-aks/providers/Microsoft.Network/virtualNetworks/vnet-aks-001
Describe the improvement
Update API version for VirtualNetwork from current v1api20201101 to min v1api20210101
The text was updated successfully, but these errors were encountered: