Deploying and configuring the F5 NGINX Plus Ingress Controller

Before deploying  BMC Helix IT Operations Management (BMC Helix ITOM, you must deploy and configure an NGINX Plus Ingress Controller. The Ingress Controller serves as a reverse proxy and load balancer in Kubernetes. It works by implementing a Kubernetes Ingress, which is an API object that defines rules for routing external traffic to services within the Kubernetes cluster. 

Starting with BMC Helix ITOMversion 24.3, we support the F5 NGINX Plus Ingress Controller. You can use either the enterprise version (F5 NGINX Plus Ingress Controller) or the open-source version.
To learn more about the F5 NGINX Plus Ingress Controller, see the NGINX Ingress Controller.

Perform the instructions on this topic if:

  • You want to install BMC Helix ITOM version 24.3 and use the F5 NGINX Plus Ingress Controller.
  • You want to upgrade to BMC Helix ITOM version 24.3 and switch to the F5 NGINX Plus Ingress Controller.

Important

Skip this topic if you have already configured the NGINX Open Source Ingress Controller and do not want to use the F5 NGINX Plus Ingress Controller.

 

Before you begin

Make sure you have obtained the required licenses to install the F5 NGINX Plus Ingress Controller.

 

apiVersion: v1
data:
  allow-snippet-annotations: "true"
 annotations-risk-level: Critical (only applicable for Ingress version 1.12.1)
  client-max-body-size: 250m
  enable-underscores-in-headers: "true"
  error-log-level: debug
  proxy-buffers: "128 4k"
  redirect-to-https: "True"
  server-name-hash-bucket-size: "1024"
  ssl-redirect: "false"
  use-forwarded-headers: "true"
  worker-processes: "40"
 large-client-header-buffers: "4 64k"

 

 

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