Error when connecting to EKS cluster after upgrade to 2025.5.81206

Lens Support & Troubleshooting
#1

After upgrading to 2025.5.81206 I get the following error when connecting to our EKS clusters:

|INFO|Starting connection ...|
|---|---|
|INFO|Authentication proxy started|
|INFO|Refreshing connection status ...|
|ERROR|E0527 11:20:27.338402 47041 proxy_server.go:147] Error while proxying request: getting credentials: exec: executable aws not found It looks like you are trying to use a client-go credential plugin that is not installed. To learn more about this feature, consult the documentation available at: https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins|
|ERROR|Failed to GET https://127.0.0.1:52269/b8ffe8e448b9e76c314f26108007e333/version: Internal Server Error (500)|

This worked fine in the previous version, and works fine if I try to use the same kubeconfig with FreeLens.

#2

How was aws cli installed? Did you use homebrew or the official way to install it?

#3

The CLI was installed with homebrew

#4

I have this issue too. Aws clusters work, but oci clusters don’t.

INFO Starting connection …
INFO Authentication proxy started
INFO Refreshing connection status …
ERROR E0605 14:39:51.293154 42117 proxy_server.go:147] Error while proxying request: getting credentials: exec: executable oci not found It looks like you are trying to use a client-go credential plugin that is not installed. To learn more about this feature, consult the documentation available at: Authenticating | Kubernetes
ERROR Failed to GET “https://127.0.0.1:49778/6406f80ce8cd9e1b218a19f805d3ed15/version”: Internal Server Error (500)

#5

Hey, thanks for the bug report. Could you check where that oci binary is located in your system by running whereis oci and then could you check echo $PATH if that directory is in your path.