Closed mattfenwick closed 6 years ago
So, the containers are silently dropped until they have valid data. I saw this kind of thing occur in my testing, but wasn't sure exactly the root case. It did appear that the image/pod got annotated at the end of the day with the correct information, so I chalked it up to a state in the system where the pod didn't have all the data it needed. I suspect that field is filled in once the pod is actually pulled to the node.
We should probably investigate why this is happening, but the end result we really care about is if that pod gets all the annotations it is supposed to receive.
Can you verify if the pod/image is correctly annotated once it has been scanned by perceptor?
@rrati will do!
in pod/pkg/mapper/pod_mapper.go:
When
len(newCont.ImageID)
is 0, the container will not be included in what's sent over to perceptor -- making perceptor think that the pod does not have that container.Expected behavior:
ImageID
is""
: ????? is this a temporary thing that only happens while a container is spinning up? should the pod just be dropped?