Azure support team not responding for ticket regarding AKS Nodes

zenith 1 Reputation point
2022-06-13T12:19:51.567+00:00

Azure Support Team has not yet responded to the ticket opened on 8th June, even with Premier Support.
Case ID: 2206080050001824,
AKS Nodes are in Not Ready State for more than a week.

Can someone from Azure Support team look into this case.

Azure Kubernetes Service (AKS)
Azure Kubernetes Service (AKS)
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
1,886 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Prrudram-MSFT 22,486 Reputation points
    2022-06-13T16:19:04.347+00:00

    Hello @zenith ,

    Support has reviewed the cluster resources and observed that the tunnel has been disconnected which connects the control plane & worker plane.

    Solution Suggested:
    Can you try deleting the tunnel front pods in the kube-system namespace from the cluster, they will be re-created again. Please ensure that the pod is running, and the node is healthy and that all the required ports are open, the list can be found here: Restrict egress traffic in Azure Kubernetes Service (AKS) - Azure Kubernetes Service | Microsoft Learn

    If restarting/deleting tunnelfront pod is not working, ssh to the agent node which running the tunnelfront pod and do following:

    1) get tunnelfront logs: "docker ps" -> "docker logs <tunnelfront_container_id>"
    2) "nslookup <ssh-server_fqdn>" whose fqdn can be get from above command -> if it resolves ip, which means dns works, then go to the following step
    3) "ssh -vv azureuser@<ssh-server_fqdn> -p 9000" ->if port is working, go to the next step
    4) "docker exec -it <tunnelfront_container_id> /bin/bash", type "ping google.com", if it is no response, which means tunnel front pod doesn't have external network, then do following step
    5) restart kube-proxy, using "kubectl delete po <kube-proxy_pod> -n kube-system", choose the kube-proxy which is running on the same node with tunnelfront. customer can use "kubectl get po -n kube-system -o wide"

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments No comments