Skip to main content

Kubernetes: A Rolling Deployment...



This is the last module of our beginner’s tutorial! My how time flies.

So, what’s the last piece of knowledge?

Rolling updates that allow Deployments updates to take place with no downtime.

How?



 By incrementally updating Pods instances with new ones, scheduled on Nodes with available resources.

Before, we just told our application to run multiple instances so we could update and not affect availability.

The default maximum # of pods that can be unavailable during an update is one (1), but you can make that another number or even a percentage of active pods.

Kubernetes updates versions and Deployment updates can be reverted back if it doesn’t work out so nicely.

What if said Deployment is exposed publicly? Then the Service will load balance the traffic to Pods available (aka, not being updated at that exact time)

Rolling updates promote applications from one environment to another by container image updates, or rollback to previous versions, with the continuous integration and delivery of applications - No downtime!

Deployments and Pods - Still 4/4!



kubectl describe pods gives us a lot of information, but somewhere in that infodump tells us that our Pods are running version 1 - We want to update them.

Changed the layout!
Seems like we updated Pods called jocatalin. See what happens next!









Let’s make sure the update is working;

Enjoy stats such as the

  • Name (kubernetes-bootcamp)
  • The node port (<unset> 31139/TCP)
  • The IP and port (10.101.170.210 and <unset> 8080/TCP).


Make an enviroment variable called NODE_PORT with the port assigned.



And there’s our variable with the corresponding number.

curl $(minikube ip):$NODE_PORT
 Hits a different Pod with every request - all Pods are running the latest version.

Let’s also confirm with a rollout status command;

kubectl rollout status deployments/kubernetes-bootcamp

The response we get is essentially “The deployment is out!”
Let’s make sure the update is working;

Enjoy stats such as the name (kubernetes-bootcamp), the node port (<unset> 31139/TCP), and the IP and port (10.101.170.210 and <unset> 8080/TCP),

Make an enviroment variable called NODE_PORT with the port assigned.

And there’s our variable with the corresponding number.

curl $(minikube ip):$NODE_PORT hits a different Pod with every request - all Pods are running the latest version.

Let’s also confirm with a rollout status command;

kubectl rollout status deployments/kubernetes-bootcamp

The response we get is essentially “The deployment is out!”

Perhaps the update isn’t what we wanted, so let’s roll it back.

The version is updaated to 10 and let’s see our deployments.



Hmm. One too many. That’s more resources than we need.

Using the describe modifier gives us a lot of information, but in short; There’s no image called v10 in the repository.



So let’s roll it back with the rollout command to go back to v2, and there are four pods once again.



Comments

Popular posts from this blog

What Do You Need? [AKA; List of Offered Services / My Next Role] (2020)

UPDATED 2021 I am a trusted outsourced remote consultant for your company.   I enjoy having the flexibility to take on temporary projects from time to time! I start at part-time, temp work for now. If we like each other, we can renegotiate. If anything sounds weird, out there, or unusual - Feel free to e-mail me .  3 Services Offered Technical: Cloud Technician     Azure [ See tag ] WORKING ON: Infrastructure As Code (Specifically Terraform/Azure and CloudFormation/AWS)  Support [Web: Example Job Description ] [Text : Example Description ]     I help you with adjustments in HTML, CSS, and Javascript.     When you email a business a question and they answer? That's me.   IT Operations Tech [ Example Job Description ]     Hardware and SaaS support.     Cisco routing and switching (Networking). CCNA, A+, Sec+, Azure certified WORKING ON: Junos Networking  Writing :      You want to pay me to write more of *waves hand* this blog? I am game .     I write B2C e-mails going out to o

Contactless Tech’s Role in the New Guest Experience ft. Intelity and The George

 Contactless hospitality technology is growing. You want to get away, and you'll be damned if a little thing like a deadly virus will stop you! But you still don't want to touch things. Ew. During the chat between INTELITY CEO Robert Stevenson and THE GEORGE Director of Operations Kerrie Hunter, you’ll learn how the historic boutique hotel has adapted a mobile-first guest experience in the wake of COVID-19—and how they see contactless technology affecting the future of hospitality. I don't remember how I found INTELITY (probably hoping to score a position with them), but I liked them enough to stay on the e-mail lists.  

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H