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.

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

[Feature]: Add warning for users of eventual change of default for "az network lb create" and "az network lb frontend-ip create" #21831

Closed
brianlehr opened this issue Mar 28, 2022 · 4 comments · Fixed by #22074
Assignees
Labels
Auto-Assign Auto assign by bot feature-request Network az network vnet/lb/nic/dns/etc...

Comments

@brianlehr
Copy link
Member

brianlehr commented Mar 28, 2022

In the latest profile and the profiles that use the same api-version as latest profile, the default public IP used for creation for an LB frontend with "az network lb create" and/or "az network lb frontend-ip create" will be changed from Basic to Standard. In advance of eventual breaking change, would like to add warning for users.

Similar change done for "az vm create" - #18662

@ghost ghost added the Network az network vnet/lb/nic/dns/etc... label Mar 28, 2022
@ghost ghost added this to the Backlog milestone Mar 28, 2022
@ghost ghost assigned jsntcy Mar 28, 2022
@ghost ghost added the Auto-Assign Auto assign by bot label Mar 28, 2022
@yonzhan
Copy link
Collaborator

yonzhan commented Mar 29, 2022

network

@brianlehr
Copy link
Member Author

brianlehr commented May 9, 2022

@necusjz @YuanyuanNi I am not seeing this as completed when I test with latest cloud shell. Please show me if this is wrong. otherwise we need to re-open this issue.

brian@Azure:~$ az network lb create --name testinglbbasic --resource-group upgradetest --location westus
{
"loadBalancer": {
"backendAddressPools": [
{
"etag": "W/"76bf8845-6c44-4d33-bfd0-fcb4a317b462"",
"id": "/subscriptions/6bb4a28a-db84-4e8a-b1dc-fabf7bd9f0b2/resourceGroups/upgradetest/providers/Microsoft.Network/loadBalancers/testinglbbasic/backendAddressPools/testinglbbasicbepool",
"name": "testinglbbasicbepool",
"properties": {
"provisioningState": "Succeeded"
},
"resourceGroup": "upgradetest",
"type": "Microsoft.Network/loadBalancers/backendAddressPools"
}
],
"frontendIPConfigurations": [
{
"etag": "W/"76bf8845-6c44-4d33-bfd0-fcb4a317b462"",
"id": "/subscriptions/6bb4a28a-db84-4e8a-b1dc-fabf7bd9f0b2/resourceGroups/upgradetest/providers/Microsoft.Network/loadBalancers/testinglbbasic/frontendIPConfigurations/LoadBalancerFrontEnd",
"name": "LoadBalancerFrontEnd",
"properties": {
"privateIPAllocationMethod": "Dynamic",
"provisioningState": "Succeeded",
"publicIPAddress": {
"id": "/subscriptions/6bb4a28a-db84-4e8a-b1dc-fabf7bd9f0b2/resourceGroups/upgradetest/providers/Microsoft.Network/publicIPAddresses/PublicIPtestinglbbasic",
"resourceGroup": "upgradetest"
}
},
"resourceGroup": "upgradetest",
"type": "Microsoft.Network/loadBalancers/frontendIPConfigurations"
}
],
"inboundNatPools": [],
"inboundNatRules": [],
"loadBalancingRules": [],
"probes": [],
"provisioningState": "Succeeded",
"resourceGuid": "3ca992e4-8bfe-48bd-96fb-c640eb93cb39"
}
}

@necusjz
Copy link
Member

necusjz commented May 10, 2022

@brianlehr, sorry for the inconvenience, it will be fixed by #22339.

@brianlehr
Copy link
Member Author

I see the warning now, thank you @necusjz

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment