Skip to main content

Docker & Kubernetes Part 1

Containerization is taking over the world, and we owe it all to LXC... oops, I mean Docker (heh heh heh). Anyways, moving on. With the Docker Engine comes the ability to create containers. Containers are processes (not VM’s) running to spin up your application in a bite-sized environment (still not a VM). With containers, they allow you to use a host(s) to spin up and manage multiple applications (have I mentioned they are not VM’s?). As you have may heard, Docker/containerization is not a virtualization platform. Containers are more processes/images then they are actual hosts. Docker is the engine and what allows you to spin up your environment. Containers are thee environment. Now, this is all fine and dand, but how about if you want multiple environments? 10 of your application running? Or 50? That’s where K8 (Kubernetes) comes in. Today, we will be installing both for Mac.  The first thing you want to do is visit the Docker Community site. There are two forms of Docker. Community edition and enterprise edition. Community edition is just fine for what we’re doing. Head over to this site and create a free account. Once you’re down, come on back to this post:

Once you sign in, you will see a download button.
Once you sign in, you will see a download button.

Once you click that, you will see a DMG downloading.

Once that is complete, open up that bad boy and work out your index finger by clicking next a bunch of tines. The, you will get a cute mascott on your top taskbar called the Docker Whale 🙂

Then, you’ll want to go ahead and open up Docker. You will see several options, but you want to click Preferences. Then head over to the Kubernetes section and enable Kubernetes.

That’s it! Crazy, right? On Part 2 we will be running Kubernetes and seeing it go up and spin up multiple environments.


Popular posts from this blog

So, you want to be a Cloud Engineer?

In 2019 one of the biggest pieces of tech is the cloud. Whether it be public cloud or private cloud, cloud technologies are here to stay (for now). I predict that Cloud Engineering will be a very big part of IT (and development) for another 5-10 years. Today I want to share with you my journey in becoming a Cloud Engineer and some helpful tips. A career timeline to be a Cloud Engineer can go like so;

Desktop Support > Junior Sysadmin > Sysadmin > Sysadmin/Technical Lead > Engineer >  Cloud Engineer.

Although our career paths may not align, I believe that this progression is very import. Let me tell you why.

Helpdesk/Desktop Support Helpdesk and desktop support get your feet wet. It allows you to understand technology and how it's used in the workplace from a business perspective. It shows you what technologies may be best in the current environment your in and how to support those technologies. It also teaches you soft skills and how to support people from a technic…

Monitoring your containers in an AKS cluster with Prometheus

Monitoring and alerting is arguably one of the most important thing in Cloud Engineering and DevOps. It's the difference between your clients stack being up and a client being down. Most of us have SLA's to abide by (for good reason). Today we're going to learn how to spin up Prometheus in an AKS cluster to monitor our applications.

1. Intermediate knowledge of Kubernetes
2. An AKS cluster spun up in Azure

Recently AKS supports Prometheus via Helm, so we'll use that for an automated solution to spin this up. This installs kube-prometheus, which is a containerized version of the application. With raw Prometheus, there are a few things that are needed for the operator;

1. Prometheus: Defines a desired deployment.
2. ServiceMonitor: Specifies how groups of services should be monitored
3. Alertmanager: Defines the operator to ensure services and deployments are running by matching the resource

With kube-prometheus, it is all packaged for you. This means configuri…

Spinning up a Kubernetes cluster with Kubeadm

In today's world, we have several public cloud technologies that will ultimately help us with spinning up these infrastructures. This however comes with a price. Because a public cloud provider (like AWS or Azure) handles the API/master server and networking, you'll get something up quick, but miss some key lessons of spinning up a Kubernetes cluster. Today, I'll help you with that.

There are some pre-reqs for this blog:
1. At least 3 VM's. In my case, I'm using my ESXi 6.7 server at home.
2. Basic knowledge/understanding of what Kubernetes is utilized for.
3. Windows, Mac, or Linux desktop. For this blog, I am using Windows 10.

The first thing you want to do is spin up three virtual machines running Ubuntu18.04. You can use a RHEL based system, but the commands I show and run (including the repos I'm using) will be different.

I have already set up my 3 virtual machines. I gave them static IP addresses as I have found API/configuration issues if the VM shuts do…