-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When creating a load balance service inside a UDN namespace, user can not access the service via ClusterIP or cluster DNS
Example:
yzamir@fedora:~$ oc get svc -n udn-dev udn-test-vm-1096-vd8ht-service NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE udn-test-vm-1096-vd8ht-service LoadBalancer 172.30.23.26 10.0.59.167 8080:32615/TCP,2112:32096/TCP 39h
What should happen:
User can access the service via the cluster IP 172.30.23.26 or http://udn-test-vm-1096-vd8ht-service.udn-dev.svc:2112
What happen:
User can not access the service via the cluster IP 172.30.23.26 or http://udn-test-vm-1096-vd8ht-service.udn-dev.svc:2112
Workaround:
- Use pod IP directly
- Use the LB ingress IP - [ oc get svc -n udn-dev udn-test-vm-1096-vd8ht-service -o json | jq .status.loadBalancer.ingress[0].ip ]