3
az network public-ip create --name <name> --resource-group <rg name> --allocation-method Static --dns-name <dns name>

{
  "publicIp": {
    "ipAddress": "1.2.3.4",
    ...
    "provisioningState": "Succeeded",
    ...
  }
}

$ kubectl describe svc -n kube-system ingressservice
...
Events:
  Type     Reason                      Age               From                Message
  ----     ------                      ----              ----                -------
  Normal   EnsuringLoadBalancer        9s (x2 over 24s)  service-controller  Ensuring load balancer
  Warning  CreatingLoadBalancerFailed  9s (x2 over 14s)  service-controller  Error creating load balancer (will retry): Failed to ensure load balancer for service kube-system/ingressservice: user supplied IP Address 1.2.3.4 was not found

Help? Shouldn't this just work? The IP is in the same resource group.

Is it an issue with AKS? It seems to work for ACS..

closed as unclear what you're asking by Jenny D, mdpc, colealtdelete, kasperd, MadHatter Dec 18 '17 at 7:15

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • When you say "just works" what do you mean? Don't you have to "associate" the new IP with either a NIC or an load balancer? – Lars Levie Nov 29 '17 at 22:05
  • No. It just has to be in the same RG. Then point the yaml config to that IP and it'll auto associate. – mmr Dec 4 '17 at 12:31
1

So. It turns out that AKS had created another RG besides the one I thought it was in. So moving the IPs to that RG solved the issue.

Not the answer you're looking for? Browse other questions tagged or ask your own question.