[gRPC](1/N) gRPC-in-gRPC-out support for Generate non-streaming #2211
+2,825
−54
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind feature
What this PR does / why we need it:
Initial support for gRPC-in-gRPC-out non streaming Generate API.
Key changes:
pkg/epp/apifolderepp/handlers/server.goflow for gRPC-in-gRPC-out, key difference are:reqCtx.SchedulingRequestBodyI tested the whole flow is working by using custom GKE controller.
The following is an successful result using test go code here: https://github.com/zetxqx/gateway-api-inference-extension/blob/c311c6f3097ee3337ccbe39714d6f649a1c3cba0/pkg/epp/grpc/examples/client/main.go
Which issue(s) this PR fixes:
Fixes partially # #2166
Does this PR introduce a user-facing change?: