Skip to content

Conversation

@nlamirault
Copy link
Contributor

generate multiple ModelConfig resources (one per provider) instead of just one for the default provider.

generate **multiple ModelConfig resources** (one per provider) instead of just one for the default provider.

Signed-off-by: Nicolas Lamirault <nicolas.lamirault@gmail.com>
Signed-off-by: Nicolas Lamirault <nicolas.lamirault@gmail.com>
Copy link
Contributor

@EItanya EItanya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a very interesting idea I like it! I will try and get to a deeper review ASAP but it may be after KubeCon as there is A LOT happening the next few work days.

@dimetron
Copy link
Contributor

maybe we should add range over additional models of the same provider ?
It's less common to use many provider types, but use model types like (default, thinking, fast) which will be translated into additional model names under the same provider. WDYT ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants