Uploaded image for project: 'Cloud Enablement'
  1. Cloud Enablement
  2. CLOUD-2364

[EAP7] Allow Openshift to override EAP bind address

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • None
    • EAP7, EAP_CD
    • None

    Description

      Note this requires some investigation, so perhaps this is not an accurate description of the issue yet.

      Using ISTIO, proxying appears to be problematic with the default address binding. We should probably honor -Djboss.bind.address / just use 0.0.0.0.

      From the report:

      "JBoss EAP appeared to come up normally, however the proxy could never talk to it, even if I rsh'd into the EAP container itself, I could not talk to it with curl. I believe this is because the containerized version of JBoss EAP always binds to the IP address reported by `hostname -i` and you can't override it with -Djboss.bind.address - it's hard-coded in the xPaaS image scripts. All other services that I use bind to 0.0.0.0 and that works great with Envoy/Istio. I imagine there's a way to make it work, but I ran out of time and switched to WF Swarm where I could override the bind address."

      Attachments

        Activity

          People

            kwills@redhat.com Ken Wills
            kwills@redhat.com Ken Wills
            Marek Schmidt Marek Schmidt
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: