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

81–90 of 178 posts

Re: Kubernetes Ingress Nginx is retiring

#81

Post by PhilippGille »

andix wrote: post #4

Does anyone know good resources on how to migrate and which gateway controllers are suitable replacements? Ingresses with custom nginx attributes might be tricky to migrate.

Literally the second link in the article is "migrating to API Gateway" and points to https://gateway-api.sigs.k8s.io/guides/

Which has this section about migration: https://gateway-api.sigs.k8s.io/guides/migrating-from-ingres...

And this list of Gateway controllers: https://gateway-api.sigs.k8s.io/implementations/

Re: Kubernetes Ingress Nginx is retiring

#83

Post by Hikikomori »

mrweasel wrote: post #74
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…

You can manage and reason about ~2000+ servers without Kubernetes, even with a relatively small team, say about 100 - 150, depending on what kind of business you're in. I'd recommend either Puppet, Ansible (with AWX) and/or Ubuntu Landscape (assuming that your in the Ubuntu ecosystem). Kubernetes is for rather special case environments. I am coming around to the idea of using Kubernetes more, but I still think that i…

Meanwhile we manage over 1200 instances with multiple kubernetes clusters with a team of 10, including complex mesh networking and everything else the team does. It might be complex but it also gives you so much for free that you don't have to deal with.

Re: Kubernetes Ingress Nginx is retiring

#84

Post by friendzis »

toredash wrote: post #75
solatic wrote: post #24

Earlier quoted context omitted.

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 often find myself trying to tell people that KISS is a good thing. If something is somewhat complex it will be really complex after a few years and a few rotations of personnel.

Quite often the tradeoff is not between complexity (to cover a bunch of different cases) and simplicity (do one thing simply), but rather where that complexity lies. Do you have dependency fanout? It probably makes sense to shove all that complexity into the central component and manage it centrally. Otherwise it probably makes sense to make all the components a bit more complex than they could be, but still manageable.

Re: Kubernetes Ingress Nginx is retiring

#85

Post by jitl »

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.

i prefer current era where i never have to ssh to debug a node. if a node is misbehaving or even needs a patch i destroy it. one command, works every time.

Re: Kubernetes Ingress Nginx is retiring

#86

Post by bostik »

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…

To quote an ex coworker: all configuration management systems are broken, in equal measure - just in different fashion. They are all trying to shoehorn fundamentally brittle, complex and often mutually exclusive goals behind a single facade.

If you are in the position to pick a config management system, the best you can do is to chart out your current and known upcoming use cases. Then choose the tool that sucks the least for your particular needs.

And three years down the line, pray that you made the right choice.

Yes, kube is hideously complex. Yes, it comes with enormous selection of footguns. But what it does do well, is to allow decoupling host behaviour from service/container behaviour more than 98% of the time. Combined with immutable infrastructure, it is possible to isolate host configuration management to the image pre-bake stage. Leave just the absolute minimum of post-launch config to the boot/provisioning logic, and you have at least a hope of running something solid.

Distributed systems are inherently complex. And the fundamental truth is that inherent complexity can never be eliminated, only moved around.

Re: Kubernetes Ingress Nginx is retiring

#87

Post by throwaway838112 »

wg0 wrote: post #69

Kubernetes is never maturing. It keeps moving. An installation just a year ago would have things that would require significant planning to upgrade. What is missing is an open source orchestrator that has a feature freeze and isn't Nomad or docker swarm.

hear hear!

Re: Kubernetes Ingress Nginx is retiring

#88

Post by steve1977 »

dangus wrote: post #41
gryfft wrote: post #22

Earlier quoted context omitted.

> It seems to me that the current tech scene doesn't reward simple. A deal with the devil was made. The C suite gets to tell a story that k8s practices let you suck every penny out of the compute you already paid for. Modern devs get to do constant busy work adding complexity everywhere, creating job security and opportunities to use fun new toys. "Here's how we're using AI to right size our pods! Never mind the actu…

This just seems like sensationalist nonsense spoken by someone who hasn’t done a second of Ops work. Kubernetes is incredibly reliable compared to traditional infrastructure. It eliminates a ton of the configuration management dependency hellscape and inconsistent application deployments that traditional infrastructure entails. Immutable containers provide a major benefit to development velocity and deployment reliab…

The problem is that some Kubernetes features would have a positive impact on development velocity in theory, however in my experience (25 years of ops and devops), the cost of keeping up often eats up those benefits and often results in a net-negative.

This is not always a problem of Kubernetes itself though, but of teams always chasing after the latest shiny thing.

Re: Kubernetes Ingress Nginx is retiring

#89

Post by p_l »

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.

We also now have multiple full featured Ingress implementations that work better than the old nginx-ingress

Re: Kubernetes Ingress Nginx is retiring

#90

Post by cess11 »

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…

I've managed a couple of hundred virtual servers on vCenter with Ansible. It was fine. Syslog is your friend.
Post reply on HN