AKS hosted apps return ERR_CONNECTION_TIMED_OUT

Eden_Reen 0 Reputation points
2024-01-05T08:34:49.8766667+00:00

Hello,

After a migration to 1.25, which who succeeded. All applications hosted on this cluster return an "ERR_CONNECTION_TIMED_OUT" error. Yet I haven't changed anything making the Kubernetes upgrade. I've tried deleting namespaces, deployments, services and ingress but nothing changes. An application gateway is used, the endpoints seem to point to the right place.

Have you had this type of problem before? Do you have any idea of a solution or where I should look, please?

Azure Kubernetes Service
Azure Kubernetes Service
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
2,447 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Rohit Kumar Sinha 1,336 Reputation points
    2024-01-05T08:59:02.8+00:00

    HI Eden ,

    Is the URL hosted on Application Gateway or Frontdoor? you can refer to the below article to check the relevant scenerio for your configuration and try the steps mentioned.

    https://learn.microsoft.com/en-us/troubleshoot/azure/azure-kubernetes/connection-issues-application-hosted-aks-cluster

    Please Accept as answer if the reply is helpful

    0 comments No comments

  2. Anveshreddy Nimmala 3,550 Reputation points Microsoft External Staff Moderator
    2024-01-08T04:05:16.2433333+00:00

    Hello Eden_Reen ,

    welcome to microsoft Q&A, Thankyou for posting for your Query here.

    Based on the error message you are seeing, "ERR_CONNECTION_TIMED_OUT", it is possible that the issue is related to network connectivity.

    Check if the Kubernetes API server is accessible by running kubectl command in the cluster.

    If you are able to connect to the API server, then the issue may not be related to Kubernetes itself.

    Check if the application gateway is configured correctly. Make sure that the endpoints are pointing to the right place and that the gateway is properly configured to route traffic to your Kubernetes cluster.

    Check if there are any firewall rules or network security groups that may be blocking traffic to your Kubernetes cluster.

    Check if there are any issues with your nodes or pods. You can use kubectl get nodes and kubectl get pods to check the status of your nodes and pods.

    Hope this helps you. please accept the answer if it helps you .


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.