LoadBalancer service Type in OpenShift deployment has confusing detailes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kuryr-kubernetes |
New
|
Medium
|
Yossi Boaron |
Bug Description
With OpenShift deployment (based on https:/
kubectl run --image=
kubectl expose deploy/
This created the following service:
kubectl describe svc:
Name: kuryr-demo901
Namespace: default
Labels: run=kuryr-demo901
Annotations: openstack.
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.
Session Affinity: None
Events: <none>
With external IP that is not on any valid network that kuryr is aware of (neither exist in neutron)
Changed in kuryr-kubernetes: | |
assignee: | nobody → yossib (yossi-boaron-1234) |
Changed in kuryr-kubernetes: | |
importance: | Undecided → Medium |