support pod label collection on MIG#660
Open
Raid57 wants to merge 1 commit into
Open
Conversation
(cherry picked from commit 1c7178849aabb069cc3b0b3608b8464a17980dcd)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Builds upon the existing Kubernetes pod label support by ensuring labels resolved for MIG workloads are propagated to the final exported metrics.
Today, pod metadata can already be resolved for MIG-backed workloads, but the labels are not copied into the final metrics emitted from the shared/MIG enrichment path. This causes inconsistent behavior between standard GPU metrics and MIG metrics, and prevents label-based filtering and aggregation for MIG workloads.
Implementation
Extends the metric enrichment flow for MIG/shared GPU workloads so that the pod labels already collected by
PodMapperare copied into the final metric labels, matching the behavior of the standard GPU mapping path.Key Changes
Configuration
No new flags or configuration are introduced.
Existing Kubernetes pod label settings continue to apply, and this change makes that behavior consistent for MIG metrics as well.