Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Gateway API: unsupported filters should be reflected in route status #1071

Open
kenjenkins opened this issue Nov 14, 2024 · 0 comments
Open

Gateway API: unsupported filters should be reflected in route status #1071

kenjenkins opened this issue Nov 14, 2024 · 0 comments

Comments

@kenjenkins
Copy link
Contributor

If a route contains a filter with a type that is not supported, this should be reflected in the "Accepted" status condition:

Unknown values here must result in the implementation setting the Accepted Condition for the Route to status: False, with a Reason of UnsupportedValue.

(reference)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kenjenkins