Skip to main content
Question

IFS Cloud Remote - community Ingress NGINX controller (kubernetes/ingress-nginx) will retire in March 2026.

  • November 18, 2025
  • 4 replies
  • 72 views

Forum|alt.badge.img+7

The community Ingress NGINX controller (kubernetes/ingress-nginx) will retire in March 2026. After that:

  • No new releases
  • No bug fixes or security patches
  • Existing deployments will still run, but without support.

What is the impact on current deployments ? Will IFS change ?

4 replies

Aswin Shadhujan
Hero (Employee)
Forum|alt.badge.img+9

Hi ​@MCIPSTEV ,

IFS Rnd Team is aware of this issue, and they are working on the better approach/solution currently. Please create a Support Case so the request can be officially tracked, and you can receive regular updates on the progress and the final solution once it is available.

Thank you,

Aswin.


Forum|alt.badge.img+7
  • Author
  • Sidekick (Customer)
  • December 17, 2025

Hi ​@MCIPSTEV ,

IFS Rnd Team is aware of this issue, and they are working on the better approach/solution currently. Please create a Support Case so the request can be officially tracked, and you can receive regular updates on the progress and the final solution once it is available.

Thank you,

Aswin.

Hello I did open a support case and they said “we close the cas, ask the community” it is like nobody wants to deal with the issue.


Aswin Shadhujan
Hero (Employee)
Forum|alt.badge.img+9

Hi ​@MCIPSTEV ,

That must be a mistake from the Service Desk Team. Please create a new Support Case by referring my note. 

Thank you,

Aswin.


Forum|alt.badge.img+6
  • Sidekick (Customer)
  • December 18, 2025

@MCIPSTEV ​@Aswin Shadhujan 

 

Hi Nader,


We have further reviewed this concern with the relevant IFS R&D team.
Please find below the response from IFS R&D regarding this issue.

We acknowledge the upcoming retirement of the Ingress NGINX Controller, which is a core component of our current Kubernetes ingress architecture.

We are actively evaluating suitable long term alternatives that align with our performance, security, and maintainability requirements, while ensuring continuity of existing functionality.

Once a replacement approach has been finalized, we will communicate the proposed plan, timelines, and any required actions.

Our objective is to ensure a controlled and seamless transition with minimal impact to existing services, and we will provide the necessary guidance and support throughout the process.

We hope this clarifies the current situation regarding this issue.
An official announcement will be made once a replacement approach has been finalized.


Thanks and Best Regards,
Raveen.