Posts

In today’s post, we will look at an interesting challenge, having GitHub actions interact with Azure PaaS services for which we have disabled public access.

If you have been following along in this series, so far we have configured the master node and added a few worker nodes to the cluster.

In the first article of this mini-series, we configured the master node and kubectl on our PC, now it’s time to configure the worker nodes and join them to the cluster, here’s the final state with my hostnames and IPs:

Motivation # I recently bought a few Raspberry PI 5 SBCs to play around with Kubernetes at home and, without noticing, I started spending a lot of my free time with it.

It’s common to evolve HTTP APIs, and while it’s very easy to expose new and improved versions of a given functionality, not so much to safely obsolete and eventually remove an API.

If you’re working with the Microsoft identity platform, you’re probably familiar with the concept of application Scopes or Roles.

I recently passed the AZ-104 certification exam, making it the third Microsoft certification under my belt so far.

OpenID Connect (OIDC) integration between Azure Active Directory and GitHub allows your GitHub Actions workflows to securely access resources in Azure, without needing to store the Azure credentials in the GitHub action secrets.

This post describes my journey to import several hundred Azure resources in Terraform.

Source code