Open vlardn opened 1 year ago
Guys, no any response for 7 months now :(
Guys, no any response for 9 months now :)
I've reproduced this. While a proper fix is worked on, you can unblock yourself by setting dapr_monitoring.enabled
to false.
// Dapr monitoring is not supported on ARM VMs due to the mdm container not being ARM64 compatible.
// Removing this once that bug is fixed. https://github.com/Azure/AKS/issues/3992
var daprMonitoringEnabled = contains(systemVmType, 'p') ? 'false' : 'true'
resource dapr 'Microsoft.KubernetesConfiguration/extensions@2023-05-01' = {
scope: aksCluster
name: 'dapr'
properties: {
extensionType: 'Microsoft.Dapr'
version: '1.14.4-msft.5'
autoUpgradeMinorVersion: false // We need to pin the version to avoid breaking changes
releaseTrain: 'stable'
scope: {
cluster: {
releaseNamespace: 'dapr-system'
}
}
configurationSettings: {
'global.nodeSelector.agentpool': 'systempool'
'dapr_monitoring.enabled': daprMonitoringEnabled
}
}
}
Dapr extension for AKS can't install latest Dapr on Arm-based node
Standard_D2pds_v5
due to the error in Dapr monitoring pod "mdm" container:exec /start_metricsextension.sh: exec format error
It looks like that 'mdm' docker container (
linuxgeneva-microsoft.azurecr.io/genevamdm:2.2023.928.2134-0de476-20230928t2244
in this case) was not built forlinux/arm64
platform.Steps to Reproduce:
PS. Dapr installation via AKS extension succeeds on similar
Standard_D2ads_v5
node but with AMD CPU (as the "mdm" container is not failing there):Environment: