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
I am running an instance of harbor on a VM outside my cluster, I can't go around that. Also, I have a few ci pipelines that use kaniko as a way to build and push images. Is there a way to use this project to replicate the push function of kaniko (without docker-daemon)?
My team has been looking for an alternative for a while.
Thank you very much for this project.
The text was updated successfully, but these errors were encountered:
@saharlaor thanks for sharing your use-case! This project does not currently support image building (though it could). The primary function of this package is being able to govern access to push images from outside of a cluster to a registry running in-cluster using k8s RBAC. It sounds like you may be doing the opposite (build images in cluster, push to registry outside). Does that sound right? What shortcomings are you seeing with kaniko that you would like to address?
I am running an instance of harbor on a VM outside my cluster, I can't go around that. Also, I have a few ci pipelines that use kaniko as a way to build and push images. Is there a way to use this project to replicate the push function of kaniko (without docker-daemon)?
My team has been looking for an alternative for a while.
Thank you very much for this project.
The text was updated successfully, but these errors were encountered: