Skip to main content

Where have I been?

Hey everyone! I wanted to send a quick update as to why I haven't been posting much. I know I typically post more often but there is a reason I haven't... I got a new job! Yay :). The reason why I haven't been posting is because I've been focusing on getting up to speed with my new position, both at home (learning new technologies, practicing, etc.) and at work (learning the technology stack, how the applications work, dependencies, etc.).

So, what am I doing? As most of you know, I was a Cloud Engineer previously. Now I'm a DevOps Engineer. What has changed in my day-to-day?

First thing is CI/CD. I have been working with CI/CD much more in my new role. This has been an amazing experience and I'm glad I was able get up to speed quickly. My stack revolves around Azure DevOps which is pretty solid. You can do anything from spinning up Docker images to infrastructure to deploying your app.

Second thing is being back in Microsoft land. If you've followed me throughout my podcast and some blog post, you'll know that a big chunk of my career so far has been around Microsoft technologies. I then moved to primary Linux and AWS for a while. This was a complete 180 for me. Now I'm back in Microsoft land working heavily with Azure, PowerShell, ARM, and az cli. Microsoft has come a long way in the tooling for DevOps and Cloud Engineering from what I can see so far. It's certainly very interesting to see all of the open source love.

Third thing is, which I know I mentioned above, ARM Templates. ARM Templates are JSON configs for Infrastructure As Code and Configuration Management. It looks very similar to CloudFormation.

The fourth thing is being on a Windows machine vs Mac/Linux as I've been used to for a while. The primary tools I'd like to point out for anyone that is doing the transition is Windows Terminal, PowerShell Core, WSL, VSCode, and chocolatey. Windows Terminal is Microsoft's new terminal that allows you to have multiple tabs open and mixing those tabs with PowerShell, PowerShell Core, WSL distros, and command prompt. It makes SSH'ing much easier and has a terminal feel that all of us Linux folk are used to.

The fifth and final thing is going from 80-90% AWS to Azure. I was working with Azure previously, but my primary workloads were in AWS. I think Azure is great for a lot of things. One primary things is Resource Groups. I really love how you can bring all of your components (storage accounts, NICs, LB's, VM's, etc.) into one centralized location for management. Azure DevOps of course works very well with Azure (you can use it for other cloud platforms as well). Azure definitely has more of an enterprise feel vs the "open source development" feeling you get while in AWS. Using PowerShell and AZ CLI will certainly help for the command line folk out there.

So, what's next? As I'm working with multiple new technologies at the moment, I imagine my blogs will be more focused in those technologies. I will be keeping the focus in DevOps/Cloud Engineering as I have been.

Stay tuned and thanks for reading!


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…