Load balancer requirements

Use an external load balancer to redirect the external URLs to the NGNIX Ingress controller within the cluster. BMC Helix IT Operations Management supports all load balancers. We have certified the F5 load balancer.

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 virtual IP (VIP) 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.

Parameter nameDescriptionProductFormatExampleMust be configured in the load balancer?Must have a DNS entry?File name
LB_HOST

Specify a URL to create the load balancer host. The BMC Helix Single Sign-on ingress uses this URL to access the BMC Helix Single Sign-on administration console. 

All<any unique string>.$DOMAINlb.mydomain.bmc.comYesYesconfigs/infra.config
TMS_LB_HOSTSpecify a URL to create the Tenant Management System host.  The value of this parameter is used by the tenant management system ingress.All<any unique string>.$DOMAINtms.mydomain.bmc.com YesYesconfigs/infra.config
MINIO_LB_HOSTSpecify a URL to create a  MinIO storage. This value is used by the MinIO ingress. All<any unique string>.$DOMAINminio.mydomain.bmc.comYesYesconfigs/infra.config

MINIO_API_LB_HOST 

Specify a URL to create a MinIO storage. All the API based operations are performed using this URL. This URL is used to create a  MinIO bucket.All<a unique string>.$DOMAINminio-api.mydomain.bmc.comYesYesconfigs/infra.config

COMPANY_NAME TENANT_TYPE ENVIRONMENT DOMAIN

Important: For COMPANY_NAME,  specify the name of the tenant name.

Use the parameters to construct a tenant URL.

Important: Use the same value that you set for the TENANT_DOMAIN_HOST parameter in the infra.config file.

All$COMPANY_NAME-$TENANT_TYPE-$ENVIRONMENT.$DOMAINpurplekite-tyrion-dev-mydomain.bmc.comYesYesconfigs/deployment.config for ENVIRONMENT and configs/infra.config for the others

KIBANA_LB_HOST

Important: KIBANA_LB_HOST is required only if Helix logging is set to on.

Specify a URL to create a Kibana load balancer host.  The BMC Helix Logging ingress uses the value of this parameter. The value of this parameter depends on the self-signed/CA-signed certificate or CA custom certificate. 

All<any unique string>.$DOMAINkibana-private-poc.mydomain.bmc.comYesYesconfigs/infra.config

COMPANY_NAME TENANT_TYPE ENVIRONMENT DOMAIN

Important: For COMPANY_NAME,  specify the name of the tenant name.

Use the parameters to construct a BMC Discovery URL.

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

  • BMC Helix IT Operations Management
  •  BMC Helix Continuous Optimization
$COMPANY_NAME-disc-$TENANT_TYPE-$ENVIRONMENT.$DOMAINpurplekite-disc-private-poc.mydomain.bmc.comNoYesconfigs/deployment.config for ENVIRONMENT and configs/infra.config for the others

Important

After the ingress controller is configured, if you browse to the URLs, you will get the message, 404 not found, which implies that the URLs are rightly getting redirected to the Ingress controller.

Was this page helpful? Yes No Submitting... Thank you

Comments