Skip to content

Comments

[dcgm-exporter] Add configure externalTrafficPolicy and nodePort for dcgmExporter service#1516

Draft
Alja9 wants to merge 3 commits intoNVIDIA:mainfrom
Alja9:featService
Draft

[dcgm-exporter] Add configure externalTrafficPolicy and nodePort for dcgmExporter service#1516
Alja9 wants to merge 3 commits intoNVIDIA:mainfrom
Alja9:featService

Conversation

@Alja9
Copy link

@Alja9 Alja9 commented Jul 2, 2025

Because the dcgmExporter service supports configuring types, in my case I use a different cluster as a monitoring center so I need NodePort type and I can't use IP pod or original source IP for scraping, but externalTrafficPolicy: Cluster would really help in that case.

But this will also help users if they need externalTrafficPolicy: Local such as cases where only specific users need node local routing or to preserve the original IP. Reference : https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip

…service

Signed-off-by: aldi.j <aldi.jayadi222@gmail.com>
@copy-pr-bot
Copy link

copy-pr-bot bot commented Jul 2, 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.

Alja9 added 2 commits July 2, 2025 22:55
Signed-off-by: aldi.j <aldi.jayadi222@gmail.com>
Signed-off-by: aldi.j <aldi.jayadi222@gmail.com>
@Alja9
Copy link
Author

Alja9 commented Jul 2, 2025

I have raised PR to dcgm exporter too : NVIDIA/dcgm-exporter#518

@Alja9 Alja9 changed the title [dcgm-exporter] Add configure externalTrafficPolicy for dcgmExporter service [dcgm-exporter] Add configure externalTrafficPolicy and nodePort for dcgmExporter service Jul 2, 2025
@Alja9 Alja9 marked this pull request as draft July 7, 2025 04:21
@elezar elezar removed their request for review October 15, 2025 13:52
@github-actions
Copy link
Contributor

This PR is stale because it has been open 90 days with no activity. This PR will be closed in 30 days unless new comments are made or the stale label is removed. To skip these checks, apply the "lifecycle/frozen" label.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 20, 2026
@rahulait rahulait removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 23, 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.

2 participants