Assigned PublicIP is returning "The server is taking too long to respond."

[jtmerch]

Problem encountered on https://dotnet.microsoft.com/learn/aspnet/deploy-microservice-tutorial/deploy
Operating System: windows

Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

Hello, I went through the weatherforecast tutorial found on your Deploy a .Net Microservice page. I do the "kubectl get service mymicroservice --watch" command as instructed and I get back the Public IP address. the issue is that when I try to connect that Public IP I always get a timeout saying "The server is taking too long to respond." I have tried this twice and keep running into the same problem when I deploy my project. It is the standard WeatherForecast demo project, so it is not a complex solution at all. Any idea of why my publicIP would keep returning that?

UPDATE: Also, as an update my deploy PODS have status "Waiting" with a reason of "ImagePullBackOff"

Thanks for any help.

[jozkee]

cc @Pilchie

[Pilchie]

@davidfowl @shirhatti - any ideas here?

[mairaw]

Tagging @shirhatti and @nishanil for help here

[shirhatti]

Also, as an update my deploy PODS have status "Waiting" with a reason of "ImagePullBackOff"

Try looking at the output of kubectl describe pod <pod-id>. My naïve guess is you have an auth issue where your cluster doesn't have access to your registry.

[jtmerch]

Thanks, I went thru the steps of adding my registry ID when I created the cluster (jn Powershell). What other steps would I need to take to ensure that my cluater has access? Joe

…

On Mon, Apr 5, 2021, 6:12 PM Sourabh Shirhatti ***@***.***> wrote: Also, as an update my deploy PODS have status "Waiting" with a reason of "ImagePullBackOff" Try looking at the output of kubectl describe pod <pod-id>. My naïve guess is you have an auth issue where your cluster doesn't have access to your registry. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6121 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFBOCDVOVCD6FREQENWGGEDTHIYVLANCNFSM42L2ILUA> .

[shirhatti]

Assuming it is an auth issue, try this- https://docs.microsoft.com/en-us/azure/aks/cluster-container-registry-integration#configure-acr-integration-for-existing-aks-clusters

I would recommend running kubectl describe pod <pod-id> first to ascertain if that's really the issue here

[jtmerch]

Thanks shirhatti. I followed all the steps in the provided link (everything but a used my dockerhub repository that was already created). And I still get the same error:

NAME READY STATUS RESTARTS AGE
microservicedemo-deploy-55f6bcdf77-4xxd9 0/1 ImagePullBackOff 0 55s

[mairaw]

Any other suggestions @shirhatti?