-
Notifications
You must be signed in to change notification settings - Fork 285
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
pod.status.containerStatuses displayed image name incorrectly when image has multiple tags on the node #165
Comments
This behaviour is defined by CRI, and seems to be done the same way in containerd: repoTags, repoDigests := parseImageReferences(image.References)
if len(repoTags) > 0 {
// Based on current behavior of dockershim, this field should be
// image tag.
spec = &runtime.ImageSpec{Image: repoTags[0]}
}
if len(repoDigests) > 0 {
// Based on the CRI definition, this field will be consumed by user.
imageRef = repoDigests[0]
} Maybe the sort order can be tweaked, but otherwise it needs to be discussed in API ? Something for SIG Node, https://github.com/kubernetes/community/tree/master/sig-node |
Thank you for your prompt reply。@afbjorklund
I have a workaround with this issue: Code |
I'm not convinced that commenting it out entirely is a great workaround, and a 4 year old k8s issue which has more or less identical behavior across CRIs is something we should be hesitant to change. If there were going to be one, sorting What are the actual impacts of this, as a reason to resurrect a 4 year old issue? |
For more detail: pod.status.containerStatuses displayed image name incorrectly when image has multiple tags on the node
The text was updated successfully, but these errors were encountered: