AKS Standard loadbalancer Manually choosing allocated outbound ports differs in functionality

Krupakar Reddy 21 Reputation points
2022-04-07T08:30:52.403+00:00

AKS Standard loadbalancer Manually choosing allocated outbound ports differs in functionality.It uses the maxnode count logic when updating from cli or through arm template but uses the current node count when updating from portal. Kindly fix this ASAP

Azure Kubernetes Service (AKS)
Azure Kubernetes Service (AKS)
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
1,938 questions
{count} votes

Accepted answer
  1. KarishmaTiwari-MSFT 18,667 Reputation points Microsoft Employee
    2022-04-13T19:38:17.043+00:00

    Issue summary:
    Clarification on whether AKS Standard loadbalancer manually choosing allocated outbound ports differs in functionality. It seems like it uses the maxnode count logic when updating from cli or through arm template but uses the current node count when updating from portal.

    Recommended solution:
    Based on the discussion in the comments above, it looks like when you are using Az CLI or arm template, it actually changes the AKS profile and this will calculate the max node count and validate if the number is correct. But via the portal, if a user is changing the load balancer configuration directly, that will not change the AKS profile so there won't be validation on the numbers.

    I would recommend to change it using CLI or Arm template and not using portal as those would be two different operations.


1 additional answer

Sort by: Most helpful
  1. Krupakar Reddy 21 Reputation points
    2022-04-11T04:34:28.09+00:00

    @KarishmaTiwari-MSFT Scenario:- its for example

    one nodepool with cluster autoscaler enabled and max node count of 50
    one outgoing loadbalancer public ip that can accomodate 64000 ports.

    So if i try to assign 2560 ports per node i.e 50*2560-128000 it exceeds 64k ports ,so it throws error through az cli and arm template which is correct but not through azure portal.(it doesnt throw error and updates successfully)

    Reference to the case raised erlier:-2112150060001731