v0.25.20: k9s stoped working with AWS EKS clusters

[roma-glushko]

Describe the bug
I have just upgraded to v0.25.20 and I think I have loosed an ability to connect to my AWS EKS clusters.

To Reproduce

1. Copy your AWS creds that you had used to access AWS clusters before and past them into your terminal session
2. Run aws eks update-kubeconfig --name XXX

Expected behavior
Previously these two steps were enough to connect k9s to clusters, but now it opens the following context window:

At the same time, vanilla kubectl could still connect to my clusters.

I have tried this with two AWS clusters associated with different AWS accounts. No luck.

k9s seems to be able to connect to my local k3d-based cluster.

Versions (please complete the following information):

• OS: macOS Monterey 12.4
• K9s: v0.25.20
• K8s: 1.20+

[roma-glushko]

Okay, it seems to be already reported in:

• Unable to connect to context #1619
• K9s fails to work cannot load context after 25.19 version upgrade #1622

[slimus]

@roma-glushko can we close this issue? Or do you still have problems?

[roma-glushko]

@slimus I have still this issue, but it seems to be well-known one, so we can close this particular task.
My workaround was to download some prior version of k9s from https://github.com/derailed/k9s/releases and put it manually to PATH-aware directory 🤷‍♂️

[sindhubb]

@slimus I have still this issue, but it seems to be well-known one, so we can close this particular task. My workaround was to download some prior version of k9s from https://github.com/derailed/k9s/releases and put it manually to PATH-aware directory 🤷‍♂️

Downgrading to which version of k9s worked for you?
Thanks :)

[slimus]

0.25.18 should work (or follow instructions and update your configs and cli tools)