Load balancer requirements

Use load balancers to prevent server overload and improve application availability. BMC Helix IT Operations Management supports F5 or any other load balancers.

Related topics

Configuration-file-settings

The following load balancer SSL methods are supported:

  • SSL Offloading at the load balancer
  • SSL Passthrough to offload at the Ingress Controller
  • SSL Full Proxy

For an improved performance, we recommend SSL offloading at the load balancer. However, all other methods are also supported.

The following headers are required for SSL offloading or SSL full proxy:

  • X-Forwarded-proto
  • X-Forwarded-port
  • X-Forwarded-host

You can also add the X-Forwarded-for header for debugging purposes.

Except for BMC Discovery URL, create the following FQDNs with a DNS entry that points to the same IP of the load balancer:

The BMC Discovery URL should point to the IP of BMC Discovery.

The property names are used in the infra.config and deployment.config files during deployment. Make sure that the URLs are in the same domain.

Important

After the ingress controller is configured, if you browse to the URLs, you must get 'default backend -404' error.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*