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)

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 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 over 280 people weekly. [ Example Job Description ]        Auditing :        Something doesn't work on your page. I can find it, or you can lose business. [ Here ] [ Example Job Description ]   Technical: Still as-needed, always remote, contract, or temporary. IT Operations Tech [ Example Job Description ]     Hardware and SaaS support.     Cisco routing and switching (Networking). CCNA, A+, Sec+, Azure certified WORKING ON: Junos Networking Cloud Technician     Azure [ See tag ]  Support [Web: Example Job Description ] [Text : Example

Portfolio of UX/Product Feedback [Vol. 1]

Have You Looked at Your Webpage From the Customer's View Lately? You have probably been linked here from a form or my resume. If you have any questions about what I'm looking for in a role, click here .   This post is not to shame, but to point out errors and hopefully make my talent for finding and documenting such mistakes clear to someone hiring. Contents: Instances where I offer constructive feedback on someone's website, logo, or app. Actions that were taken by the developers or artists.  I'm glad you want your webpages to be the best they can be with my help; If you need your sites audited, e-mail me . Latest Update -  November 20th, 2020.   Vol. 2 is here .

Wireless Diagnostics on Mac OS; Packet Sniffing on a WLAN

There's a post sitting in my drafts about Wireshark and how to sniff packets out of the air that was going to be about sniffing for authentication packets for Wi-Fi hotspots that aren't broadcasting SSID (Which you shouldn't do apparently! It's still not safe). I was watching this video to find a little more information about how to properly use Monitoring mode on my Macbook to sniff for WLAN packets on the network. So when he said "Just open up Wireless Diagnostics and sniff your network (check your width and channel)." It was shocking to me.