-
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
Add image replacement support for multicontainer pods in kubectl rolling-update #9868
Add image replacement support for multicontainer pods in kubectl rolling-update #9868
Conversation
…t a multi-container pod.
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. |
Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist") If this message is too spammy, please complain to ixdy. |
Additional CLA was submitted - do I need to do anything to have this rechecked by the system? Also - I can't view the shippable failure details. If someone can point me to the error, I'll take a look. Thanks |
Make sure you did: |
Your commits are authored by matthewsimon-ww who has not signed the CLA. |
Looks like this fixes #9868 |
Assigned to davidopp who has previously shown interested in rolling updated. Feel free to punt elsewhere. |
We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm. |
Hi, you are mistaken, they were authored by me. Thanks. On Tue, Jun 16, 2015 at 1:16 PM, googlebot notifications@github.com wrote:
|
Thanks for the feedback erictune, I've resolved the boilerplate and other issues as per the hooks, and also fixed a unit test I missed earlier. |
Thanks very much for the PR! Unfortunately, we're currently in "code freeze" in preparation for our 1.0 release, so we can't merge this right now. However, this feature is obviously useful and we can definitely merge it after the code freeze is over. In the mean time, it would be great if you could add some tests. |
Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist") If this message is too spammy, please complain to ixdy. |
@@ -74,6 +74,7 @@ func NewCmdRollingUpdate(f *cmdutil.Factory, out io.Writer) *cobra.Command { | |||
cmd.Flags().String("timeout", timeout, `Max time to wait for a controller to update before giving up. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h".`) | |||
cmd.Flags().StringP("filename", "f", "", "Filename or URL to file to use to create the new controller.") | |||
cmd.Flags().String("image", "", "Image to upgrade the controller to. Can not be used with --filename/-f") | |||
cmd.Flags().String("container-name", "", "Container name which will have its image upgraded. Only relevant when --image is specified, ignored otherwise. Required when using --image on a multi-container pod") |
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.
Please conform to the convention of other commands, such as log and exec: --container
, -c
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/kubectl/cmd/log.go#L85
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/kubectl/cmd/exec.go#L68
We're trying to clear the PR backlog. Please rebase. |
What branch should I rebase to? Master? Or the 1.0? Sent from my iPhone
|
Rebase to master. I believe release branches are considered final except
|
Yes, master, sorry. |
Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist") If this message is too spammy, please complain to ixdy. |
cc @kubernetes/kubectl |
@@ -36,6 +36,7 @@ $ kubectl rolling-update frontend --image=image:v2 | |||
### Options | |||
|
|||
``` | |||
--container-name="": Container name which will have its image upgraded. Only relevant when --image is specified, ignored otherwise. Required when using --image on a multi-container pod |
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.
Please be consistent with other commands that have container-name flags. For instance:
https://github.com/kubernetes/kubernetes/blob/master/pkg/kubectl/cmd/exec.go#L68
Please rebase. |
Ping @mhenniges could you rebase? @k8s-bot ok to test |
GCE e2e build/test failed for commit 5c55120. |
Labelling this PR as size/M |
This PR appears to be inactive since July. Closing. |
So this will never be added to K8S? |
@coleca please see #13483 (comment) |
Added support to kubectl rolling-update with the --image flag when operating on multi-container pods. The container to update is selected by the new --container-name option.
All existing behavior of kubectl was preserved.
Thanks for reading!