-
Notifications
You must be signed in to change notification settings - Fork 283
feat(api): Add appProtocol to InferencePool API for gRPC support #2162
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
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
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.
why define it in TargetPort if all ports must share the same protocol? why not define it directly here?
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.
Good call, listing the pros and cons below. I feel add a single appProtocol in InferenceSpec is better. So I changed accordingly. PTAL
Option 1. the original change: add appProtocol to Port and create a separate Port for EndPointPicker.
Pros:
Cons:
Option 2. new solution(the comment here), add appProtocol in parallel with targetPorts.
Pros:
Cons: