github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-09-14 05:36:12 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #24645 from jlowdermilk/rolling-update

Browse Source 
Automatic merge from submit-queue

kubectl rolling-update support for same image

Fixes #23497.

Enables `kubectl rolling-update --image` to the same image, adding a `--image-pull-policy` flag to remove ambiguity. This allows rolling-update to behave as an "update and/or restart" (https://github.com/kubernetes/kubernetes/issues/23497#issuecomment-212349730), or as a forced update when the same tag can mean multiple versions (e.g. `:latest`). cc @janetkuo @nikhiljindal
This commit is contained in:
k8s-merge-robot
2016-05-04 07:24:22 -07:00
parent 3b63b06b1b 9b91750284
commit 1642083e60
10 changed files with 103 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/man/man1/kubectl-rolling-update.1
View File

@@ -42,6 +42,10 @@ existing replication controller and overwrite at least one (common) label in its
\fB\-\-image\fP=""
Image to use for upgrading the replication controller. Must be distinct from the existing image (either new image or new image tag). Can not be used with \-\-filename/\-f
.PP
\fB\-\-image\-pull\-policy\fP=""
Explicit policy for when to pull container images. Required when \-\-image is same as existing image, ignored otherwise.
.PP
\fB\-\-include\-extended\-apis\fP=true
If true, include definitions of new APIs via calls to the API server. [default true]