top | item 45924055

(no title)

mt42or | 3 months ago

This is required steps but the timing plan is bad. Looks like a google product closing. Let people time to move out, 6 month is not enough.

discuss

order

pronik|3 months ago

To be fair, this is not the first time we'e heard about this, https://github.com/kubernetes/ingress-nginx/issues/13002 exists since March. However I also thought that the timeline to a complete project halt would be much longer considering the prevalence of the nginx ingress controller. Might also mean that InGate is dead, since it's not mentioned in this post and doesn't seem to be close to any kind of stable release.

nielsole|3 months ago

> InGate development never progressed far enough to create a mature replacement; it will also be retired

Unroasted6154|3 months ago

It's not a service shutting down though. It will still work fine for a while and it there is a critical security patch required, the community might still be able to add it.

mt42or|3 months ago

No they are going to forbid people to commit anything to the project so even security patch will be blocked.

preisschild|3 months ago

> Let people time to move out, 6 month is not enough.

Did you actually contribute? Either by donations or code? If not, Beggars can't be choosers. You are not entitled to free maintainence for open source software you use.