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: https://store.docker.com/editions/community/docker-ce-desktop-mac


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.

Comments

Popular posts from this blog

DevOps tooling in the Microsoft realm

When I really started to dive into automation and practicing DevOps with specific tooling, there were a few key players. At the time Microsoft was not one of them. They were just starting to embrace the open source world, including the art and practice of DevOps. Since then Microsoft has went all in and the tech giant has made some incredible tooling. Recently I switched to a Microsoft-heavy environment and I love it. I went from AWS/Python/Ansible/Jenkins to Azure/PowerShell/ARM/Azure DevOps. My first programming language was PowerShell so being back in the saddle allowed me to do a full circle between all of the different types of tooling in both worlds. Today I want to share some of that tooling with you.

The first thing I want to talk about is ARM. What is ARM? ARM is a configuration management tool that allows you to perform software-defined-infrastructure. Much like Ansible and Terraform, ARM allows you to define what you want your environment to look like at scale. With ARM, yo…

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.

Pre-reqs;
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…

Run PowerShell code with Ansible on a Windows Host

Ansible is one of the Configuration Manager kings in the game. With it's easy-to-understand syntax and even easier to use modules, Ansible is certainly a go-to when you're picking what Configuration Management you want to use for your organization. Your question may be "but Ansible is typically on Linux and what happens when I'm in a Windows environment?". Luckily I'm here to tell you that Ansible will still work! I was pleasantly surprised with how easy it is to use Ansible on Windows with a little WinRM magic. Let's get started.

Pre-requisites for this post:
1) WinRM set up to connect to your Windows host from Ansible
2) Ansible set up for Windows Remote Management
3) SSH access to the Ansible host
4) Proper firewall rules to allow WinRM (port 5985) access from your Ansible host to your Windows host
5) Hosts file set up in Ansible that has your IP or hostname of your Windows Server.
6) At least one Linux host running Ansible and one Windows Server host …