You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following design #527 we should implement container image discovery as part of the kubernetes provider added by #561.
The provider should list all the nodes in the cluster, and from the node's status field collect the list of containers which are currently stored in the node's container runtime. A ContainerImage asset should be returned for each discovered container.
We should use the reference/name with registry hash as the ID for the ContainerImage asset.
We should use the container image size as the ContainerImage asset size.
We should use the Node's architecture and OS as the ContainerImage architecture and os.
The text was updated successfully, but these errors were encountered:
Following design #527 we should implement container image discovery as part of the kubernetes provider added by #561.
The provider should list all the nodes in the cluster, and from the node's status field collect the list of containers which are currently stored in the node's container runtime. A ContainerImage asset should be returned for each discovered container.
We should use the reference/name with registry hash as the ID for the ContainerImage asset.
We should use the container image size as the ContainerImage asset size.
We should use the Node's architecture and OS as the ContainerImage architecture and os.
The text was updated successfully, but these errors were encountered: