-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Generate error page warnings for gRPC upstreams #2196
Conversation
Lots of tests, great stuff |
4c60a0a
to
18a28c4
Compare
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.
Hi @ciarams87 Please see my comments and suggestions
349e8ff
to
f744cb1
Compare
293df52
to
470f1d2
Compare
d6855db
to
9651ca0
Compare
9651ca0
to
c55cdf6
Compare
c55cdf6
to
01b0ef5
Compare
@pleshakov Can you please re-review when you get a chance? Thank you! |
190b3d9
to
0e6cc68
Compare
a3c15fd
to
974015c
Compare
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.
Hi @ciarams87 This looks good! Just a few comments
0d9e003
to
bf0f3a7
Compare
bf0f3a7
to
b2b0f1b
Compare
Proposed changes
Generate an error when a user configures one or more gRPC Upstreams in the VirtualServer resource with a custom error page which conflicts with the ones generated for a gRPC upstream (one of 400, 401, 403, 404, 405, 408, 413, 414, 415, 426, 429, 495, 496, 497, 500, 501, 502, 503, 504)
Checklist
Before creating a PR, run through this checklist and mark each as complete.