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;


Labels:

Comments

Post a Comment

Popular posts from this blog

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
Post a Comment
Read more

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory
Post a Comment
Read more

Building, Breaking, and Building A CRM with Retool

 I like no- or low-code solutions to things. I've often wanted to simply push a button or move some GUI around and have the code implement itself.  I've thought about building something that's like a customer relationship management (CRM) system for keeping up with my network better than my little spreadsheet where I click links and then go like something. The general idea in this CRM Development is:  To have a GUI to add people to a NRM (Network Relationship Management).       Attach it to a database (MySQL is what I went with eventually using Amazon Relational Database service, but you can use PostGRES, and probably others).     Make sure components are connected to each other in the retool interface. This video is a good start. Watching the tutorial video, heard some SQL commands and went 'Oh no 😳" before going "Wait I know basic SQL", which is good, because you'll see.  When you get set up, there's a plethora of resources you can use -- Incl
Post a Comment
Read more