Effect of Kubernetes freezing Ingress API

[tpfau]

Given that the retirement of nginx ingress (Ingress https://kubernetes.io/blog/2025/11/11/ingress-nginx-retirement/), and kubernetes having essentially frozen the ingress API, I'm wondering, what effect this will have on the http-add-on, given that it needs an ingress. Would http-add-on work with the gateway API and/or what would need to change?

I'm just curious if there are any opinions on this and/or what the general feel of this is, since I somewhat fear that using the http-add-on might lead me into a dead end if clusters stop using ingress at some point.

[linkvt]

Hi @tpfau ,

there is no effect on the HTTP Add-on as we do not depend on any specific "ingress solution", whether it is an ingress controller, gateway API implementation or something else entirely.
The HTTP Add-on just needs to receive traffic from somewhere and will route it to a target on its own depending on the configured routing rules in the HTTPScaledObject (or its successor, see #1532 ).

This means you can use the setup that fits your needs (including Gateway API) as long as you configure it to send traffic for a specific host/path/header match to the HTTP Add-on (the interceptor to be precise) -

Hope that clears things up!