Posts

In this article, I’m going to show you how to build an Azure Kubernetes Service lab environment with Bicep. This sample was inspired by this AKS Lab provided by the AKS team! [!NOTE] If you want to see a live demo of this instead, check it out on my YouTube channel! We’re going to build the lab environment step by step using Bicep. Wherever possible, we will avoid creating resources using the AZ CLI, and instead take an opinionated approach to defining our infrastructure declaratively with Bicep instead. We will still need to use the AZ CLI to do some tasks, such as deploying our resources. ...

In order to control traffic flow within our Azure virtual networks, we can use custom routes, and configure the routes to direct traffic through a network virtual appliance. Azure automatically creates a route table for each subnet in our virtual networks, and adds system default routes to the table. We can override these default routes with custom routes and more custom routes to route tables. In this article, we’ll learn how routing in Azure works, how we can use custom routes to override the default routes, before implementing an example of custom routing using Bicep. ...

In distributed Azure architectures, it’s necessary to split up your virtual network infrastructure into different parts. This may happen over different Azure regions, or different subscriptions. Even in networks that are distributed, we’ll need a mechanism to communicate between these different networks. For this, we can use virtual network peering. Virtual network peering enables us to connect two or more virtual networks in Azure, whether they are in the same Azure region or not. The traffic between peered virtual networks is private, and they appear as one for connectivity purposes. Traffic between virtual machines in peered networks uses the Microsoft backbone infrastructure. ...

To facilitate communication between resources in Azure deployed in virtual networks, we can use domain name resolution over relying on IP address, making the communication process simpler. In Azure, DNS is split into two areas: Public DNS, and Private DNS. Domain Name System, otherwise known as DNS, is responsible for resolving a service name to an IP address. Azure DNS provides DNS hosting, resolution, and load balancing for your Azure applications. In this article, I’ll talk about the differences between Public DNS Domains and how we can delegate DNS domains. Then i’ll talk about how Private DNS works in Azure, and how we can set up Private DNS Zones in Azure. ...

Azure Virtual Networks use private IP addresses which aren’t routable on public networks. To enable support networks that exist both in Azure and on-prem environments, we need to configure IP addressing for both networks. Public IP addresses allow resources on the internet to communicate with Azure, and also enable outbound communication for Azure resources to public-facing services on the internet. In Azure, we can create public IP addresses and assign them to specific resources. ...