You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When using the URLRewrite filter in NGINX Gateway Fabric version 1.1.0, even after configuring it according to the documentation and the commit here, an error occurs: "All rules are invalid: [spec.rules[0].filters[0].type: Unsupported value: "URLRewrite": supported values: "RequestRedirect", "RequestHeaderModifier", spec.rules[1].filters[0].type: Unsupported value: "URLRewrite": supported values: "RequestRedirect", "RequestHeaderModifier"]".
To Reproduce
Steps to reproduce the behavior:
Deploy NGINX Gateway Fabric version 1.1.0 to a Kubernetes Bare Metal cluster.
Configure an HTTPRoute with the URLRewrite filter as described in the provided example route.
Apply the configuration and observe the error.
Expected behavior
The URLRewrite filter should be supported and function as expected without throwing errors.
Your environment
Version of the NGINX Gateway Fabric: 1.1.0
Version of Kubernetes: v1.29.2
Kubernetes platform: Bare Metal
Details on how NGINX Gateway Fabric Pod is exposed: LoadBalancer
Logs of NGINX container:
Describe the bug
When using the URLRewrite filter in NGINX Gateway Fabric version 1.1.0, even after configuring it according to the documentation and the commit here, an error occurs: "All rules are invalid: [spec.rules[0].filters[0].type: Unsupported value: "URLRewrite": supported values: "RequestRedirect", "RequestHeaderModifier", spec.rules[1].filters[0].type: Unsupported value: "URLRewrite": supported values: "RequestRedirect", "RequestHeaderModifier"]".
To Reproduce
Steps to reproduce the behavior:
Deploy NGINX Gateway Fabric version 1.1.0 to a Kubernetes Bare Metal cluster.
Configure an HTTPRoute with the URLRewrite filter as described in the provided example route.
Apply the configuration and observe the error.
Expected behavior
The URLRewrite filter should be supported and function as expected without throwing errors.
Your environment
Version of the NGINX Gateway Fabric: 1.1.0
Version of Kubernetes: v1.29.2
Kubernetes platform: Bare Metal
Details on how NGINX Gateway Fabric Pod is exposed: LoadBalancer
Logs of NGINX container:
Additional context
The text was updated successfully, but these errors were encountered: