Skip to Content

Statement of direction: End of support for Kubernetes NGINX Ingress controller

The retirement of the Kubernetes NGINX Ingress controller in March 2026 impacts your BMC Helix IT Operations Management on-premises environments that currently rely on Kubernetes NGINX Ingress controller. For more details on the Kubernetes announcement, see Kubernetes official retirement notice.

In our earlier communication, we outlined plans to transition to the F5 Community NGINX Ingress controller starting with BMC Helix IT Operations Management 26.1.00 timeframe. However, during final validation, we identified technical issues that prevent completion of certification in time for this release. As a result, you should continue using the existing Kubernetes NGINX Ingress Controller at this time.

Information
Important

While every effort is made to provide accurate, forward-looking guidance on product direction to assist you with your buying and planning decisions, BMC Helix cannot guarantee that intentions stated as follows are final and binding. 

Statement of direction

For the time being, we recommend you to remain on the Kubernetes NGINX Ingress Controller but use the Chainguard‑maintained images, which extend maintenance and security updates for the existing retired controller. For information about Kubernetes NGINX Ingress Controller with Chainguard, see Keeping ingress-nginx alive in Chainguard documentation.

Transition period

BMC Helix will use the following options:

  • BMC Helix will test and certify Kubernetes NGINX Ingress Controller with Chainguard maintained images.
  • BMC Helix will continue to test the F5 NGINX Plus with BMC Helix IT Operations Management.

Forward looking approach

BMC Helix remains committed to providing a long‑term, fully supported alternative Ingress controller solution.

Once finalized and fully certified, we will publish migration guidance outlining the recommended replacement controller and upgrade steps.

If you prefer a fully supported commercial option today, F5 NGINX Plus is already supported in Helix and provides an enterprise‑grade, fully supported ingress controller.

Summary

Until a new certified ingress controller alternative is delivered, you should:

  1. Stay on the existing Kubernetes NGINX Ingress Controller.
  2. Adopt Chainguard‑maintained images for continued security coverage.
  3. Plan for a future transition following our upcoming certified migration guidance, or choose F5 NGINX Plus, which is already supported and fully backed by F5.

Frequently asked questions

What is the Kubernetes NGINX Ingress controller retirement date?

Kubernetes NGINX Ingress controller retirement date is March 2026.
See Kubernetes official retirement notice.

My company is using Kubernetes NGINX Ingress controller with BMC Helix IT Operations Management earlier than 24.3.00. What should I do?

BMC Helix recommends you to perform the following actions before March 2026:

  • Upgrade to BMC Helix IT Operations Management 24.3.00  or later.
  • Transition Ingress configuration to F5 NGINX Plus or Kubernetes NGINX Ingress Controller with Chainguard maintained images.
Will my existing BMC Helix IT Operations Management environment that uses NGINX Ingress controller stop working?

No. Existing on-premises deployments of BMC Helix IT Operations Management will continue to work after reaching the Ingress controller retirement date, and you can continue using such deployed instances. However, it would not be fixed for security vulnerabilities.

Should we keep our BMC Helix IT Operations Management environment with NGINX Ingress controller implementation going?

BMC Helix strongly recommends that you start using the Chainguard Nginx images or transition to F5 NGINX Plus starting in March 2026.

 

 

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

BMC Helix IT Operations Management deployment 25.4