Skip to main content

"That's So Sad, Kubernetes, Deploy It Anyway."


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.



The cluster is running, so let’s deploy the containerized applications.

I’ll make a Deployment configuration, which tells Kubernetes how to create and update app instances.

It’ll schedule Instances onto individual nodes in our cluster to be monitored by the Deployment Controller.

If something goes down, or is deleted, the DC replaces it quickly and without much concern, much like replacing a minimum wage worker.

Kubectl is the CLI for Kubernetes, once again using the API to talk with the cluster.

When making a deployment, you need to specify the container image and number of replicas to run.

Put your applications into one of the supported container formats (?) to be deployed on the system.

kubectl commands have their own format;
kubectl [action][resource]

action - create, describe, modify
on the resource - node, container.

I use kubectl version again and see clearly now that Client and Server versions are installed.

The get nodes command also shows the same information as last time - minikube is ready.

Before deploying the app, let’s make sure it runs. We need to provide the
- Deployment name (I think it’s just kubernetes-bootcamp here)
- App image location (respository url for things outside of Docker hub)
- Which app to run the port on.

The command is;
kubectl run kubernetes-bootcamp —image=gcr.io/google-samples/kubernetes-bootcamp:v1 —port8080


Nice.

How many times is it running?



It’s running inside a container on our node, in a private, isolated network. kubectl is interacting through an API endpoint.

It can also create a proxy to forward communications into the clusterwide privage network, and stopped by ctrl+c.


A connection between terminal and cluster.

The API will automatically make an endpoint for each pod based upon the name that we can see through the proxy.

But what is the pod name?
(It’s stored in POD_NAME variable)

Let’s make the http request to the app in the pod;


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