Issue with setting a custom public ip for ingress (aks)

[azzlack]

Creating a new Public IP in Azure and linking it with annotations does not seem to work anymore. Before, I could create a Public IP and set ingress.appscode.com/load-balancer-ip to that IP to use an A-record at my domain provider for a proper url. NOTE: This was with Voyager v7.0.0 and K8s v1.8.7.

Now when I do this, I get the following errors at the ingress:

kubectl describe service voyager-bkhub-haproxy -n bkhub-prod
Name:                     voyager-bkhub-haproxy
Namespace:                bkhub-prod
Labels:                   origin=voyager
                          origin-api-group=voyager.appscode.com
                          origin-name=bkhub-haproxy
Annotations:              ingress.appscode.com/last-applied-annotation-keys=
                          ingress.appscode.com/origin-api-schema=voyager.appscode.com/v1beta1
                          ingress.appscode.com/origin-name=bkhub-haproxy
Selector:                 origin-api-group=voyager.appscode.com,origin-name=bkhub-haproxy,origin=voyager
Type:                     LoadBalancer
IP:                       172.15.204.220
IP:                       137.117.191.71
LoadBalancer Ingress:     137.117.177.20
Port:                     tcp-80  80/TCP
TargetPort:               80/TCP
NodePort:                 tcp-80  30319/TCP
Endpoints:                172.16.1.12:80
Session Affinity:         None
External Traffic Policy:  Cluster
Events:
  Type     Reason                      Age                From                Message
  ----     ------                      ----               ----                -------
  Normal   EnsuredLoadBalancer         35m (x2 over 35m)  service-controller  Ensured load balancer
  Warning  CreatingLoadBalancerFailed  35m                service-controller  Error creating load balancer (will not retry): failed to persist updated status to apiserver, even after retries. Giving up: not persisting update to service 'bkhub-prod/voyager-bkhub-haproxy' that has been changed since we received it: Operation cannot be fulfilled on services "voyager-bkhub-haproxy": the object has been modified; please apply your changes to the latest version and try again
  Normal   LoadbalancerIP              14m                service-controller  -> 137.117.191.71
  Warning  CreatingLoadBalancerFailed  7m (x3 over 14m)   service-controller  Error creating load balancer (will retry): failed to ensure load balancer for service bkhub-prod/voyager-bkhub-haproxy: timed out waiting for the condition
  Normal   EnsuringLoadBalancer        2m (x15 over 39m)  service-controller  Ensuring load balancer

As you can see it also creates its own public ip which is associated with a load balancer in Azure. If I create an A-record pointing to 137.117.177.20 everything works, but if I point it to 137.117.191.71 all requests are timing out.

Am I doing anything wrong? Are there any changes in the later versions that I have missed?