Mário Abreu

It seems the culprit is having the spec: ingressClassName: azure-application-gateway If i use the annotation kubernetes.io/ingress.class: azure/application-gateway I can't reproduce the behavior.

On my environments on the latest release I also get **UNAUTHORIZED** even if the node identity already has AcrPull permission. This works on the version 2.2.2 but not on 2.5.0....

@leedavidr as far as i know using imagePullSecrets bypasses azure rbac and uses traditional authentication, that's why it works. On my setup using imagePullSecrets also works, but its not an...

UPDATE: it was azure_policy add-on that was preventing us from creating the pods. The UNAUTHORIZED pull error from ACR was misleading.

Not a specific policy but the addon itself. how to repro: Create a new cluster with the addon enabled Push the sample injector image to an ACR Push an nginx...

> > You should also see UNAUTHORIZED errors on kube events for the injector app and no pods running for this deployment; > > What is the sample injector app...

> Do you install the injector app in the same namespace with akv or a different namespace? azurekeyvaultsecret object needs to be on the same namespace than the app. Akv2k8s...

hi @dstrebel are there any plans for the AKS Office Hours to come back?