Skip to content
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

Kubernetes Container Image Discovery #564

Closed
Tracked by #558
Tehsmash opened this issue Aug 16, 2023 · 0 comments · Fixed by #711
Closed
Tracked by #558

Kubernetes Container Image Discovery #564

Tehsmash opened this issue Aug 16, 2023 · 0 comments · Fixed by #711
Labels
enhancement New feature or request

Comments

@Tehsmash
Copy link
Contributor

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.

@Tehsmash Tehsmash mentioned this issue Aug 16, 2023
8 tasks
@Tehsmash Tehsmash added the enhancement New feature or request label Aug 21, 2023
@lgecse lgecse added this to the v0.6.0 milestone Aug 25, 2023
@lgecse lgecse removed this from the v0.6.0 milestone Sep 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants