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

51–60 of 178 posts

Re: Kubernetes Ingress Nginx is retiring

#51

Post by nunez »

SlavikCA wrote: post #7

Reading few blogs and forums about it today - people talking about switching to Gateway API (from "legacy" Ingress). And I do not understand it: 1. Ingress still works, it's not deprecated. 2. There a lot of controllers, which supports both: Gateway API and Ingress (for example Traefik) So, how Ingress Nginx retiring related / affects switch to Gateway API?

1) ingress still works but is on the path to deprecation. It's a super popular API, so this process will take a lot of time. That's why service meshes have been moving to Gateway API. Retiring ingress-nginx, the most popular ingress controller, is a very loud warning shot.

2) see (1).

Re: Kubernetes Ingress Nginx is retiring

#52

Post by nunez »

MrDarcy wrote: post #21
seized wrote: post #20

It's in beta, but HAProxy has a gateway product: https://www.haproxy.com/blog/announcing-haproxy-unified-gate...

Love haproxy but if we’re shilling projects istio is superior. Multi cluster, hbone, ambient.

Lots more moving pieces though

Re: Kubernetes Ingress Nginx is retiring

#53

Post by dangus »

makeitdouble wrote: post #36
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 b…

Even after the bash script era, I don’t think the configuration management landscape gets enough discredit for how bad it is. I never felt like it stopped feeling hacked together and unreliable.

E.g., Chef Software, especially after its acquisition, is just a dumpster fire of weird anti-patterns and seemingly incomplete, buggy implementations.

Ansible is more of the gold standard but I actually moved to Chef to gain a little more capability. But now I hate both of them.

When I just threw this all in the trash in my HomeLab and went to containerization it was a major breath of fresh air and resulted in getting a lot of time back.

For organizations, of the best parts about Kubernetes is that it’s so agnostic so that you can drop in replacements with a level of ease that is just about unheard of in the Ops world.

If you are a small shop you can just start with something simpler and more manageable like k3s or Talos Linux and basically get all the benefits without the full blown k8s management burden.

Would it be simpler to use plain Docker, Docker Swarm, Portainer, something like that? Yeah, but the amount of effort saved versus your ability to adapt in the future seems to favor just choosing Kubernetes as a default option.

Re: Kubernetes Ingress Nginx is retiring

#54

Post by [deleted] »

sph wrote: post #44
cmckn wrote: post #39

Earlier quoted context omitted.

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.

> doesn’t change that much Yet they are retiring a core Ingress that has been around for almost as long as Kubernetes has.

[deleted]

Re: Kubernetes Ingress Nginx is retiring

#55

Post by jen20 »

mt42or wrote: post #34
Unroasted6154 wrote: post #29

Earlier quoted context omitted.

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.

The chance of this not having a fork keeping security updates running is effectively zero.

Re: Kubernetes Ingress Nginx is retiring

#56

Post by withinboredom »

bennysaurus wrote: post #32
all_usernames wrote: post #5

What's the security back-story here?

Only a single maintainer for years, and it's fallen now to best-effort.

I (and others) have offered to create a PR for issues opened — just point us in the right direction we asked. The maintainer always came back with “I fixed it for you”.

The maintainer had plenty of people who wanted to help, but never spent the time to teach them.

Re: Kubernetes Ingress Nginx is retiring

#57

Post by [deleted] »

cesnja wrote: post #49
cmckn wrote: post #39

Earlier quoted context omitted.

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.

But the Gateway API has only been generally available for two years now. And the last time I checked, most managed K8S solutions recommend the Ingress API while Gateway support is still experimental.

[deleted]

Re: Kubernetes Ingress Nginx is retiring

#58

Post by jackhalford »

I don’t think this is the https://xkcd.com/2347/ of the ops world? People will usually use the ingress controller of their cloud provider. I’ve been using the tailscale ingresses for tailscale funnel. But the transition from ingress to gateway api is seeming to take forever so I’m just running a caddy pod with a static config until the dust settles.

Re: Kubernetes Ingress Nginx is retiring

#59

Post by [deleted] »

dangus wrote: post #53
makeitdouble wrote: post #36

Earlier quoted context omitted.

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

Even after the bash script era, I don’t think the configuration management landscape gets enough discredit for how bad it is. I never felt like it stopped feeling hacked together and unreliable. E.g., Chef Software, especially after its acquisition, is just a dumpster fire of weird anti-patterns and seemingly incomplete, buggy implementations. Ansible is more of the gold standard but I actually moved to Chef to gain…

[deleted]

Re: Kubernetes Ingress Nginx is retiring

#60

Post by [deleted] »

sph wrote: post #44
cmckn wrote: post #39

Earlier quoted context omitted.

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.

> doesn’t change that much Yet they are retiring a core Ingress that has been around for almost as long as Kubernetes has.

[deleted]
Post reply on HN