How can we improve Azure Networking?

← Networking

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.

1,393 votes
Vote
Sign in
(thinking…)
Sign in with: Microsoft
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Rohit Kumar shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

60 comments

Sign in
(thinking…)
Sign in with: Microsoft
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Kaat, Robert te commented  ·   ·  Flag as inappropriate

    AKS cluster upgrades cause downtime sometimes for a whole day because of slow loadbalancer updates. To update my loadbalancers to Standard sku instead of Basic, I also need to update IP-address skus. Since this is impossible, I loose IP-addresses. For incoming traffic I can manage this through DNS probably, using CNAMEs, etc. For egress traffic I cannot: partners have been white listing our IPs and now I have to confront everyone with this change.

  • Steve Kaye commented  ·   ·  Flag as inappropriate

    This is a major issue for people migrating from ASM. When I migrate my IP address, it comes over as the basic SKU. This is very limiting and prevents me from using a Standard Load Balancer or an Application Gateway leaving me without an SLA backed component on that part of our solution.

    It also prevents us from replicating the current ASM feature where all our servers have one external IP address because you can't add machines from different Availability Sets to a basic load balancer.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Do it team. what are you waiting for, your customer is troubled enough to mov eto AWS.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Is there a rough ETA yet? We need to make some road maps decisions based on this feature.

  • Kim commented  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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?

  • Tamir commented  ·   ·  Flag as inappropriate

    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.

← Previous 1 3

Networking: Load Balancer

Categories

Feedback and Knowledge Base

(thinking…)
Hosted by UserVoice