Public IP not reachable and connection timeout

Baptiste Pattyn 11 Reputation points
2020-10-12T06:46:18.047+00:00

We are using a new AKS cluster with only one deployment. That deployment runs only one pod and exposes a .NET core 3.1 application that uses two ports: one for public access and one for private access. To access the public port I created service of type loadbalancer that exposes the public port. After doing this I can see that a public IP is assigned to the service when I do kubectl get services but when I try to reach the IP of the service by entering it in a browser or by using it within POSTMAN to execute a get request I cannot connect and the site is not reachable.

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
{count} votes

3 answers

Sort by: Most helpful
  1. KarishmaTiwari-MSFT 20,772 Reputation points Microsoft Employee Moderator
    2020-10-15T02:33:36.58+00:00

    To narrow down the cause, you can start with confirming whether the service is accessible from:

    -Pod IP
    -ClusterIP of the service, inside the cluster
    -and then test the load balancer.

    You can also test the connectivity from a curl command ideally from a host machine inside the same vnet where the AKS is created.
    For example, "curl EXTERNAL-IP:8080"

    They you would need to look at allowing traffic access from the internet in the NSG applied to the vnet/subnet for aks.

    Let me know your observations and I can help troubleshoot further.


  2. Adnan Kamili 1 Reputation point
    2021-03-02T06:10:53.71+00:00

    We had a similar issue which happened after we re-installled the ingress which changed the external IP address. When this happens the old IP address still remains in the kube-proxy somehow.

    So, deleting the kube-proxy pods on all the nodes restarted the kube-proxy and our issue was resolved.

    0 comments No comments

  3. Amit Kumar Singh 0 Reputation points
    2023-08-29T10:58:13.0033333+00:00

    I have Kubernetes configured with nginx controller .

    I can access my services by logging onto pod container and doing curl for ingress controller IP address.

    So all works fine as expected from inside the AKS subnet.

    However, I am not able to access same from IP Address of ingress controller from browser.

    Looks like traffic is getting blocked and not reaching public ip address of ingress.

    NSG is open for AKS subnet. Anything else which we can check.

    0 comments No comments

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.