RUN TCP/IP | Morgan Lucas is Tech Blogging

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?

Exactly what it says on the tin.

An article by Tyler Stearns on Solutions Review. Read it at the source, the gist is - Google Cloud Launcher is now Google Cloud Platform Marketplace. Container based applications like Kubernetes. The New Marketplace has easily deployable apps. Security partners Aqua, DivvyCloud, and CyberArk approach Kubernetes security differently. There's more things about Databases, Storage, and Machine Learning at the article, so go read it.

SCALING: Changing the number of replicas in a Deployment. The Deployment only created one Pod to run our application, and that just won't do. We need more when traffic increases. When you scale, you make sure new Pods are created and scheduled to Nodes who have the resources. Scaling in will "reduce the number of Pods to the new desired state". "Can we do this automatically?" Yes! But not now. Running multiple application instances require a way to distribute traffic to them all. There is an integrated load-balancers with Services to do so, and they will continuously monitor the running Pods with endpoints , ensuring the traffic is sent only to available Pods.

In Pokemon, but one of them was Paras, a little bug with two little mushrooms on its back. It evolved into Parasect, which was the shell of the body controlled by the parasite mushrooms. I was trying to make an allegory with today’s subject matter but it doesn’t quite fit.  If a Worker Node dies, the Pods running on it die too. A Replication Controller ensures that a specific number of pod replicas are always up and running by creating new pods in an instance like this. Remember that each Pod in a Cluster has a unique IP, even those on the same Node, so how do pods let everyone else know about the changes so everything keeps working.

The title was initially 'Bring Back the Node', but I didn't think people would get the reference. Applause if you did! Making a deployment in the previous post made a POD for our application to be hosted in. ($POD_NAME variable) Pods are an abstraction that represent 1 or more containers and shared resources for them, like Volumes, what the page describes as ‘Networking, as a unique cluster IP address’ (Sounds exciting, like a distant relative of subnetting or vlans)  and instructions on  how to actually run the containers.

Talk about 'Things that are going to be outdated in about five minutes,". So, while I did install Minikube onto my Mac, it brought my machine nearly to a crawl. Sticking with the in-house module for now. Full disclaimer; I did this when I was very tired so the images may not line up in the right spots.

(I was going to title this 'Kubernetes Khan', like Kublai Khan). First; What is this? I received some advice that Containers are all the rage. Containers make it possible for software on one system to work reliably upon another by shoving the environment software needs to run in a container. It's like an ant farm - The ants still work if you move them from the forest to the beach. We're going to learn Kubernetes, which schedules and distributes containers across clusters.