1cb427e27b
* Create aspnetapp.yml * removing push trigger * removing windows 2019 as an option Signed-off-by: Gordonby <gordon.byers@microsoft.com> * stopping kubenet + windows Signed-off-by: Gordonby <gordon.byers@microsoft.com> * more windows guidance Signed-off-by: Gordonby <gordon.byers@microsoft.com> * error message tidying Signed-off-by: Gordonby <gordon.byers@microsoft.com> * typo Signed-off-by: Gordonby <gordon.byers@microsoft.com> * margin --------- Signed-off-by: Gordonby <gordon.byers@microsoft.com> |
||
|---|---|---|
| .. | ||
| README.md | ||
| main.bicep | ||
| winNodePools.png | ||
| winResourcesDeployed.png | ||
README.md
Windows node pool example
This sample showcases using the AKS Construction bicep code for creating an AKS cluster with a Windows node pool.
A common configuration for Windows AKS Clusters is to use 3 nodepools. The Helper supports configuration for 2 nodepools, so we'll supplement the creation with an extra nodepool called from a parent bicep file.
- Creating Virtual Networks prior to AKS Cluster creation
- Creating an AKS Cluster with a linux system pool and a linux user nodepool (for ancilliary components like ingress controller)
- Extending the AKS config by creating additional autoscaling Windows node pools post creation
Deploying the sample
az group create -n win-demo -l northeurope
az deployment group create -n win-demo -g win-demo -f ./samples/windows/main.bicep
Inspecting the deployed resources
Inspecting the created node pools
