Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Kubernetes Ingress Nginx is retiring

kubernetes.dev

Post reply on HN
Print view View original

31–40 of 178 posts

Re: Kubernetes Ingress Nginx is retiring

#31

Post by selfmodruntime »

solatic wrote: post #24
3ln00b wrote: post #19

How do you people even keep up with this? I'm going back to cybersecurity after trying DevOps for a year, it's not for me. I miss my sysadmin days, things were simple back then and worked. Maybe I'm just getting old and my cognitive abilities are declining. It seems to me that the current tech scene doesn't reward simple.

It's exactly why taking a trip through the ops/infra side is so important for people - you learn why LTS-style engineering is so important. You learn to pick technologies that are stable, reliable, well-supported by a large-enough people who are conservative in their approach, for anything foundational, because the alternative is migration pain again and again.

I also feel like we as an industry should steer towards a state of "doneness" for OSS solutions. As long as it works, it's fine to keep using technologies that are only sparsely maintained.

Re: Kubernetes Ingress Nginx is retiring

#34

Post by mt42or »

Unroasted6154 wrote: post #29
mt42or wrote: post #23

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.

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.

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

Re: Kubernetes Ingress Nginx is retiring

#35

Post by pronik »

mt42or wrote: post #23

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.

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.

Re: Kubernetes Ingress Nginx is retiring

#36

Post by makeitdouble »

3ln00b wrote: post #19

How do you people even keep up with this? I'm going back to cybersecurity after trying DevOps for a year, it's not for me. I miss my sysadmin days, things were simple back then and worked. Maybe I'm just getting old and my cognitive abilities are declining. It seems to me that the current tech scene doesn't reward simple.

> things were simple back then

If you were working in the orgs targeted by k8s, I think it was generally more of a mess. Think about managing a park of 100~200 servers with home made bash scripts and crappy monitoring tools and a modicum of dashboards.

Now, k8s has engulfed a lot more than the primary target, but smaller shops go for it because they'r also hoping to hit it big someday I guess. Otherwise, there will be far easier solutions at lower scale.

Re: Kubernetes Ingress Nginx is retiring

#37

Post by figassis »

This is terrible. Of all things k8s, ingress was the part I just did not want to have to mess with. It just worked and was stable, this gateway is completely unnecessary. And it seems to me that nginx retiring is just because people were pushing for the gateway so much that they threw in the towel. Infra is not react, people need to leave it alone.

Re: Kubernetes Ingress Nginx is retiring

#38

Post by merb »

3ln00b wrote: post #19

How do you people even keep up with this? I'm going back to cybersecurity after trying DevOps for a year, it's not for me. I miss my sysadmin days, things were simple back then and worked. Maybe I'm just getting old and my cognitive abilities are declining. It seems to me that the current tech scene doesn't reward simple.

ingress-nginx is older than 5-7 years tough. In that time frame you would’ve needed to update your Linux system, which gets hairy most often as well. The sad thing is just that the replacement is just not there and gateway api has a lot of drawbacks that might get fixed in the next release (working with cert manager)

Re: Kubernetes Ingress Nginx is retiring

#39

Post by cmckn »

3ln00b wrote: post #19

How do you people even keep up with this? I'm going back to cybersecurity after trying DevOps for a year, it's not for me. I miss my sysadmin days, things were simple back then and worked. Maybe I'm just getting old and my cognitive abilities are declining. It seems to me that the current tech scene doesn't reward simple.

The Ingress API has been on ice for like 5 years. The core Kubernetes API doesn't change that much, at least these days. There's an infinite number of (questionable) add-ons you can deploy in your cluster, and I think that's mostly where folks get stuck in the mud.

Re: Kubernetes Ingress Nginx is retiring

#40

Post by nielsole »

pronik wrote: post #35
mt42or wrote: post #23

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.

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 releas…

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