Skip to Content

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

The changes mentioned in this Statement of direction apply to the on-premises deployment of BMC Helix Intelligent Integrations 26.1.00 and later versions.

Kubernetes has announced the retirement of the NGINX Ingress Controller in March 2026. This change impacts your BMC Helix Intelligent Integrations on‑premises environments if you currently use the Kubernetes NGINX Ingress Controller.

For more information about the Kubernetes announcement, see Kubernetes official retirement notice.

Warning
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

As an interim solution, BMC Helix recommends updating the Kubernetes NGINX Ingress Controller to use the Chainguard‑maintained container images instead of the standard upstream container images.

BMC Helix has tested and validated the use of Chainguard-maintained images with BMC Helix Intelligent Integrations. Chainguard-maintained images are secure, FIPS-capable, and compatible with your existing NGINX Ingress Controller and Helm charts. Therefore, your existing deployments and manifests require minimal changes.

All required images are available in the BMC Helix Docker Trusted Registry (docker.io) along with other BMC Helix deployment images. To start using the new Chainguard-maintained images, you must migrate your existing images to Chainguard-maintained images. For information about the migration steps, see Migrating NGINX Ingress Controller container images to Chainguard-maintained container images.

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.

Will my existing BMC Helix Intelligent Integrations environment that uses NGINX Ingress Controller stop working?

No. Existing on-premises deployments of BMC Helix Intelligent Integrations 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 Intelligent Integrations environments with NGINX Ingress Controller implementation going?

BMC Helix strongly recommends that you start using the Chainguard-maintained images starting in March 2026.

 

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

BMC Helix Intelligent Integrations 26.2