-
Notifications
You must be signed in to change notification settings - Fork 465
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
Adds EP-10494: AI APIs enhancement proposal #10495
base: main
Are you sure you want to change the base?
Adds EP-10494: AI APIs enhancement proposal #10495
Conversation
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.
This proposal LGTM
spec: | ||
ai: | ||
vertexAi: | ||
model: gemini-1.5-flash-001 |
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.
Should we mention what would happen if the URL or the request body contains the model value that's not the same as the model value in the Upstream?
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.
Yep, I'll add a sentence about if the model is not provided as well. We use the Upstream in the case of a mismatch, right?
3ab7979
to
b1fe48b
Compare
name: openai-secret | ||
``` | ||
|
||
Notice that this Upstream does not specify a model, so kgateway will use the model value in the request to determine |
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.
kgateway will use the model value in the request
What does this mean? Might be worth elaborating here.
filters: | ||
- type: ExtensionRef | ||
extensionRef: | ||
group: gateway.kgateway.dev/v1alpha1 | ||
kind: RoutePolicy | ||
name: open-ai-opt |
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.
Prefer using targetRef
attachment on the RoutePolicy
rather than ExtensionRef
?
The `pool` entries can either define a list of backends or a single backend. | ||
|
||
```yaml | ||
multi: |
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.
Does this live on the Upstream
? More context would be help IMO
Description
Adds Enhancement Proposal 10494 that proposes adding AI Gateway APIs support.
Supports #10494
Initial APIs can be found in this draft PR: #10493