-
Notifications
You must be signed in to change notification settings - Fork 40k
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
WIP: add kubectl push command #17771
Conversation
Labelling this PR as size/L |
@@ -244,8 +244,6 @@ func (pf *PortForwarder) nextRequestID() int { | |||
func (pf *PortForwarder) handleConnection(conn net.Conn, port ForwardedPort) { | |||
defer conn.Close() | |||
|
|||
glog.Infof("Handling connection for %d", port.Local) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have to remove this to make output happy, any suggestions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
GCE e2e test build/test passed for commit 7c4b07c. |
I am curious why I am pretty sure in OpenShift we allow multiple registries, do you foresee ever doing the same on base Kubernetes? @smarterclayton @ncdc - thoughts on this command? |
@derekwaynecarr |
I'm a bit skeptical that we're ready for something this opinionated in the cli without a larger discussion about the registry addon and extension CLIs. I also don't think this has to be a kubectl command - it can very easily be something in contrib/. It assumes details of the registry addon that I don't think represent the standard needs of a registry deployed with Kube (like security). |
Agreed. That's why I didn't try to fully implement this. What's the plan for 'larger discussion' for such extension CLIs? |
Add a command to make pushing image to cluster registry eaiser. Some unanswered questions at #17707