-
Notifications
You must be signed in to change notification settings - Fork 385
Build / push is painful if not using gcr and gke #67
Comments
+1, I do not personally use either of those things.
…On Tue, Nov 29, 2016 at 9:56 PM, Kent Rancourt ***@***.***> wrote:
It's been tough trying to get through the walkthrough on minikube. (And
because I am working locally, I really only want to push built images to a
local registry.) I think the difficulty I'm encountering exposes a fault
that the build, push, and (helm) install are too tightly coupled to an
(unfair) expectation that such Google services are being used.
I would propose that we abandon such assumptions and use a more generic
option to allow users to simply specify a docker registry URL without any
assumption that it is gcr.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#67>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAWXmAxbK349uCSNpO6RADyfycx0czZpks5rDOX0gaJpZM4K_v4p>
.
|
I'd say that it is however important that it be possible to use build/push with registries commonly used. I.e. that it be possible to (easily) have make push into gcr (or any other registry). Specifically it means making it possible to authenticate against the registry so that the docker push command succeeds. The goal, IMO, is ease of use and not requiring lot of manual steps to use the system. It would be great to add support for other registries without degrading the experience with gcr, and ensuring that experience with other registries is equally easy, or even easier. |
It can simply be stated as a pre-requisite that the user is authenticated to whatever registry they wish to push to. That's not unreasonable and it does not undermine ease of use for any registry-- gcr included. I think one thing we really need to try and avoid here is boiling the ocean. I've spent most of my evening poring over the build / push process, scripts, etc. and it seems that so much of what was built, presumably as a convenience, makes lots of assumptions that make those same bits a hindrance for anyone who doesn't satisfy those assumptions. Personally, I'm inclined to say that less is more here. |
Closing, as I have replaced this with a more concrete proposal on how to move forward. See #77 |
It's been tough trying to get through the walkthrough on minikube. (And because I am working locally, I really only want to push built images to a local registry.) I think the difficulty I'm encountering exposes a fault that the build, push, and (helm) install are too tightly coupled to an (unfair) expectation that such Google services are being used.
I would propose that we abandon such assumptions and use a more generic option to allow users to simply specify a docker registry URL without any assumption that it is gcr.
The text was updated successfully, but these errors were encountered: