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

11–20 of 178 posts

Re: Kubernetes Ingress Nginx is retiring

#12

Post by [deleted] »

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?

[deleted]

Re: Kubernetes Ingress Nginx is retiring

#13

Post by stackskipton »

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?

It doesn't but Kubernetes team was kind of like "Hey, while you are switching, maybe switch away from Ingress API?"

Re: Kubernetes Ingress Nginx is retiring

#14

Post by imcritic »

seabombs wrote: post #6
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.

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.

Re: Kubernetes Ingress Nginx is retiring

#16

Post by eddythompson80 »

imcritic wrote: post #14
seabombs wrote: post #6

Earlier 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.

You don't. Envoy is great if you programmatically configure it, or if you have very small and simple configs. It can't be maintained by a human. But if you have tools that generate it programmatically based on other config, you can read through it.

Re: Kubernetes Ingress Nginx is retiring

#17

Post by mzaccari »

seabombs wrote: post #6
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.

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/

^ I second Envoy Gateway! It has support for HTTPRoute like all the others, but also TCPRoute, UDPRoute, TLSRoute, GRPCRoute backed by Envoy and they have worked great for me on EKS clusters I manage for work. The migration from Ingress API to Gateway API hasn’t been bad, as you can have both running side-by-side (just not using the same LB) and the EnvoyPatchPolicy has been great for making advanced changes for things not covered by the manifests

Re: Kubernetes Ingress Nginx is retiring

#19

Post by 3ln00b »

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.
Post reply on HN