-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
no connection for cached dial! for eks cluster #2677
Comments
A few weeks ago I also started to have "no connection for cached dial" errors all of the sudden. I've used k9s for more than a year and never had that problem before. In my case I'm connecting to GKE clusters. If I try to reach the clusters using |
@pdfrod did you try the workaround i mention |
Just tried it, but it didn't make any difference for me unfortunately. |
Unfortunately I'm also running into this same issue. After sourcing my new AWS temp credentials with MFA if i start k9s i have to wait several seconds for the context to be loaded properly and it starts working. However sometimes it doesn't load properly and I'm stuck with: "no connection to cached dial". Version: v0.32.4 |
Having the same issue, in some cases k9s appears to reload itself and somehow the issue resolves itself but I'm not quite sure how to trigger it. I tried switching between clusters or hitting I even tried to re-authenticate outside of k9s but the UI eventually seemed to refresh on its own after several seconds. It might be helpful to be able to trigger whatever refresh process seemingly happens in the background manually either when refreshing with |
I ran into this problem today with clusters in both EKS and GKE, and here's how I solved it:
After following these three steps, k9s automatically boots into the last context I connected to. I believe what happened in my case was that I updated the names of my contexts in my |
Most likely a duplicate of #2651 |
Maybe not related, but: we are using GCP and what has helped me was:
|
Same issue here with GCP and AZ clusters |
Same issue here with AZ and Openshift clusters |
Actually not, since I am having the problem as well and I do have Edit: I even moved my |
FWIW, I just ran in to this. I was deleting a cluster while I had k9s open so I could watch the nodes being drained. I didn't exit k9s by the time the cluster was being deleted. I tried the workarounds listed about, but ultimately I had to switch the |
It seems "no connection to cached dial" can happen for a number of reasons. I eventually narrowed down the cause by looking in My instance of this error was caused by DNS failing to resolve through my SOCKS proxy (it's always DNS). It's clearly different for different people. |
Describe the bug
cannot connect to EKS cluster after credentials expire and are refreshed
get "no connection for cached dial!"
To Reproduce
Steps to reproduce the behavior:
Historical Documents
1932 9:00AM INF <U+2705> Kubernetes connectivity 1933 9:00AM ERR Fail to load global/context configuration error="the server has asked for the client to provide credentials\nk9s config file "/home/someuser/.config/k9s/config.yaml" load failed:\nAdditional pr 1933 operty fullScreen is not allowed\ncannot connect to context: arn:aws:eks:someregion::cluster/blahblah\nk8s connection failed for context: arn:aws:eks:somregeion::cluster/blahblah" 1934 9:00AM ERR Load cluster resources - No API server connection
1935 9:00AM ERR failed to list contexts error="no connection"
1936 9:00AM WRN Unable to dial discovery API error="no connection to dial"
1937 9:00AM ERR can't connect to cluster error="the server has asked for the client to provide credentials"
1938 9:00AM ERR Load cluster resources - No API server connection
1939 9:00AM WRN Unable to dial discovery API error="no connection to dial"
1940 9:00AM ERR Context switch failed error="no connection to cached dial"
1941 9:00AM ERR no connection to cached dial
1942 9:00AM ERR Context switch failed error="no connection to cached dial"
1943 9:00AM ERR no connection to cached dial
1944 9:00AM ERR Context switch failed error="no connection to cached dial"
1945 9:00AM ERR no connection to cached dial
1946 9:00AM ERR Context switch failed error="no connection to cached dial"
1947 9:00AM ERR no connection to cached dial
1948 9:00AM ERR Context switch failed error="no connection to cached dial"
1949 9:00AM ERR no connection to cached dial
1950 9:00AM ERR Context switch failed error="no connection to cached dial"
1951 9:00AM ERR no connection to cached dial
1952 9:00AM ERR Context switch failed error="no connection to cached dial"
1953 9:00AM ERR no connection to cached dial
1954 9:00AM ERR Context switch failed error="no connection to cached dial"
1955 9:00AM ERR no connection to cached dial
1956 9:00AM ERR Context switch failed error="no connection to cached dial"
1957 9:00AM ERR no connection to cached dial
1958 9:00AM ERR Context switch failed error="no connection to cached dial"
1959 9:00AM ERR no connection to cached dial
1960 9:00AM ERR Context switch failed error="no connection to cached dial"
1961 9:00AM ERR no connection to cached dial
1962 9:00AM ERR Context switch failed error="no connection to cached dial"
1963 9:00AM ERR no connection to cached dial
1964 9:00AM ERR Context switch failed error="no connection to cached dial"
1965 9:00AM ERR no connection to cached dial
1966 9:00AM ERR Context switch failed error="no connection to cached dial"
1967 9:00AM ERR no connection to cached dial
1968 9:00AM ERR Context switch failed error="no connection to cached dial"
1969 9:00AM ERR no connection to cached dial
1970 9:00AM ERR Context switch failed error="no connection to cached dial"
1971 9:00AM ERR no connection to cached dial
1972 9:00AM ERR Context switch failed error="no connection to cached dial"
1973 9:00AM ERR no connection to cached dial
1974 9:00AM ERR Context switch failed error="no connection to cached dial"
1975 9:00AM ERR no connection to cached dial
Expected behavior
it refreshes the connection with new creds
Screenshots
Versions (please complete the following information):
Additional context
the only way i could work around this was by moving mv /home/someuser/.local/share/k9s/clusters /home/someuser/.local/share/k9s/clustersbad
The text was updated successfully, but these errors were encountered: