This documentation supports an earlier version of BMC Helix IT Service Management on-premises deployment.To view the documentation for the latest version, select 23.3.04 from the Product version picker.

Preparing to install in an OpenShift cluster

If you are installing BMC Helix Service Management in an OpenShift cluster, perform the following steps on your Jenkins server before you begin the installation:

  • Make sure that you install Kubernetes Ingress controller.

    BMC Helix Platform supports only Ingress for application URLs.

  • Add the following security context constraints in your cluster to control permissions for pods:

    oc adm policy add-scc-to-user anyuid -n <BMC Helix Platform namespace> -z default
    oc adm policy add-scc-to-user privileged -n <BMC Helix Platform namespace> -z default

    These security context constraints are required to run the HELIX_INTEROPS_DEPLOY pipeline successfully during BMC Helix Service Management installation.

    Important

    Remove the security context constraints after the HELIX_INTEROPS_DEPLOY pipeline run is complete.

    Use the following commands to remove the security context constraints:

    oc adm policy remove-scc-from-user anyuid -n <BMC Helix Platform namespace> -z default

    oc adm policy remove-scc-from-user privileged -n <BMC Helix Platform namespace> -z default

  • For all the product components, make sure that you increase the number of threads to 4096 per node so that sufficient threads are available to the processes running in the containers.
    To increase the number of threads, perform the steps given in Unable to create more than 1024 Threads in OCP 4 in the Red Hat documentation.
    For more information, see Number of threads in the Elasticsearch documentation.


Where to go from here

Next task

Back to process

If you are finished installing BMC Helix Platform services, return to the appropriate installation or upgrade process:

 

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