-
Notifications
You must be signed in to change notification settings - Fork 555
Move HTTPRouteRule and GRPCRouteRule 'name' fields to Standard #3826
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
Move HTTPRouteRule and GRPCRouteRule 'name' fields to Standard #3826
Conversation
Skipping CI for Draft Pull Request. |
@guicassolato, should this be moved out of draft? |
Done, @kflynn. I wanted to get an idea if, at a glance, it looks good, but apparently ppl are already approving it. So I guess I got my answer 🙂 Thanks! |
/cc |
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.
looks good to me, thanks @guicassolato !
Can you also add two conformance tests in conformance/tests/mesh
? it should be very similar tests with just a few changes. you can take an example from the tests thats already in that folder.
I can add one, for HTTP. (Actually just pushed.) For GRPC, I could use some help, since we don't seem to have the tooling in place for mesh conformance. |
wdym tooling in place for mesh conformance? assuming you have istio installed, you can easily test your conformance test by running (from gateway-api root folder):
Let me know if you encounter any issues with it. |
/hold until featureNames are in at least |
I meant test helpers to make the GRPC requests, like we do for n/s. But if I'm wrong and you can give an example, I'd appreciate it and happy to add to the PR. |
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.
Thanks! Mind actually running the tests with the command I pasted above (for gateway and mesh) and see if it works?
I see what you mean. right, there isn't right now. Either add it or defer for later. I am fine having the PR without the grpc conformance for mesh + have an issue to backfill later. |
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.
Did you run the tests?
LGTM, but I'd like to see a review from @mlavacca as well. |
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.
/assign @mlavacca |
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.
Thanks for this PR, @guicassolato!
Signed-off-by: Guilherme Cassolato <guicassolato@gmail.com>
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.
/approve
I think the only thing to navigate is whether we want to actually mark it Standard
yet, or if we want some soak time for the new conformance tests. If we merge as-is that's fine, we just need to track getting some feedback on those tests before v1.4.0
releases.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: guicassolato, howardjohn, LiorLieberman, shaneutt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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
/unhold |
Apologies for the delay in getting back to this, but looks great where it ended up! Re #3826 (comment) I added a comment at #3566 (comment) about formalizing GRPCRoute support in mesh as potential scope for the v1.5 timeframe, and should be able to confirm shortly if we're passing these additional tests in Istio. |
That would be great, thank you @mikemorris. |
What type of PR is this?
/kind gep
/area conformance-test
What this PR does / why we need it:
Moves HTTPRouteRule and GRPCRouteRule
name
fields (GEP-995) to Standard.Which issue(s) this PR fixes:
Fixes #995
Does this PR introduce a user-facing change?: