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

Allow adding custom labels to the "gpu-operator" ServiceMonitor #710

Open
peihsuant opened this issue Apr 30, 2024 · 12 comments
Open

Allow adding custom labels to the "gpu-operator" ServiceMonitor #710

peihsuant opened this issue Apr 30, 2024 · 12 comments
Labels
feature issue/PR that proposes a new feature or functionality

Comments

@peihsuant
Copy link

feature description

There is a ServiceMonitor named gpu-operator that was automatically created and is owned by the ClusterPolicy. I would like to add custom labels to it so the Prometheus instance with a serviceMonitorSelector can scrape it.

Thanks.

@cdesiniotis
Copy link
Contributor

@peihsuant this is already possible today with the dcgmExporter.serviceMonitor.additionalLabels field in clusterpolicy.

@peihsuant
Copy link
Author

Hi @cdesiniotis, what I need to modify is the servicemonitor of gpu-operator not dcgmExporter, thanks.

@cdesiniotis cdesiniotis added the feature issue/PR that proposes a new feature or functionality label May 2, 2024
@cdesiniotis
Copy link
Contributor

@peihsuant apologies, I misread the description. I see we do not have any fields for configuring the gpu-operator ServiceMonitor, unlike for dcgmExporter.

If you are interested in working on this, PRs against our gitlab repository are always welcome. https://gitlab.com/nvidia/kubernetes/gpu-operator

@csauoss
Copy link

csauoss commented Jul 5, 2024

@cdesiniotis I would like to give this a try if its still needed.

@cdesiniotis
Copy link
Contributor

@csauoss yes this is open. PRs are welcome here https://github.com/NVIDIA/gpu-operator/pulls

@csauoss
Copy link

csauoss commented Jul 15, 2024

@cdesiniotis thank you, but should I create a MR in gitlab(since documentation mentions it) or a PR here is fine as well?

@csauoss
Copy link

csauoss commented Jul 17, 2024

@cdesiniotis I created MR 1099 in gitlab for this issue for now. Please review it when you get a chance.

@cdesiniotis
Copy link
Contributor

cdesiniotis commented Jul 18, 2024

@csauoss we have recently migrated to GitHub and now perform development here. Can you open your PR against https://github.com/NVIDIA/gpu-operator?

(since documentation mentions it)

Can you point me to where our documentation states this?

@csauoss
Copy link

csauoss commented Jul 18, 2024

Thanks @cdesiniotis! sounds good, will PR here in that case. Here in CONTRIBUTING.md file is where I saw references to Gitlab.

@csauoss
Copy link

csauoss commented Jul 18, 2024

Thanks @cdesiniotis! sounds good, will PR here in that case. Here in CONTRIBUTING.md file is where I saw references to Gitlab.

Actually the pr template in github too

@cdesiniotis
Copy link
Contributor

Thank you for pointing this out. I have filed #851 to update our docs.

@csauoss
Copy link

csauoss commented Jul 19, 2024

@cdesiniotis I created pr #850 in github to address this issue. Please review it when you get a chance. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature issue/PR that proposes a new feature or functionality
Projects
None yet
Development

No branches or pull requests

3 participants