#Kubernetes Gateway API: a sobering look
My biggest pain with ingresses are regex redirects.
So many of us relied on the notorious #nginx annotations or even deployed separate nginx instances for more complex redirects.
With #GatewayAPI we have HttpRoutes with RequestRedirect filters but they don't have a path type regex.
How to migrate nginx annotations?
The go-to solutions seem proprietary CRDs like #traefik middleware.
So, no Gateway API, then?
Please tell me that I'm missing something!
I've read the docs and understood that regexes are "not quite as broadly supported".
https://gateway-api.sigs.k8s.io/geps/gep-726/#future-extension
And I know there is much more to GW API and by no means want to belittle the efforts many people have put into it. It is just so frustrating to have a controller that is perfectly capable of doing regex redirects but not being able to use it because of abstraction.
@schnatterer yeah this is weird. I just skimmed over the docs because my team plans using route filtering.
Anyhow, I figure the Gateway-API team probably postpones the regexp filter mechanic because more complex replacments might end up terribly bad.
I do hope they figure out what they want to achive, otherwise the community ends up with sub-par filter mechanisms if API team fumbles that one.
Johannes Schnatterer
Pxl Phile