Open vladimirvivien opened 10 months ago
Hello, if no one is working on this yet, may I give it a try? 😄
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
@heylongdacoder Still interested in working on this ?
/remove-lifecycle stale
Hey @vladimirvivien, I have finished part of it with test cases. I will probably commit the code for review this weekend. But if I am blocking the progress, please feel free to take this! Many thanks!
Hi @heylongdacoder were you able to start PR?
@vladimirvivien sorry for the delay, I am working on it now.
@heylongdacoder no worries at all.
hey @vladimirvivien I would like to continue on this and confirm a few things.
BuildDockerLocal
and BuildDockerRemote
still relevant? RemoveLocalImage
, we would need the docker
binary since ko
does not have the functionality to remove images from Docker. Do you think that is ok?RemoveLocalImage
, if we want to remove the images that were uploaded to KinD, currently I got no idea on how to implement this, since KinD does not provide the functionality to remove the images. Let me know if you have idea about this.Thanks!
Hi @heylongdacoder when I wrote the issue, I was giving an example of what could work. You are free to implement whatever works best for the feature.
Thanks agai.
What do you want to see?
ko is a tool that automates the build and publication of Go code as container images. I think it would be useful to be able to create and deploy (locally or even remotely) container images during testing. This is especially true if building/testing Kubernetes controller/operators.
For instance, the following provides an idea of how that could work :
Extra Labels
No response