Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 4m11s default-scheduler Successfully assigned ingress-basic/ingress-nginx-admission-create-ncwjj to aks-nodepool1-27424342-vmss000000
Normal Pulling 2m40s (x4 over 4m11s) kubelet Pulling image "acruseaksdv.azurecr.io/ingress-nginx/kube-webhook-certgen:v1.1.1"
Warning Failed 2m40s (x4 over 4m10s) kubelet Failed to pull image "acruseaksdv.azurecr.io/ingress-nginx/kube-webhook-certgen:v1.1.1": rpc error: code = Unknown desc = failed to pull and unpack image "acruseaksdv.azurecr.io/ingress-nginx/kube-webhook-certgen:v1.1.1": failed to resolve reference "acruseaksdv.azurecr.io/ingress-nginx/kube-webhook-certgen:v1.1.1": failed to authorize: failed to fetch anonymous token: unexpected status: 401 Unauthorized
Warning Failed 2m40s (x4 over 4m10s) kubelet Error: ErrImagePull
Warning Failed 2m25s (x6 over 4m9s) kubelet Error: ImagePullBackOff
Normal BackOff 2m11s (x7 over 4m9s) kubelet Back-off pulling image "acruseaksdv.azurecr.io/ingress-nginx/kube-webhook-certgen:v1.1.1"
How to fix this:-
To resolve this issue, you may want to check the following:
Ensure that the image reference is correct. Verify that the image is available in the specified registry, and that the reference is correct and up to date.
Check the authentication credentials. Ensure that the Kubernetes cluster has the correct credentials to access the Azure Container Registry. You may want to verify the Azure Service Principal credentials and permissions to access the registry.
Check the network connectivity. Verify that the Kubernetes cluster node can access the internet and the Azure Container Registry without any network restrictions.
Check the Kubernetes cluster configuration. Ensure that the Kubernetes cluster is configured correctly to access the Azure Container Registry. You may want to verify the Kubernetes secret and config map settings.
No comments:
Post a Comment