This week I hosted my first ever on-line hands-on workshop under my Infrastructure as Code user group. It was 12 participants, 4 hours of pure hands-on, awesome participants and a lot of ARM templates.
As part of the preparation for the workshop, I spend quite a lot of time structuring and working with the content of the labs. The goal was that each lab is well documented, self-explained and contains all information needed to complete it, including useful and relative links. This way I tried to minimize the amount of potential questions during the workshop. And it looks like it worked really well. There were almost no questions related to the lab itself. People understood what they expected to do.
So, if you want to learn some basics about how to work with ARM templates, how to use ARM Tools plugin for VS Code, how to use variables and parameters and finally how to use parameters file for multiple environments, try to work with these 11 labs.
Here is the list of prerequisites you need to have before you start.
You can also check out my previous Infrastructure As Code workshops:
- Working with Azure Network Watcher
- Working with Azure Private Links
- Automate DNS and Certificate management on Azure with Azure DevOps
- Load-Balancing Options on Azure
- Automate Azure workload provisioning with Bicep, Powershell and Azure DevOps
- How to live in harmony with ARM templates
- Implement immutable infrastructure on Azure with ARM templates
- Implement immutable infrastructure with Pulumi: Part I
- Implement immutable infrastructure with Pulumi: Part II
- Immutable AKS infrastructure with Bicep
and Azure Kubernetes Services (AKS) workshops:
- AKS Workshop #1 - Introduction to Azure Kubernetes Service (AKS)
- AKS Workshop #2 - Advanced AKS configuration
- AKS Workshop #3 - Immutable AKS infrastructure with Bicep
- AKS Workshop #4 - GitOps in AKS with Flux
- AKS Workshop #5 - scaling options for applications and clusters in AKS
- AKS Workshop #6 - Monitoring options in AKS
If you have any issues/comments/suggestions related to the labs, you can reach out to me at evgeny.borzenin@gmail.com.
With that - thanks for reading!