canonical / canonical/hardware-observer-operator

dcgm exporter conflict with self-installed dcgm exporter

Open
#525 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
20
Forks
18
Avg merge
1d 5h
Merged PRs (30d)
3

Description

Description

we are using helm installed gpu-operator which installed another set of dcgm exporter in the kubernetes cluster.
the dcgm exporter installed by hardware observer is conflicting with helm installed dcgm exporter with hostNetwork.

We need to have a way to scrape the helm installed dcgm exporter properly.

Charm revision

755

Juju version

3.6.21

Cloud

Kubernetes

Expected behaviour

COS is able to scraping helm installed dcgm exporter.

Reproduce / Test

When we want to scrape the metrics from dcgm exporter, we need to

  1. stop the snap installed dcgm exporter from hardware observer
  2. keep the relation between hardware observer with grafana-agent-k8s for the scrape to work.
  3. enable hostNetwork in helm installed dcgm exporter for scraping.
Notes & References

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test entry point is named in the report. Start by reproducing the three-step Kubernetes setup at charm revision 755 and trace how the hardware-observer relation to grafana-agent-k8s discovers and scrapes the Helm-installed DCGM exporter, including the hostNetwork setting. Done means COS can scrape the Helm-installed exporter without requiring the conflicting snap-installed exporter to run.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes, prometheus, python
Domain
cloud, devops, observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.