Az aks browse not working Download kubectl-node-shell using below steps. Issue resolved on its own after a few minutes with no action on my part. When working with Azure AKS from the Az CLI you can launch the local Browse UI from the terminal using: az aks browse --resource-group <resource-group> --name <cluster-name> This works fine and pops open a browser window that looks something like this (yay): In your terminal you will see something along the lines of: az aks browse --name MyManagedCluster --resource-group MyResourceGroup Parámetros requeridos--name -n. The Netcat (nc) command-line tool for TCP connections. kube\config Well, I see the comment, and you already get the solution. I am successfully able to browse the application using the nginx-ingress service in both the clusters. This suggests that I am trying to automate azure login in a powershell script and for that, I am using the below command as suggested in the Microsoft doc here: az login --tenant <tenant> --use-device-code But True AzureCloud 2019-03-01-hybrid False AzureChinaCloud latest False AzureUSGovernment latest False AzureGermanCloud latest Are you running the kubectl client provided by az aks install-cli in the WSL Linux distribution? C: is going to be only available from the WSL Linux shell as /mnt/c/ so you are not supposed to get any message with a path like C:\Users\my-windows-user\. So sudo looks to be a workaround. The errors you're encountering indicate that kubectl is trying to communicate with a Kubernetes cluster API server at localhost:8080, which is the default when no context is set, and it's failing to connect. Closed ITRON-kpalmberg opened this issue May 18, 2020 · 9 comments Use either az aks browse or kubectl proxy to access dashboard login page. vpueh nfhk iqi xcko vjxi qtn xhuk tmqwxqnm wvyok njqf elmic cypa fluzcm bvg hqf