<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kuebrnetes on BrainBit Latest Articles</title><link>https://brainbit.uk/tags/kuebrnetes/</link><description>Recent content in Kuebrnetes on BrainBit Latest Articles</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 31 May 2017 07:26:25 +0000</lastBuildDate><atom:link href="https://brainbit.uk/tags/kuebrnetes/index.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes 101 #4 Rollouts</title><link>https://brainbit.uk/posts/kubernetes-sharp-rollouts/</link><pubDate>Wed, 31 May 2017 07:26:25 +0000</pubDate><guid>https://brainbit.uk/posts/kubernetes-sharp-rollouts/</guid><description>Quick one about rollouts , so the idea is “update” docker images to a new version “without” disrupting services… that is relative and it is something i would like to investigate later on.
But the general idea is , you have a deployment using a given version:
So this deployment will create a replicaset with 3 containers running nginx:1.7.9.
So the idea is that you change the image and update the deployment , this can be done in a few different ways , but one of them would be:</description></item></channel></rss>