Repository navigation
Fully working fix and flow for ai gateway - #71
Merged
Merged
Conversation
Signed-off-by: Sergey Pronin <sp@solanica.io>
Signed-off-by: Sergey Pronin <sp@solanica.io>
Signed-off-by: Sergey Pronin <sp@solanica.io>
Signed-off-by: Sergey Pronin <sp@solanica.io>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Creating the model as a service with AI gateway.
Full description is in docs/proposals/ai-gateway-api-keys.md
This is the flow to support single domain, various models, where each model has its own key.
Later on this can be extended to having a user with various keys and accesses to models.
We might need to create some plugin or deployer that is going to automate the routine of deploying cert-manager, APIGateway CRDs, Envoy proxy, etc.