Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kubectl stopped working with ***eastus.azmk8s.io: no such host #104

Closed
AceHack opened this issue Dec 30, 2017 · 5 comments
Closed

kubectl stopped working with ***eastus.azmk8s.io: no such host #104

AceHack opened this issue Dec 30, 2017 · 5 comments

Comments

@AceHack
Copy link

AceHack commented Dec 30, 2017

PS D:\Kubernetes\kube-resources\ark> kubectl get nodes
Unable to connect to the server: dial tcp: lookup aks-use-ar-rgp-use-arch-aks-774cce-acee7226.hcp.eastus.azmk8s.io: no such host

Things were working fine yesterday, this just started!!

@AceHack
Copy link
Author

AceHack commented Dec 30, 2017

az aks browse --name aks-use-arch-dev --resource-group rgp-use-arch-aks

still works fine and I can see everything in my cluster

@AceHack
Copy link
Author

AceHack commented Jan 1, 2018

I think this problem happened because of a second cluster I created and deleted with a similar name. The problem started when I deleted that 2nd cluster.

The 2 clusters were:

--name aks-use-arch-dev --resource-group rgp-use-arch-aks
--name aks-use-arch-dev --resource-group rgp-use-arch-aks9

I deleted
--name aks-use-arch-dev --resource-group rgp-use-arch-aks9

and then, the one below stopped working
--name aks-use-arch-dev --resource-group rgp-use-arch-aks

kubectl stopped working with the error above

@seanknox
Copy link
Contributor

seanknox commented Aug 2, 2018

Closing due inactivity. Feel free to re-open if still an issue.

@toddbu
Copy link

toddbu commented Apr 8, 2019

I ran into this issue and it was because I had forgotten that I deleted the AKS cluster. it's not a terribly intuitive error

@shivarajisnhce
Copy link

shivarajisnhce commented May 16, 2020

az aks get-credentials --name CLUSTER_NAME --resource-group RESORCE_GROUP
this would solve,It updates the config in C:\Users\user_name.kube\config

@ghost ghost locked as resolved and limited conversation to collaborators Aug 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants