[AVM Module Issue]: Deployment is failing while using the managed cluster

[Bayanapurnima]

Check for previous/existing GitHub issues

• I have checked for previous/existing GitHub issues

Issue Type?

I'm not sure

Module Name

avm/res/container-service/managed-cluster

(Optional) Module Version

0.8.0

Description

I you have created this AKS cluster “aks-weu-prd” with Azure Verified Modules(br/public:avm/res/container-service/managed-cluster:0.1.7). However when I tried to upgrade the version(0.8.0) of the cluster it has failed with this error “Deployment template parse failed: 'Required property 'type' expects a value but got null”
The template we followed is:
//AKS with Azure Network
module managedCluster 'br/public:avm/res/container-service/managed-cluster:0.8.0' = {
scope: cmdsResourceGroup
name: 'aks-${deploymentSuffix}'
params: {
// Required parameters
name: 'aks-${resourceSuffix}'
primaryAgentPoolProfiles: [
{
availabilityZones: [
3
]
count: 1
enableAutoScaling: true
maxCount: 3
maxPods: 30
minCount: 1
mode: 'System'
name: 'systempool'
nodeTaints: [
'CriticalAddonsOnly=true:NoSchedule'
]
osDiskSizeGB: 0
osType: 'Linux'
serviceCidr: ''
storageProfile: 'ManagedDisks'
type: 'VirtualMachineScaleSets'
vmSize: environment.cmdsSettings.aks.nodepools.systempoolSKU
vnetSubnetID: AKSSubnet
}
]
// Non-required parameters
agentPools: [
{
availabilityZones: [
1
3
]
count: 2
enableAutoScaling: true
maxCount: environment.cmdsSettings.aks.nodepools.maxInstancesUserpool4
maxPods: 40
minCount: environment.cmdsSettings.aks.nodepools.minInstancesUserpool4
minPods: 2
mode: 'User'
name: 'userpool4'
nodeLabels: {}
osDiskSizeGB: 0
osSKU: 'AzureLinux'
osType: 'Linux'
scaleSetEvictionPolicy: 'Delete'
scaleSetPriority: 'Regular'
type: 'VirtualMachineScaleSets'
vmSize: environment.cmdsSettings.aks.nodepools.userpool4SKU
vnetSubnetID: AKSSubnet
}
{
availabilityZones: [
2
]
count: 2
enableAutoScaling: true
maxCount: environment.cmdsSettings.aks.nodepools.maxInstancesUserpool2
maxPods: 40
minCount: environment.cmdsSettings.aks.nodepools.minInstancesUserpool2
minPods: 2
mode: 'User'
name: 'userpool2'
nodeLabels: {
app: 'clamav'
}
osDiskSizeGB: 128
osSKU: 'AzureLinux'
osType: 'Linux'
scaleSetEvictionPolicy: 'Delete'
scaleSetPriority: 'Regular'
type: 'VirtualMachineScaleSets'
vmSize: environment.cmdsSettings.aks.nodepools.userpool2SKU
vnetSubnetID: AKSSubnet
}
]
enableStorageProfileDiskCSIDriver: true
enableStorageProfileFileCSIDriver: true
enableStorageProfileSnapshotController: true
networkPlugin:'azure'
privateDNSZone: pdnszone_aks.id
enablePrivateCluster: true
enableKeyvaultSecretsProvider: true
enableSecretRotation: true
enableOidcIssuerProfile: true
disableRunCommand: true
omsAgentEnabled:true
monitoringWorkspaceResourceId:aiLogAnalyticsWorkspaceResourceId
openServiceMeshEnabled: false
autoUpgradeProfileUpgradeChannel: 'none'
kubernetesVersion: '1.29.7'
managedIdentities: {userAssignedResourcesIds:['${managedIdentityAks.outputs.resourceId}']}
tags: commonTags
}
}
In the above template I have provided the value for type as 'VirtualMachineScaleSets'
Given that we are working with a tight deadline of March 3rd, 2025, it is essential that we deploy it as soon as possible. Please consider this issue as priority and it would be helpful for us

(Optional) Correlation Id

No response

[microsoft-github-policy-service]

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

[avm-team-linter]

@Bayanapurnima, thanks for submitting this issue for the avm/res/container-service/managed-cluster module!

Important

A member of the @Azure/avm-res-containerservice-managedcluster-module-owners-bicep or @Azure/avm-res-containerservice-managedcluster-module-contributors-bicep team will review it soon!

[Bayanapurnima]

^{Purnima Bayana [email protected], Mercedes-Benz Research and Development India, Provider Information}](https://github.com/mercedes-benz/foss/blob/master/PROVIDER_INFORMATION.md)%3C/sup%3E)