LoadBalancer service Type in OpenShift deployment has confusing detailes

With OpenShift deployment (based on https://review.openstack.org/#/c/497933/), deployment of the following application provided confusing details of the created service:
 kubectl run --image=celebdor/kuryr-demo kuryr-demo901
 kubectl expose deploy/kuryr-demo901 --port 80 --target-port 8080 --type=LoadBalancer

This created the following service:
kubectl describe svc:
Name: kuryr-demo901
Namespace: default
Labels: run=kuryr-demo901
Annotations: openstack.org/kuryr-lbaas-spec={"versioned_object.data": {"ip": "10.0.0.152", "lb_ip": null, "ports": [{"versioned_object.data": {"name": null, "port": 80, "protocol": "TCP"}, "versioned_object.name":...
Selector: run=kuryr-demo901
Type: LoadBalancer
IP: 10.0.0.152
External IPs: 172.29.33.223
LoadBalancer Ingress: 172.24.4.4
Port: <unset> 80/TCP
NodePort: <unset> 32379/TCP
Endpoints: 10.0.0.67:8080,10.0.0.72:8080
Session Affinity: None
Events: <none>

With external IP that is not on any valid network that kuryr is aware of (neither exist in neutron)