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

Bind management interface to 0.0.0.0

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Done
    • Icon: Major Major
    • None
    • EAPCD 15.0.GA
    • EAP_CD
    • Cloud Sprint 32

      For CLOUD-3074, EAP metrics will be directly exposed by EAP using its metrics subsystem.
      The HTTP endpoint /metric is exposed on the HTTP management interface which is bound to 127.0.0.1 by default (both in the standalone-openshift.xml[1] and in the openshift-launch.sh[2] script).

      To be able to be queried inside Kubernetes cluster, this HTTP management needs to be bound to 0.0.0.0 (and the management-http port needs to be exposed as a containerPort).
      This implies that all management endpoints (not only /metrics but also /health and /management) would be exposed to the Kubernetes cluster.

      The safest way to enable this change is to modify standalone-openshift.xml[3] to change the management interface to use 0.0.0.0 (to preserve the behaviour of the -bmanagement parameter).

      [1] https://github.com/jboss-container-images/jboss-eap-modules/blob/master/jboss-eap-cd15-openshift/added/standalone-openshift.xml#L609
      [2] https://github.com/jboss-container-images/jboss-eap-modules/blob/master/os-eap7-launch/added/openshift-launch.sh#L29
      [3] https://github.com/jboss-container-images/jboss-eap-modules/blob/34a1d6a6d479f488f5dca58a280613909340d26c/jboss-eap-cd15-openshift/added/standalone-openshift.xml#L596

              kwills@redhat.com Ken Wills
              jmesnil1@redhat.com Jeff Mesnil
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: