We don't expect to see unparseable image names in running pods, since k8s was able to parse all the image names when the pod was created. However, that appears to be what's happening in #71, so we should handle the case to avoid dereferencing a nil pointer.
We don't expect to see unparseable image names in running pods, since k8s was able to parse all the image names when the pod was created. However, that appears to be what's happening in #71, so we should handle the case to avoid dereferencing a nil pointer.