Rancher for Microservices : Upgrades and Rollback.

Ravi Vagadia
Sep 9, 2018 · 4 min read

So far we’ve checked how easy it is to get up and running with Rancher. We also deployed a very simple HTTP service on our Rancher Cluster, attached an L7 Load balancer and successfully scaled up containers running this service. In this post, I’ll use the same service with a slight modification which is version number now return as 2.0 in HTTP response.

So far our service is on v1.0, let’s say we’ve worked very hard and released a new version with latest features. We want to release it to our users while ensuring there is no downtime during…

Keep the story going. Sign up for an extra free read.

You've completed your member preview for this month, but when you sign up for a free Medium account, you get one more story.
Already have an account? Sign in

Written by

Computer Geek. M.Sc. IT, DA-IICT. Software Developer. Interested in Distributed Computing, DevOps and Cloud Infrastructure.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade