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.
Kubernetes Ingress Nginx is retiring
21–30 of 178 posts
Re: Kubernetes Ingress Nginx is retiring
#22How 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 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 actual costs and reliability compared to traditional infrastructure, we only ever need to talk about the happy path/best case scenarios."
Re: Kubernetes Ingress Nginx is retiring
#23This 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.
Re: Kubernetes Ingress Nginx is retiring
#24How 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.
Re: Kubernetes Ingress Nginx is retiring
#25Traefik has an Nginx compatibility for annotations as well to make it easy to switch.
Re: Kubernetes Ingress Nginx is retiring
#26How 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 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…
Mhm! And Google just sit there laughing at everyone. Mission accomplished
Re: Kubernetes Ingress Nginx is retiring
#27Earlier quoted context omitted.
I've been using Envoy Gateway in my homelab and have found it to be good for my modest needs (single node k3s cluster running on an old PC). I needed to configure the underlying EnvoyProxy so that it would listen on specific IPs provided by MetalLB, and their docs were good enough to find my way through that. https://gateway.envoyproxy.io/
But envoy configs are unreadable abominations, why would you choose it? How did you even learn how to configure it? It's documentation is so confusing.
Envoy is designed with the intent that a machine is dynamically reconfiguring it at runtime. It is not designed to be configured directly by a human.
The tradeoff is that you can do truly zero downtime configuration changes. Granted, this is important to a very small number of companies, but if it's important to you, Envoy is great.
Re: Kubernetes Ingress Nginx is retiring
#28Why would you kill a thing that works so well, is so flexible, and does not have an equal yet? I do not understand.
There are no maintainers. It was maintained by one engineer for years, he stepped down, and F5 (who bought nginx) don't want to contribute since they have a competitor.
The project is still active even not pushing new big features.
Re: Kubernetes Ingress Nginx is retiring
#29This 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.
Re: Kubernetes Ingress Nginx is retiring
#30How 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 like devops. It means you get to get ahead of all the issues that you could potentially find in cybersecurity. Sure it's complicated, but at least you'll never be bored. I think the hardest part is that you always feel like you don't have enough time to do everything you need to.