Skip to content

Helm fix identical template selector#1481

Closed
peterzandbergen wants to merge 4 commits intoNVIDIA:mainfrom
peterzandbergen:helm-fix-identical-template-selector
Closed

Helm fix identical template selector#1481
peterzandbergen wants to merge 4 commits intoNVIDIA:mainfrom
peterzandbergen:helm-fix-identical-template-selector

Conversation

@peterzandbergen
Copy link
Copy Markdown

The helm chart used the same labels for the selector in the daemon sets

I have fixed this for all daemon sets, being the mps and gfd.

@copy-pr-bot
Copy link
Copy Markdown

copy-pr-bot Bot commented Oct 29, 2025

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@uristernik
Copy link
Copy Markdown
Contributor

@elezar can someone have a look here?

@npdgm
Copy link
Copy Markdown

npdgm commented Jan 16, 2026

Per Helm Standard Labels I think we should keep common app.kubernetes.io/name and app.kubernetes.io/instance for all pod controllers, and instead introduce app.kubernetes.io/component to each DaemonSet. Also templates won't need repetition and can then call a common one for name and component.

@rahulait rahulait self-assigned this Apr 17, 2026
@rahulait
Copy link
Copy Markdown
Contributor

Thanks @peterzandbergen. Can you make sure commits are signed and fix the merge conflicts.

type: application
description: A Helm chart for the nvidia-device-plugin on Kubernetes
version: "0.18.0"
version: "0.18.1"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets not bump the version. We bump it when we want to release.

@rahulait
Copy link
Copy Markdown
Contributor

Per Helm Standard Labels I think we should keep common app.kubernetes.io/name and app.kubernetes.io/instance for all pod controllers, and instead introduce app.kubernetes.io/component to each DaemonSet. Also templates won't need repetition and can then call a common one for name and component.

Yeah, agree with this. We can just introduce additional app.kubernetes.io/component: {{ .component }} for each daemonset.

So each daemonsets / pods labels will be like:

# device-plugin
app.kubernetes.io/name: nvidia-device-plugin
app.kubernetes.io/instance: my-release
app.kubernetes.io/component: device-plugin

# gfd
app.kubernetes.io/name: nvidia-device-plugin
app.kubernetes.io/instance: my-release
app.kubernetes.io/component: gpu-feature-discovery

# mps
app.kubernetes.io/name: nvidia-device-plugin
app.kubernetes.io/instance: my-release
app.kubernetes.io/component: mps-control-daemon

@rahulait
Copy link
Copy Markdown
Contributor

Closing this PR in favor of #1716

@rahulait rahulait closed this Apr 22, 2026
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

Successfully merging this pull request may close these issues.

4 participants