Ingress Nginx goes EOL in March 2026

[pearj]

Ingress Nginx is going EOL in March 2026. What are Ping's plans to respond to this?

[pearj]

@lee-baines thoughts?

[lee-baines]

Hi @pearj. Thanks for highlighting this. I was unaware of Ingress Nginx going EOL. I've created a story to switch out the current Ingress Nginx to an alternative. It will be available in our next maintenance release, hopefully by the end of the year

[pearj]

Thanks @lee-baines, would it likely stay with the Ingress API? Or would you switch to the Kubernetes Gateway API instead? Or as well as?

[lee-baines]

We will stay on the Ingress API for now. The most important consideration for us is to maintain consistency and stability within forgeops. But I will create a spike for the Gateway API to see whether it is something we could offer as an additional option within Helm in the future.

[pearj]

Hi @lee-baines have you picked the Ingress Nginx replacement? It would be good to know asap so we can begin our own preparation.

Would the spike for the Gateway API complete before before Ingress Nginx goes EOL? Or is it more of a future thing that will be looked into separately that won't be offered as an alternative to the Ingress API as part of this EOL?

At present we're leaning towards haproxy simply because it's already on the Forgeops supported list.

[lee-baines]

Hi @pearj. We're looking at https://github.com/nginx/kubernetes-ingress which seems the obvious replacement. We have used this previously so unless there any major issues, this will probably be what we replace ingress-nginx with.

Gateway API is purely a future thing. From a vanilla forgeops, we try to keep everything agnostic and simple so we try not to add too much support for additional 3rd party tooling unless there is a big ask for it across multiple customers and it benefits the default deployment.

HA Proxy is an option. You can select it via the forgeops tool

[pearj]

Thanks @lee-baines, that’s helpful.