Ingress NGINX Retirement

[swapsCAPS]

Hi all,

I was wondering which direction Strimzi is going after the announced Ingress NGINX Retirement and if there are users having strong preferences etc.

[ppatierno]

There is not a clear plan yet, but we have an open issue for that #12140 where the discussion will likely take place.

[scholzj]

Please keep in mind that Strimzi does not include Nginx Ingress itself in any way. We only provide an API and some orchestration code to make it easier for our users to use it. So Strimzi itself is not directly exposed to any CVEs or bugs that might be left unresolved due to Ingress Nginx retirement. So for Strimzi itself, it is mostly about whether the APIs and code used to manage the Ingress resources still makes sense with other Ingress controllers, and when/how should we remove it.

The users really have to decide on their own what to do about their Nginx Ingress installations. One can use NodePorts or Loadbalancers. But Strimzi today is pretty flexible, so one can also use other Ingress controllers or Gateway API if needed.

Apart from the issue linked by Paolo, there are also few discussions on Slack about this in the #strimzi and @strimzi-dev channels on CNCF Slack. But I do not think will tell you anything new.