Skip to main content

Setting up your cloud engineering Linux desktop environment

As technology professionals, we spend a TON of time in front of our computers. To be battle-station-ready, we need to have the right tools for the right job.

The first thing is the OS. For my Linux desktop, I like to use Elementary. It's an aptitude-based distro with a Mac-like feel. It's fast, steady, and I haven't had many problems. Remember to keep it up to date however. A cron job at every boot to run apt-update -y will do the trick.

The next thing is your code-editor. A lot of distros come with one, but I prefer VSCode. VSCode has very quickly become a top-tier editor. The amazing amount of extensions alone makes it the top, if not, very close to the top. My top extensions are;

1. PowerShell
2. Python
3. Docker
4. Kubernetes

Since I work on both Azure and AWS, I need PowerShell to manage Azure. For this, PowerShell Core is the way. Below is instructions depending on your distro.

The next thing we need to test on our cloud environments is the cloud's CLI and API. Working on both AWS and Azure, we'll need awscli and az (az is Azure's CLI). Along with this, PowerShell can import az and you'll have cmdlets at your disposal.

I'll need to be able to test some micro services and containers. For this, we'll definitely need Docker. We won't run production-level workloads from our Linux desktop, but we'll need to have the ability to test containers on the fly.

Now that we have Docker installed, we need some Kubectl. Kubectl from your Linux terminal will allow you to run your Kubernetes config locally so you can connect to your orchestration system6.

The final thing, as in most desktops, we need a good web browser. I prefer Chrome.


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.

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…

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…