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

Azure Networking Options - Core Cloud Services

I have done a lot of AWS things on here. Time to give Azure some attention. After all, since employers don't think Cisco or COMPTIA certifications are important, maybe Microsoft ones are?

First, let's really think about why these are the two biggest cloud services providers in the world:

They've been doing internet things for a long time.Amazon launched in 1995, a virtual bookstore.
Microsoft, well, you know. 

They've lived, breathed, and frankly, created, infrastructure that we use today, that they're selling to us today. Of course the Store of Everything and the Company of Everything would encourage us to put everything in their hands.

Also: Azure has a lot less silly names for modules. Important. I appreciate straightforwardness.


I said 'a lot less', not '100% sensible names'

Microsoft has a clear set of Azure Fundamentals that anyone can interact with. Let's talk about networking basics, basically to say, again, "Hi, employers, I have an …

The Updated "What I'm Looking For In A Role" Post (2020)

Thank you for wanting to help with my job search! Here are some parameters.


Ideal:
Part time remote, text based support. It's a little far fetched, but the positions do exist. I enjoy having the flexibility to take on temporary projects from time to time!
Also; If anything sounds weird, out there, or unusual - Feel free to e-mail me. Doesn't have to be tech related. I just have to possibly find it interesting, fun, and with the possibility to get up and stretch when I want to.

Feel free to suggest something full time (still remote) that can fit within the below criteria;


Skills:


Informative writing about tech concepts and consumer electronics. You want to pay me to write more of *waves hand* this? I am game.
IT SupportUX Auditing [See Here][See example job description here] eCommerce merchandising [See Here]Azure
Cisco routing and switching technician
Proofreading

Volunteering:
Find me on Jumpstart and CareerVillage.
Jobs:
Network Tech IT SupportTechnical Consulting

I'm not super i…

Grace Hopper Celebration 2019 (GHC19)

From Aicha Evans' speech at the Keynote.
September 6th - I receive an email from Anita B Organization, saying "We read your application, we like your website, and here's a free ticket to GHC 2019 in Orlando, Florida!"


After a few more questions, it seemed everything was on the up and up, and so I accepted - and that's what this post is about!

For those who don't know, Grace Hopper Celebration is the largest gathering of Women in Technology in the world.

On a personal note, This is the first trip I've taken without my parents. Sure, they've left me behind to go on vacations, but I've never left them. I was totally worried! But you know what happened?

I met a lot of cool people in Orlando, learned a lot of neat things, and had a blast just walking around airports for upwards of 8 hours.

New Delta Sky Club on Wikimedia I really, really love airports! And I survived.

I know in the past, I've wormed my way out of jobs despite being interested simpl…