Open zsedem opened 2 months ago
Hey @zsedem, thanks for the report. The short answer is: yes, this is an unexpected implicit limitation - we cannot create multiple instances of request-transformer
Plugin associated with a single Kong Route.
I agree it's a bug and we should solve it either by:
request-transformer
configuration by merging the configuration generated by filters and the config provided by a user in a plugin (perhaps making the user's config higher priority in case of an overlap).I'm adding this issue preliminary to 3.4 milestone and we will discuss how this should be fixed.
For the time being, a reasonable workaround is creating a custom plugin, which does the request transformation.
Is there an existing issue for this?
Current Behavior
Adding plugin with request-transformer type to an HTTPRoute with Rewrite will make one of the rules not take effect. Either
Expected Behavior
Have the route both the additional header applied to it and the urlrewrite rule
Steps To Reproduce
Kong Ingress Controller version
Kubernetes version
Anything else?
In the proposed solution for the support of UrlRewrite here: https://github.com/Kong/kubernetes-ingress-controller/issues/5853 They mention using a Kong request-transformer plugin, is it possible that because of this, we cannot use
UrlRewrite
and request-transformer plugin together?