Kubernetes - Azure Load Balancer provisioning fails - name too long

[azure]

Kubernetes - Azure Load Balancer provisioning fails - name too long

[SorraTheOrc]

I can confirm this is a bug. I've reproduced it and worked around it by using a shorter service and resource group name (which involves redeploying the cluster).

[amritb]

@jdumars as per our discussion https://kubernetes.slack.com/archives/C5HJXTT9Q/p1499199490084628

[davenemeth]

@marceldempers Thanks for this detailed description, I have the same issue.

The name seems to be generated the following way: [container service]-[resource group]-[random 6]-[random 32]
That means we have 39 characters for the container service and resource group names together.

Is there any chance to influence how the load balancer name is generated or do we have to recreate all our resource groups and container services as a workaround?

Renaming the resource is not possible: https://feedback.azure.com/forums/281804-azure-resource-manager/suggestions/6017710-rename-resource-groups

[jorgearteiro]

Yep, same thing here. Re-creating everything...

[lironmo]

same here:
Warning CreatingLoadBalancerFailed 3m (x36 over 2h) service-controller
Error creating load balancer (will retry): Failed to create load balancer for service kube-system/kibana-logging:
network.PublicIPAddressesClient#CreateOrUpdate:
Failure responding to request: StatusCode=400 -- Original Error:
autorest/azure: Service returned an error. Status=400
Code="InvalidResourceName" Message="Resource name xxx-managed-lod-northeurope-lhsn4dewd34mgmt-aa8d2afbb2cf111e899a9000d3aba07f
is invalid. The name can be up to 80 characters long.
It must begin with a word character, and it must end with a word character or with ''. The name may contain word characters or '.', '-', ''." Details=[]
xxx-managed-lod-northeurope-lhsn4dewd34mgmt-aa8d2afbb2cf111e899a9000d3aba07f

[aegershman]

Using Pivotal Container Service (PKS) on Azure & ran into this

Resource name a6e3b5380eaca11e9ac9f000d3a42ae6-sandbox-centralus-xxxxxxxx-infrastructure-subnet is invalid. The name can be up to 80 characters long. It must begin with a word character, and it must end with a word character or with ''. The name may contain word characters or '.', '-', ''.

In my case the generated resource name is 81 characters long.

;_;