HAproxy service

The HAproxy service enables load balancing and SSL termination. After the Gateway hosts are set up, the HPE Ezmeral Runtime Enterprise Controller automatically starts using the Gateway proxy set for container port mappings.

Service endpoints for a Kubernetes cluster in a deployment appear in the Gateway Mappings column of the table on the Kubernetes Service Endpoints screen. See Endpoints Tab.

HAproxy Stats UI

HAProxy provides a "Stats" web UI for monitoring the health of all back-end service endpoints. The UI is available over HTTP on port 8081 of each Gateway host, with username haproxy and password haproxy. The Gateway host uses the Stats web UI to provide the HAProxy service status information on the HPE Ezmeral Runtime Enterprise Dashboard.

  • Beginning with HPE Ezmeral Runtime Enterprise 5.4.1, the HAProxy Stats web page is configured by default to accessible from the local host only. To enable temporary access from other hosts, do the following on each Gateway host:
    1. Open the file /opt/bluedata/common-install/scripts/haproxy/haproxy_globals.cfg for editing.
    2. In the listen stats section, find the following line:

      bind 127.0.0.1:8081
    3. Change this line to the following:
      bind 0.0.0.0:8081
    4. Restart the service by executing the following command on the Gateway host:
      systemctl restart bds-controller

    This change does not persist across software upgrades, and is not replicated onto new hosts.

  • For HPE Ezmeral Runtime Enterprise 5.4.0 and prior releases, the HAProxy Stats web page is configured by default to be accessible from any host on the network. To restrict access to the local host only, do the following on each Gateway host:

    1. Open the file /opt/bluedata/common-install/scripts/haproxy/haproxy_globals.cfg for editing.
    2. In the listen stats section, find the following line:

      bind 0.0.0.0:8081
    3. Change this line to the following:
      bind 127.0.0.1:8081
    4. Restart the service by executing the following command on the Gateway host:
      systemctl restart bds-controller

    This change does not persist across software upgrades, and is not replicated onto new hosts.