Conversation
Signed-off-by: Sathvik <Sathvik.S@ibm.com>
|
|
||
| **Key Generation & Deployment Flow**: | ||
| ``` | ||
| 1. Generate Keys (if authEnabled=true and keys empty) |
There was a problem hiding this comment.
can we expect the user to supply the key manually if not just just don't set? and store the key in the secret so that we can use that wherever required!
There was a problem hiding this comment.
If my understanding is right, are you suggesting,
We keep auth disabled by default and if the user provides the key, we use that key, else keep auth disabled?
There was a problem hiding this comment.
yes, that is what I'm thinking.. or can we even have a default password! I'm just trying to avoid any extra logic required for generating anything(this will become application/service specific logic which I want to avoid), let me know if you any different approach.
There was a problem hiding this comment.
I think its not a good practice to keep authN disabled by default. We can have some default vllm auth keys for each vllm service.
| authEnabled: true # Default: true (authentication enabled) | ||
|
|
||
| instruct: | ||
| apiKey: "" # Auto-generated if authEnabled=true and empty |
There was a problem hiding this comment.
Can we keep these keys in base64 encoded format just to avoid storing the keys in plain text?
3 participants
AISERVICES-913