This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
This is a blog on how to use a modular approach for Infrastructure as Code (IaC) in provisioning a private AKS cluster and other related resources. The Bicep modules in the repository are designed keeping the AKS baseline architecture in mind. You can start using these modules as is or modify to suit your own needs.
The Bicep modules will provision the following Azure Resources under subscription scope:
- A Resource Group with Baseline variables
- Hub VNet with required subnets
- Azure Firewall Subnet
- Azure Bastion Subnet
- A jumpbox subnet
- Spoke VNET with AKS cluster subnet and additional subnet for other services like Azure Container Registry etc.
- Azure Firewall and required routes
- Azure Bastion resource and a jumpbox VM without public IP for securing traffic
- Azure Container Registry for storing images.
- A Private Endpoint for ACR
- Private DNS Zone
- AAD Enabled, Managed Private AKS Cluster with monitoring Addon and Azure Policy enabled
- Private AK Cluster need the UDR routes enabled via Firewall.
Clone the repo
git clone https://github.com/ssarwa/bicep cd bicep # You could use deploy.azcli as your working file. Don't run the script as is!
Login to Azure
az login az account set -s <Subscription ID>
# Change the variables as required (baseline and location) on deploy.azcli # Deploy the bicep script az deployment sub create -n $baseline'Dep' -l $location -f main.bicep
The deployment could take somewhere around 20 to 30 mins. Once provisioning is completed you can use the cluster for your needs.
- Enable GitOps using Flux operator for Application deployment
- Enable IaC using CI/CD pipelines on Github Actions