[chore] [receiver/k8s_cluster] Fix nil dereference in RecordSpecMetrics when container status is missing#47554
Merged
dmitryax merged 1 commit intoApr 10, 2026
Conversation
…s when container status is missing Guard docker.ParseImageName and LastTerminationState access under a single cs != nil block to avoid a panic when a container spec exists but kubelet has not yet reported its status. Assisted-by: Claude Opus 4.6
dmitryax
requested review from
a team,
ChrsMark and
TylerHelmuth
as code owners
crobert-1
approved these changes
Apr 10, 2026
AndrewCharlesHay
pushed a commit
to AndrewCharlesHay/opentelemetry-collector-contrib
that referenced
this pull request
Apr 23, 2026
…cs when container status is missing (open-telemetry#47554) Replacing open-telemetry#47538 as we need to merge it before the next release to avoid regression. Guard `docker.ParseImageName` and `LastTerminationState` access under a single cs != nil block to avoid a panic when a container spec exists but kubelet has not yet reported its status. Taking opportunity to increase test coverage of the `receiver/k8sclusterreceiver/internal/container` package
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
3 participants
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.
Replacing #47538 as we need to merge it before the next release to avoid regression.
Guard
docker.ParseImageNameandLastTerminationStateaccess under a single cs != nil block to avoid a panic when a container spec exists but kubelet has not yet reported its status.Taking opportunity to increase test coverage of the
receiver/k8sclusterreceiver/internal/containerpackage