CODEWITHSUNDEEP
azureipkubernetesazure-load-balancer
user_mda
user_mda

Reputation: 19418

Service of Type LoadBalancer on AKS

I am using AKS and when I create a service of type LoadBalancer, it creates a service and allocates and IP but the following requests to create services of type loadbalancer the IP does not get allocated and it shows <pending> state forever

I verified that the quotas for public IP are witin range. Is this a limitation that I am hitting? How should I go abot debugging this?

This is a relevant link https://github.com/Azure/acs-engine/issues/737

I see this when I descibe the service

 Warning  CreatingLoadBalancerFailed  18s (x5 over 1m)  service-controller  Error creating load balancer (will retry): Failed to create load balancer for service kubernetestypo32/hello-world-serviceypo32: network.LoadBalancersClient#CreateOrUpdate: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="LoadBalancerFrontendIPConfigurationCountLimitReached" Message="Basicsku load balancer /subscriptions/c28f7a55-03f7-41fb-b96b-011eff3ce42e/resourceGroups/MC_spalshikResourceGroup_spalshikK8sCluster_eastus/providers/Microsoft.Network/loadBalancers/kubernetes cannot have more than 10 FrontendIPConfigurations." Details=[]

Upvotes: 0

Views: 690

Answers (1)

4c74356b41
4c74356b41

Reputation: 72191

So in this case the problem was in a stale ip addresses in the load balancer configurations. They need to be removed.

proper way of doing that - removing stale kubernetes services

Upvotes: 1

Related Questions