-
Notifications
You must be signed in to change notification settings - Fork 0
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
Feature Request | Operator | Allow operator-wandb to accept license as a string or as a secretKeyRef #18
Comments
Vijay to retest as per the conversation in the meeting with Eng. |
@vijay-wandb - Were you able to retest? |
I used the correct format like this in values.yaml, but it doesn't appear to work
I think, secret references are not being properly defined in the Helm chart It may be have to like this
Instead of
|
Fix PR from @velotioaastha - wandb/helm-charts#231 |
@jsbroks @danielpanzella - Can we please review the fix PR here? Thanks. |
Users should be able to specify the license string as a string as is currently supported or as a reference to secret in the cluster. There may be some benefit to allowing the same key to be used for both, but it probably needs to be a separate field.
It is expected that the user will create this secret outside operator or the chart
If its possible to use the same key, these would be the desired shapes
If that is not reasonable then a new field will work
licenseSecret
if specified, should take precedence over the string.I think only the app chart uses the current value to create a secret which is referenced in the deployment. The secret should be made conditional and the references updated
The text was updated successfully, but these errors were encountered: