-
Notifications
You must be signed in to change notification settings - Fork 677
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Httpproxy not supporting queryParameter match condition #5549
Comments
Hey @nageshs28! Thanks for opening your first issue. We appreciate your contribution and welcome you to our community! We are glad to have you here and to have your input on Contour. You can also join us on our mailing list and in our channel in the Kubernetes Slack Workspace |
@relu Can you please help here |
@nageshs28 are you sure you updated the CRDs? Make sure the |
Yep this sounds like an out of date CRD issue, query param match is available in Contour 1.25 (see https://github.com/projectcontour/contour/blob/v1.25.0/apis/projectcontour/v1/httpproxy.go#L81 and https://github.com/projectcontour/contour/blob/v1.25.0/examples/contour/01-crds.yaml#L4551-L4553) |
Thanks folks, it was issue with outdated crd only. |
What steps did you take and what happened:
Upgraded contour to 1.25
Update httpproxy routes to add querycondition
Error - strict decoding error: unknown field "spec.routes[0].conditions[0].queryParameter
What did you expect to happen:
Httpproxy should be applied and show valid, envoy should honour during routing
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
): 1.26/etc/os-release
): ubuntu 22 ltsThe text was updated successfully, but these errors were encountered: