Skip to content
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

Jump to bottom

Rolling Update to New "latest" Image #11348

Closed
esecules opened this issue Jul 16, 2015 · 2 comments
Closed

Rolling Update to New "latest" Image #11348

esecules opened this issue Jul 16, 2015 · 2 comments
Labels
area/app-lifecycle area/kubectl priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@esecules
Copy link

Is it possible to do a rolling update where kubernetes pulls and uses the newest Docker image with the "latest" tag rather than having to change the replication controller spec to use version 2.0.0 instead of 1.2.3 for example?
@bgrant0607 bgrant0607 added kind/support Categorizes issue or PR as a support question. area/kubectl sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. labels Jul 16, 2015
@ArtfulCoder ArtfulCoder added this to the v1.0-post milestone Jul 16, 2015
@bgrant0607 bgrant0607 removed this from the v1.0-post milestone Jul 24, 2015
@bgrant0607 bgrant0607 added priority/backlog Higher priority than priority/awaiting-more-evidence. area/app-lifecycle labels Jul 27, 2015
@bgrant0607
Copy link
Member

Using "latest" leads to unpredictable behavior. Any pods that happen to be created for any reason (node death, scaling, rolling update of some other field) after the latest tag is retargeted to a new version would pull that new version. Is that what you want? (Well, there's also the issue of whether the imagePullPolicy may interfere.)

Or, would you like "latest" to be automatically translated to a tag referring to the current version? That was proposed in #1697. The v2 registry API should make that more feasible.

@goltermann goltermann removed the kind/support Categorizes issue or PR as a support question. label Aug 26, 2015
@bgrant0607 bgrant0607 added team/ux and removed sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. labels Sep 16, 2015
@bgrant0607
Copy link
Member

cc @nikhiljindal @ironcladlou

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/app-lifecycle area/kubectl priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@ArtfulCoder @esecules @bgrant0607 @goltermann