-
-
Notifications
You must be signed in to change notification settings - Fork 54
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
Support for easy hardware acceleration config in values #138
Comments
values.yaml: machine-learning:
image:
tag: v1.118.2-openvino |
But this way it will not use the global tag declaration right? I have configured renovate to look at the global one |
Correct, there's no way to combine the two. It'd be nice to have hwaccel support in the chart so you can just set a type to use and it handles appending the right tag as well as setting the container resources etc. I'll rename this issue to be a FR for that. |
I don't know how any of the hardware accel mappings work in kubernetes, so if people who are currently using it can post their values here for the different methods that'd be a useful reference. |
That would be perfect! Thanks |
Just for some more context, my setup is based on node-feature-discovery with intel operator and gpu plugin. I am able to just give it a request of
If I do a |
Adding it via a device plugin is definitely sufficient, no need for any manual dev mount stuff! |
Hi!
I was able to make HW transcoding work by modifying the live yaml but I am not sure how this charts supports it.
The text was updated successfully, but these errors were encountered: