55cebf0622
* - Updated K8s version to current default - Updated region list to include all current regions - Updated SKU families to include latest v5 and remove oldest v2 - Updated generate-vm-sku-list.sh logic to pick correct storage parameter for ephemeral storage * - Updated default system and user node SKU to use Standard_D4ds_v5 - Updated cost optimised clusters to use Standard_B4s_v2, and performance clusters to Standard_D8ds_v4 - Updated workflows to use current gen VM SKUs Standard_D4ds_v5 * - Changed default node pool names to "agentpool" and "userpool01" to align more closely with the Portal * - Changed default OS disk size to 128 GB (to match portal behaviour) * - Updated default Kubernetes versions in main.bicep and other JSON config files * Adding userpool and agentpool to spell expections * Reverting managedClusters API version * Updated aksOutboundTrafficType from natGateway to managedNatGateway to try and address build issues * Updated aksOutboundTrafficType to loadBalancer to try and address build issues * Changed managedClusters API version to 2023-11-01 * Changed 'natGateway' to 'managedNatGateway' to align with current examples * Changed 'natGateway' to 'managedNATGateway' to align with current API spec * Updated another reference to natGateway Updated workflow to use in-branch version of AksDeploy-Basic.parameters.json isntead of hosted version (which won't be up-to-date with any changes in current branch) * Reverting to 0.10.4 as reverting to API version 2023-11-01 hasn't taken effect as this is pulled from the latest published release rather than in-branch * Enclosing `natGatewayProfile` in `networkProfile` key * Pointing workflow at local parameter file to reflect changes in local branch * Pointing workflow at local parameter file to reflect changes in local branch * Pointing workflow at local parameter file to reflect changes in local branch * Pointing workflow at local parameter file to reflect changes in local branch * Temporarily pointing to this working branch for testing * Reverting to 0.10.5 as 0.10.4 contains a parameter thats been removed from the API * Reverting ParamFile to the file on main branch. This will cause builds to fail until changes in this PR get published. * - Added branch variable to allow workflows to build off current branch for PRs - Reverted AKS API version to 2024-01-01 * - Added branch variable to allow workflows to build off current branch for PRs * - Added branch variable to allow workflows to build off current branch for PRs * - Reverting change from natGateway to managedNATGateway, back to natGateway * - Reverting change from natGateway to managedNATGateway, back to natGateway * - Trying to fix the error about the natGatewayProfile: `unknown field \\\"natGatewayProfile\\\" Check that the field is in the right location, is spelled correctly, and is supported in the API version` * Enclosing `natGatewayProfile` in `networkProfile` key * - Commenting out problematic code for testing * - Changed default outbound type to loadBalancer for pipeline tests - Reverting previous changes to `managedNATGatewayProfile` JSON snippets |
||
|---|---|---|
| .. | ||
| deploy-stages | ||
| flux | ||
| peered-vnet | ||
| shared-acr | ||
| terraform | ||
| windows | ||
| README.md | ||
| SampleAppMain.bicep | ||
| SampleAppMain.json | ||
| SystemPresetExample.bicep | ||
| SystemPresetExample.json | ||
| deployToRegistry.ps1 | ||
| networkforbyo.bicep | ||
| networkforbyo.json | ||
| shortLocationNames.json | ||
README.md
Samples
These samples demonstrate relevant Bicep patterns and show how to best consume the bicep modules from this project in your own deployments.
| Filename | Description | Deploy |
|---|---|---|
| SampleAppMain.bicep | When consuming the AKS Construction Bicep as a module, doing so from your own Bicep file is recommended. This sample shows using environment mapping, custom naming and basic conditional logic for using the module. |
|
| SystemPresetExample.bicep | The AKS Construction Bicep uses preset configurations for the system pool. Where you wish to deviate from these recommended presets, you can provide your own custom preset. This sample shows how to achieve that. | |
| Multi-Cluster with Peered vNets | When more control is required on the Networking and Resource Groups, you can deploy at the subscription scope. | |
| Shared ACR | Where an existing Azure Container Registry exists in a different resource group, this sample shows how to create the scoped 'ACR Pull' role assignment that the AKS cluster requires. | |
| NetworkForByo.bicep | When using the BYO network configuration you'll usually be deploying to a subscription with a peered virtual network already deployed with the correct subnets. This bicep file bridges the gap where you don't yet have that virtual network, but want to BYO network. | |
| Deployment Stages | Creating a staged deployment with an existing Managed Identity, Network Subnet and ACR, this configuration demonstrates how to pass the BYO Identity into AKS-Construction for Azure Subscriptions with restricted RBAC. |