Uploaded image for project: 'OpenShift Core Networking'
  1. OpenShift Core Networking
  2. CORENET-6370

LB service in UDN namespace accessible via IP but not via DNS

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Undefined Undefined
    • None
    • None
    • OVN Kubernetes
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 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 ]

              Unassigned Unassigned
              yzamir@redhat.com Yaacov Zamir
              None
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: