3 ms·

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.

• Unroasted6154 1y 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 1y ago
    No they are going to forbid people to commit anything to the project so even security patch will be blocked.
    • jen20 1y ago
      The chance of this not having a fork keeping security updates running is effectively zero.
• pronik 1y ago
  To be fair, this is not the first time we'e heard about this, https://github.com/kubernetes/ingress-nginx/issues/13002 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 1y ago
    > InGate development never progressed far enough to create a mature replacement; it will also be retired
    • pronik 1y ago
      I stand corrected. Had a feeling it's dead when I looked into the GitHub repository a couple of weeks back.
• preisschild 1y 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.