DevOps

This morning I had some fun writing a Go program which takes the latest blog post from my RSS feed and posts it to Mastodon. It is based on my twitter cli I wrote a while ago. It was fun to write some Go again, it has been far too long. I’ve been writing mostly Terraform and yaml recently and working a lot with infrastructure. I haven’t been doing any projects at home that required programming. But recently I started up my personal blog and completely re-architected my social media setup. ...

In this video, I will walk you through the following steps: Set up a repo in Azure DevOps with MkDocs files Set up a Static Web App in Azure portal and link it to the repo Configure the Azure DevOps pipeline for MkDocs deployment Configure a custom theme for the website Demonstrate the pull request workflow for updating the docs By the end of this video, you will have a fully functional MkDocs site hosted on Azure Static Web Apps. You will also learn how to use Azure DevOps and Static Web Apps to collaborate on your documentation projects. ...

In the Azure portal you can’t select multiple resource groups for deletion. I have a sponsored subscription to play around in which I sometimes wish to clean completely. I wrote this script to delete all resource groups using bash. #!/bin/bash # script to delete all resource groups in a subscription using Azure CLI # get the current subscription name to confirm subscription=$(az account show --query name -o tsv) echo "Use this script with caution!" echo "You are about to delete all resource groups in the subscription: $subscription" # prompt for confirmation read -p "Are you sure? (y/n) " will_delete if [[ $will_delete == [Yy]* ]]; then echo "Deleting resource groups..." groups=$(az group list --query "[].name" -o tsv) # Loop through each group name and delete it for group in $groups; do az group delete --name "$group" --yes --no-wait done echo "All resource groups have been deleted." exit 0 fi echo "Exiting without deleting any resource groups." echo "Probably wise." Links: 202307081507 ...

As a DevOps Engineer or Cloud Native Engineer, I think it’s important to specialize in one cloud provider in the beginning of your career. Specializing allows you to gain deep knowledge and expertise in the specific tools and services related to that cloud provider, making you a valuable asset to any company using that provider. Although cloud computing is similar in essence no matter which provider you choose, each cloud provider has its own vocabulary and way of structuring things. ...

Finish deploying keyvault using pipeline Get the random name generation to work Lessons Learned Subscriptions need to be registered with resource providers, apparently https://learn.microsoft.com/en-us/azure/azure-resource-manager/troubleshooting/error-register-resource-provider?tabs=azure-cli acccesPolicies are mandatory on KeyVaults, but not when RBAC is enabled Assign contributor role to Azure DevOps service connection to be able to create resource groups from pipeline Achieved Setting up connection between pipeline and Azure subscription Assign correct rights to the service connection so it is allowed to deploy new resource groups (and other resources) Learned about provider registrations Made progress on creating unique names for resources Successfully deployed new resource group and key vault from the pipeline Next time: Look into random string creation with utcNow ...

Write KeyVault template Write pipeline code set up Azure DevOps pipeline Lessons Learned Always make sure to use az deployment group instead of az group deployment Because it has older Bicep version and will be deprecated Make sure to be in correct Directory to be able to sync subscriptions for service connection Links: 202306302206 ...

CNI? CNI stands for Container Network Interface. It allows communication between pods and services. Current Azure CNI limitations Let’s take a practical example. We have an enterprise environment where a large network is utilized, spanning multiple clouds and on-prem infrastructure hubs. To enable seamless communication across these sections, they must belong to the same network. As a result, specific IP address ranges are assigned to each section, with AWS, On-Prem A, and Azure each having their respective ranges. ...

Not sure how this will play out with more complex applications, but I can definitely see how this would accellerate the process for developers to get their first versions deployed without the toil of setting up manifests and pipelines. Will definitely play around with this soon and I’m curious to see how far Microsoft will take this! Links: 202306092006 ...

Next winter I’ll be entering my third year as a DevOps Engineer. When you first break into this field there is an overwhelming amount of things to learn. Frankly, this will always be the case. But I’m reaching a point where I have gained experience with most of the main areas and tooling, and I can start seeing the relations between them and how they compare to one another. Just like any other job or activity, there are things that you like and that suit you well, and there are things that you don’t like. And now the first phases of overwhelm are confidently behind me, I’m starting to learn the things I prefer doing over others. ...

I found an excellent video by Rob Muhlenstein explaining the differences between Cloud, Cloud Native and DevOps. Here are the notes I wrote. Cloud These are primarily cloud services. The external cloud. “Something as a Service”. Amazon Azure GCP Cloud Native This is Cloud Native: The CNCF Landscape Cloud Native is the technology that makes the cloud possible, and all the technology dependent on those services. Computing Edge Computing High Performance Computing ...