-
Notifications
You must be signed in to change notification settings - Fork 527
Return 500 responses for invalid backends #443
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
Return 500 responses for invalid backends #443
Conversation
Codecov Report
@@ Coverage Diff @@
## main #443 +/- ##
==========================================
+ Coverage 60.08% 62.09% +2.00%
==========================================
Files 40 40
Lines 4347 4406 +59
==========================================
+ Hits 2612 2736 +124
+ Misses 1583 1525 -58
+ Partials 152 145 -7
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
internal/gatewayapi/testdata/httproute-with-some-invalid-backend-refs-no-service.out.yaml
Outdated
Show resolved
Hide resolved
can you also add the appropriate conformance test to
|
|
Signed-off-by: AliceProxy <alicewasko@datawire.io>
Signed-off-by: AliceProxy <alicewasko@datawire.io>
Signed-off-by: AliceProxy <alicewasko@datawire.io>
Signed-off-by: AliceProxy <alicewasko@datawire.io>
Signed-off-by: AliceProxy <alicewasko@datawire.io>
That all I needed to do? Looks like they ran and passed. I checked the logs to confirm they really ran.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for adding this tricky feature !
Thanks for the many reviews after all my changes 😅 |
When a HTTPRoute has invalid backends we need to return 500 responses for gateway API conformance. If there are no valid backends at all then a direct response is issued with status 500, if there is a mix of valid and invalid backends then a weighted cluster is used.
resolves #162