# Clusters dissapeared on the new Lens Desktop Version

**URL:** https://forums.k8slens.dev/t/clusters-dissapeared-on-the-new-lens-desktop-version/5210
**Category:** Lens Support & Troubleshooting
**Tags:** new-release, macos, lens-desktop, kubernetes, cluster
**Created:** [December 16, 2024, 11:34am UTC](https://forums.k8slens.dev/t/clusters-dissapeared-on-the-new-lens-desktop-version/5210 "2024-12-16T11:34:13Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![joaomjoia](https://forums.k8slens.dev/letter_avatar_proxy/v4/letter/j/bb73d2/32.png) [@joaomjoia](https://forums.k8slens.dev/u/joaomjoia)
#### Post date: [December 16, 2024, 11:34am UTC](https://forums.k8slens.dev/t/clusters-dissapeared-on-the-new-lens-desktop-version/5210/1 "2024-12-16T11:34:13Z")

</div>

Hello,

As requested by the application I updated the Lens Desktop to version 2024.11.261604-latest.

Now I open the Lens Desktop and can’t see my EKS clusters.  
I have the kubeconfig present on the Lens Desktop but nothing happens.

If I change my apiVersion from “[client.authentication.k8s.io/v1alpha1](http://client.authentication.k8s.io/v1alpha1)” to apiVersion “[client.authentication.k8s.io/v1beta1](http://client.authentication.k8s.io/v1beta1)”, the clusters appears on the LEns Desktop but still doesn’t work.

Last version of the Lens Desktop everything was working correctly.

MAy someone help me out here?

Lens Desktop: 2024.11.261604-latest  
MacOS Sequoia Version 15.1.1 Intel

---

<div class="post-metadata">

### Author: ![phorsmalahti](https://forums.k8slens.dev/user_avatar/forums.k8slens.dev/phorsmalahti/32/560_2.png) [@phorsmalahti](https://forums.k8slens.dev/u/phorsmalahti)
#### Post date: [December 16, 2024, 11:37am UTC](https://forums.k8slens.dev/t/clusters-dissapeared-on-the-new-lens-desktop-version/5210/2 "2024-12-16T11:37:34Z")

</div>

Can you try to regenerate the kubeconfig with newer tooling?

---

<div class="post-metadata">

### Author: ![joaomjoia](https://forums.k8slens.dev/letter_avatar_proxy/v4/letter/j/bb73d2/32.png) [@joaomjoia](https://forums.k8slens.dev/u/joaomjoia)
#### Post date: [December 16, 2024, 11:57am UTC](https://forums.k8slens.dev/t/clusters-dissapeared-on-the-new-lens-desktop-version/5210/3 "2024-12-16T11:57:58Z")

</div>

Hi,  
Which new tool?

I’m importing kubeconfig from eks as requested by AWS

aws eks update-kubeconfig --name

---

<div class="post-metadata">

### Author: ![phorsmalahti](https://forums.k8slens.dev/user_avatar/forums.k8slens.dev/phorsmalahti/32/560_2.png) [@phorsmalahti](https://forums.k8slens.dev/u/phorsmalahti)
#### Post date: [December 16, 2024, 12:12pm UTC](https://forums.k8slens.dev/t/clusters-dissapeared-on-the-new-lens-desktop-version/5210/4 "2024-12-16T12:12:58Z")

</div>

The aws cli, can you try to update to the latest version of aws cli?

> **[Installing or updating to the latest version of the AWS CLI - AWS Command...](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html)**
>
> Instructions to install or update the AWS CLI on your system.

---

<div class="post-metadata">

### Author: ![maquenedo](https://forums.k8slens.dev/letter_avatar_proxy/v4/letter/m/f14d63/32.png) [@maquenedo](https://forums.k8slens.dev/u/maquenedo)
#### Post date: [December 17, 2024, 4:29pm UTC](https://forums.k8slens.dev/t/clusters-dissapeared-on-the-new-lens-desktop-version/5210/5 "2024-12-17T16:29:09Z")

</div>

Hi, this happened today to me. AWS cli version was just too old. Updated aws cli to latest, ran `aws eks update-kubeconfig --name=<cluster-name>` and clusters reappeared.

---

<div class="post-metadata">

### Author: ![romanmaerov](https://forums.k8slens.dev/letter_avatar_proxy/v4/letter/r/ecae2f/32.png) [@romanmaerov](https://forums.k8slens.dev/u/romanmaerov)
#### Post date: [December 18, 2024, 2:52pm UTC](https://forums.k8slens.dev/t/clusters-dissapeared-on-the-new-lens-desktop-version/5210/6 "2024-12-18T14:52:11Z")

</div>

It happened to me also… after upgrading to the latest 2024.11.261604 )-: AWS CLI upgrade solved the issue for me. IMO Lense should provide some warning regarding this before the upgrade, like the precondition is the latest AWS CLI or something…