Skip to content
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

Deploy nvidia-device-plugin-daemonset to only certain nodes #547

Open
5 tasks done
Hayes-buzzni opened this issue Jul 10, 2023 · 2 comments
Open
5 tasks done

Deploy nvidia-device-plugin-daemonset to only certain nodes #547

Hayes-buzzni opened this issue Jul 10, 2023 · 2 comments

Comments

@Hayes-buzzni
Copy link

Hayes-buzzni commented Jul 10, 2023

The template below is mostly useful for bug reports and support questions. Feel free to remove anything which doesn't apply to you and add more information where it makes sense.

1. Quick Debug Checklist

  • Are you running on an Ubuntu 18.04 node?
  • Are you running Kubernetes v1.13+?
  • Are you running Docker (>= 18.06) or CRIO (>= 1.13+)?
  • Do you have i2c_core and ipmi_msghandler loaded on the nodes?
  • Did you apply the CRD (kubectl describe clusterpolicies --all-namespaces)

1. Issue or feature description

I'm currently trying to deploy gpu-operator to only certain nodes (at least the nvidia-device-plugin) using helm. I've checked all the issue pages and documentation, but I haven't found a way to deploy to specific nodes. I've also tried changing the templete to specify affinity, but that didn't work well. Is there any way to deploy gpu-operator, or the nvidia-device-plugin that gpu-operator deploys, to specific nodes?

@rockholla
Copy link

I created a related PR to add node selector capabilities to common daemonset config via the ClusterPolicy: https://gitlab.com/nvidia/kubernetes/gpu-operator/-/merge_requests/976. I think this should address the need here.

@chaunceyjiang
Copy link

Hi, @rockholla Do you have any new progress? I've also encountered this problem. If you don't have spare time, I can continue with your subsequent work.

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

No branches or pull requests

3 participants