Skip to main content

Hold Everything! It's time for Kubernetes Tutorial 1

(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.




With a tutorial right on the very website! Always love it when people make it easy to learn their product.

WHAT is a Kubernetes Cluster?
 It’s a group of computers intended to work as a single unit.

(Reminds me of a bot net).

Abstractions in the software let you send containerized (packaged enviroments) applications to a cluster and not tie them to specific machines.


The cluster has two things.

Master - Coordinates it, ‘it’ being app scheduling and maintaining the right state, updates, and scaling applications.

Nodes - The bits that run the applications.
They (and the end user) talk to the master using the Kubernetes API that the master exposes.

Nodes have something called a KUBELET which talks to the Master and manages the node.

Does the Kubelet talk with the API? Or is it the API?

Deploying apps with Kubernetes tells the Master to start the app containers, and the Master schedule containers to run on the notes

There’s also MINIKUBE that makes a VM on your machine and makes a cluster with only one node.

And we can install it on Mac! So let’s do it!

Thanks Vitalflux!
https://vitalflux.com/install-kubernetes-mac-os-x/

This is my first time working with Mac terminal, and it looks pretty similar to Linux/Ubuntu, except it’s a bit easier to read.


I’m fonder of black on white.

First we install Homebrew and we have version 1.7.0.

The page recommends we download Hyperkit over Xyve Driver.

There’s an important note;
* opam config env must be evaluated each time prior to building hyperkit so the build will find the ocaml environment.





Now you’re kubing with power!

With the start command, the terminal says ‘Downloading Minikube ISO’. Who knew that was a possibility, eh? Technology is amazing.

While it’s loading, let’s use the on-site tutorial.

It mentions something called kubectl, which will come later, but we can see if it’s installed or not;


I’ll take it as a yes.

kubectl is the client version and the server version is Kubernetes on the Master.

What’s going on with the cluster?


I don’t think there’s anything, but minikube is ready to roll, and that concludes our first tutorial!
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

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.
Post a Comment
Read more