Load Balancer and Public IP SKU.
There must be an option of Upgrading Public IP SKU from Basic to Standard without losing Static PIP as it is a creating a big road block when we do any planning like moving existing PIP behind any NVA Standard Load balancer.
If any existing Production Server are already running on Basic PIP then it is very tough to make any decisions to upgrade SKU or move it behind any Standard ELB.
Need suggestion here how and till what time we can overcome here.
Rohit Kumar
shared this idea
Thank you for the feedback. We are working on prereqs to make this possible. Not in scope for CY2019.
— Christian
48 comments
-
Anonymous
commented
Do it team. what are you waiting for, your customer is troubled enough to mov eto AWS.
-
Anonymous
commented
Is there a rough ETA yet? We need to make some road maps decisions based on this feature.
-
Brice GUILLAUME
commented
We also need a solution, this kind of limitation is ridiculus...
-
Kim
commented
It took years to migrate our Classic environment, simply because we cannot change our Public IPs (due to integrations with numerous customers that needed our IP whitelisted). The migrated IPs all have Basic SKUs. Now we want to use Application Gateways (with WAF), but unable to do so because of the inability to change the SKU of a Public IP. This seems to be a ludicrous restriction and a blocker for many.
-
Anonymous
commented
Thread started on June 26, 2018- 18 months ago! :) Got attention one year later. Planned but NOT for CY 2019... So, CY 2020? Maybe we get to use free A-lastic IP's after the long wait:)
-
Benny
commented
Hi, i have a migration depending on it, would love to know is it in the roadmap of 2020?
If so, any chance you know which quarter in 2020? -
Manjoor
commented
We are in 2020 now. Any update for current year?
-
Tamir
commented
Having the same issue on our production clusters for AKS that were created prior to the Standard LB support. currently facing SNAT issues and trouble to migrate as we have some dependency (IP whitelisting on our customer's side for example) on the current IP addresses which are in basic SKU and no migration option on Azure rather than creating all from scratch.
-
Jeff Puccinelli
commented
This is disappointing.
We have deployed our services using the Basic SKU Public IP and now wanted to upgrade to Standard to use AKS Standard Load balancers and use Traffic Manager to geo route between regions. We cannot change our IPs as we have been using them for public facing APIs and B2B services for a couple of years now. I feel that we have painted ourselves into a corner with this.
Please provide a resolution.
-
Umair Syed
commented
what is the implications on internal LB that doesnt have PIP? Can we upgrade the existing instance or we have to delete the existing and deplpy a new instance?
-
Jonathan
commented
I would also ask to convert from standard to basic
-
Tony LaGrassa
commented
Would appreciate resolution to this.
-
Steven Yong
commented
Surely Microsoft is not expecting customer to change PIP for an upgrade this cause a lot of reworks on B2B service where it will require firewall change at BSB client firewall at the best estimate about 3 months of efforts. Is Microsoft going to help out with funding for this unnecessary change?
-
D Kulkarni
commented
We need a solution for this urgently.
-
Junwei Huang (MVP)
commented
is it planned in CY2020?
-
Sandip
commented
I have created public IP SKU in Basic now i want to switch to standard but its very hard to hear that it's not possible and its not possible in CY2019. Very disppointment.
-
Robert Buckmaster
commented
What a horrible joke of a move by Microsoft. When we created our Load Balancers and Public IP's in Azure RM, there was NO SKU choice. Now they are basic and limited. Microsoft support is telling me I have to completely DELETE and LOSE my "basic" Public IP's in order to recreate and gain the Standard sku functionality. IDIOTIC and completely NOT CUSTOMER FOCUSED what you've done here! This sku value should be able to be modified, and I am sure that it can be on the backend but we are told sorry, no.
-
Anonymous
commented
is it planned for Q12020?
-
Jari Turkia
commented
What!
You cannot change public IP address SKU!!!?At the time I created those addresses, no SKU choice was available and now you cannot change it? Is this for real or are these guys just joking?
-
Vipin Yadav
commented
Really surprised by MS's approach on this issue. Its stand still since more than an year and there r so many clients like us who are impacted by this.