We install the Dapr extension in our managed AKS cluster with az k8s-extension. From Dapr version 1.12 this requires 2 new container images coming from linuxgeneva-microsoft.azurecr.io container registry regarding observability. As my company has a policy implemented to allow only images coming from a private container registry and mcr.microsoft.com, it does not allow these container images (mdm and amacoreagent) to be pulled.
My proposed solution is that these container images are pulled from mcr.microsoft.com when deploying by using Azure CLI or bicep, just like how the other dapr container images are pulled from container registry.
We install the Dapr extension in our managed AKS cluster with az k8s-extension. From Dapr version 1.12 this requires 2 new container images coming from linuxgeneva-microsoft.azurecr.io container registry regarding observability. As my company has a policy implemented to allow only images coming from a private container registry and mcr.microsoft.com, it does not allow these container images (mdm and amacoreagent) to be pulled.
My proposed solution is that these container images are pulled from mcr.microsoft.com when deploying by using Azure CLI or bicep, just like how the other dapr container images are pulled from container registry.