yes, it makes sense, thank you On 28 September 2016 at 16:36, Rodrigo Campos <rodr...@sdfg.com.ar> wrote:
> On Wed, Sep 28, 2016 at 03:10:09PM +0100, Norman Khine wrote: > > Well the issue is that the new updated version is not deployed, so when i > > push to `develop` branch I have my image built on quay.io and this then > > triggers the update, but on the k8s cluster it is using the cached image > > version so the only way to change force an update is to alternate between > > :latest and :develop > > > > the same happen if i do it from the command line > > > > kubectl replace -f templates/pods/prod/app.yaml > > > > the only way to make a change is to alter the :tag in the yaml file from > > :develop to :latest and back! > > Ohh, I thought the new deployment was not working. But ok, no new > deployment is > made. > > Yes, that is like that. It's not easy to do a rollback otherwise, etc. if > you > always use the same tag. And I strongly recommend you to have this unless > you > have a good reason. For example, in our case, a new tag is created for > development each time automatically. But is particularly important in > production, IMHO, because you can know exactly which version was running, > have a > rollback or an update that fails and doesn't break the current running > pods, > etc. For example, if you use "latest" for your production env and have 3 > pods > running that, create a new image and tag it as latest again but the > readiness > test fails, you can't rollback (your previous image is overwritten, as > latest > points to the new one) and if one node crashes where the remaining pods are > running, they will fail to start because "latest" now is the new (failing) > image. > > I think you might be able to force a deploy with the kubectl set-image > option, > but haven't used it. > > > > Thanks a lot, > Rodrigo > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Kubernetes user discussion and Q&A" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/kubernetes-users/uh_ON-SrVoc/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > kubernetes-users+unsubscr...@googlegroups.com. > To post to this group, send email to kubernetes-users@googlegroups.com. > Visit this group at https://groups.google.com/group/kubernetes-users. > For more options, visit https://groups.google.com/d/optout. > -- %>>> "".join( [ {'*':'@','^':'.'}.get(c,None) or chr(97+(ord(c)-83)%26) for c in ",adym,*)&uzq^zqf" ] ) -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
