NVIDIA / NVIDIA/k8s-device-plugin
MPS control daemon wrong pod selector
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.9k
- Forks
- 868
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 27
Description
I’ve installed the latest version of the nvidia-device-plugin (0.16.2) using Helm. Alongside the device plugin, the MPS control daemon is also being installed. The problem is that in the MPS control daemon set, the pod selector is the same as in the device plugin daemon set. As a result, the device plugin pod starts first, and both controllers attempt to manage the same pod, preventing MPS from ever starting.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the Helm templates for the MPS control daemon set and the device plugin daemon set, focusing on their pod selectors. Confirm that both controllers currently target the same pods, then make the selectors distinct and verify that the MPS control daemon can start without managing the device plugin pod.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, helm, kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100