-
Notifications
You must be signed in to change notification settings - Fork 182
Add BBR docs, example deployment #1498
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
Conversation
Welcome @srampal! |
Hi @srampal. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
✅ Deploy Preview for gateway-api-inference-extension ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
/ok-to-test Thanks for starting this, any planned progress on it? |
Yes, I am working on it based on the v1.0.0 release that just came out. There are already some doc updates on BBR added and I will add some more in the next few days. |
ef93eea
to
14b4788
Compare
@ahg-g @kfswain this is ready for review now. I could add some more (such as using BBR to directly route to a standalone LLM service as the BackendRef instead of to an InferencePool/EPP) but maybe those and other potential scenarios could be added in a followup PR to let this one get merged for now. cc @keithmattix @davidbreitgand |
f1a34ab
to
d878235
Compare
/lgtm Thanks! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahg-g, srampal 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 |
/lgtm |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes ##711
Does this PR introduce a user-facing change?: