Azure container registry repository not accessible while Bursting from AKS to ACI with the Virtual Kubelet

2/20/2020

api call to https://management.azure.com/subscriptions/75b381e6-d739-4955-2-e7e7adc/resourceGroups/MC_xxxcoreapi_CoreCluster_westeurope/providers/Microsoft.ContainerInstance/containerGroups/xxx-coreapi-public-xxxcorejob1-vdjsb?api-version=2018-10-01: got HTTP response status code 400 error code "InaccessibleImage": The image ''xxxx.azurecr.io/core:v1.0.0.0'' in container group ''xxx-coreapi-public-xxx-vdjsb'' is not accessible

Use Case: Bursting from AKS to ACI with the Virtual Kubelet. I am able to pull it using docker pull, also I can pull image in AKS node with and without imagePullSecret, but not with the ones type: virtual-kubelet

Already tried the following:

Pull an Image from a Private Registry

CreateSecret
 imagePullSecrets:
   name: xxx-axth

Also use service account with secret. My AKS Service principal has contributor and acrpull roles

Furthermore I have tried:

az aks update -n CoreCluster -g xxxcoreapi --attach-acr xxxcoreapi"
-- aamir sajjad
azure
azure-aks
azure-container-instances
kubernetes

1 Answer

2/21/2020

So it is resolved finally

Strange enough, I log out to the azure portal, restart my pc, and everything working as expected.

As per my understanding possible causes are

  • Azure refresh cache thing

  • My computer cache refresh for related files/config

I hope that my experience will help somebody with similar situation

-- aamir sajjad
Source: StackOverflow