Before you deploy the product, make sure that your environment meets the hardware and software requirements.
The Java Keytool is required on the system where you download the installer. OpenJDK 11 or later is supported.
|Package Manager||Helm 3.2.3|
nginx-ingress-controller is installed by default in the ingress-nginx namespace. Review the following parameter value requirements in the nginx-configuration configmap in the ingress-nginx namespace:
You can use the following command to view the parameters in the nginx-configuration configmap:
|Container Host operating system|
BMC Helix IT Operations Management has no specific dependencies on the underlying Linux OS or release running on your Worker Nodes.
You can use any x86_64 GNU/Linux OS supported by your Kubernetes or OpenShift platform and release version.
The following is required:
|Host OS Bash Shell||Bash Shell 4.2 or later|
|Persistent or Elastic Storage|
BMC supports a Bring-Your-Own-Storage-Class model, for any block storage supporting high performance IOPS.
CephRBD is certified by BMC.
For NFS storage, an NFS mount point is required. Perform the following steps:
For sizing information, see Sizing considerations.
F5 Load Balancer or other Load Balancer is supported.
The following load balancer SSL methods are supported:
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:
You can also add the X-Forwarded-for header for debugging purposes.
The following host names must be created with a DNS entry that points to the load balancer. 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.
DigiCert and R3 certificates.
Other CA signed certificates and self-signed certificates are not supported by default. If you want to use any other DigiCert CA, ensure that in the configs/infra.config file, the value of the
You can use a trusted CA SSL certificate (client root certificate) or a self-signed certificate while deploying the product. For instructions on using a self-signed or custom CA certificate, see Using self-signed or custom CA certificates.
If you are using a self-signed or custom CA certificate, perform the following steps:
BMC does not manage any repository other than Harbor and recommends that you use the local Harbor repository to pull the container image. However, if you are using any other repository, make sure that the repository is configured to connect to the BMC DTR to pull the container image.
A local repository provides the following benefits:
BMC Helix Platform uses the HorizontalPodAutoscaler (HPA) for its services so that the product can scale based on the customer usage. For the HPA to function, Kubernetes must expose metrics that are used to trigger scaling activities, for which a Metrics Server is required.
For information about the HPA, see .
For information about the Metrics Server, see .