After addition of a new kubeconfig to sync, the corresponding cluster does not appear in Cluster lists

[alexrubtsov]

Describe the bug After addition of a new kubeconfig to sync, the corresponding cluster does not appear in Cluster lists

To Reproduce

1. Click "Catalog (app)" button
2. Hover over "+" button, then click "Sync kubeconfig file(s)"
3. Select the kubeconfig file (my file is "W:\kubiki\Repro2.txt") and click "Sync"

Actual behavior The list of clusters remains empty

Expected behavior The cluster from the added kubeconfig has appeared in the list of clusters

Screenshots

Environment

• Lens Version: 2023.5.310801-latest
• OS: Windows 11
• Installation method: exe file from the website

Logs: lens-logs-1686757675753.zip

Kubeconfig: Repro2.txt

Additional context

• The added config file is present in "Preferences > Kubernetes > Kubeconfig syncs > Synced items"
• After terminating Lens and then launching again, the cluster appears in the list
• I observe similar behavior when deleting a kubeconfig from sync list - the clusters from this kubeconfig remains in the cluster list until restart of the application

[SpeedHighway]

Additionally, closing and re-opening does not work if you close from the 'X' at the top right. You must use file -> quit.

[wizpresso-steve-cy-fan]

It seems like the sync did not happen immediately

[Pablo-platypus]

this is also happening to me in macOS. I have no way to add Clusters to connect to. It just stopped working. I use the paid/pro version.

Please team, I can see this bug happening on and off for the last few years. It is making this beautiful software useless to me.

[agianni]

Have been seeing this for several months now. The Synch is not working for folders or files...local or remote shares. The only way I can get it to work is to cut and paste the kubeconfig contents in.

[billy-doyle]

Similar issue, although clicking the X or file -> quit did not work for me.

Instead, searched for lens in activity monitor, double clicking and clicking "Quit" did work

[bgalvao]

I know this is not a solution for everyone, but in my case, my ~/.kube dir had more than just the kubeconfig file (~/.kube/config). So that may have been interfering with LENS ability to read in the contexts.. So my solution was

rm -rf ~/.kube
# rewrite kubeconfig file
aws eks update-kubeconfig --region us-central-1 --name your-cluster

[kennethlynne]

My issue: context.cluster did not match cluster.name, so there was an error in the config. Fixing that it showed up immediately

[emirozmen07]

I think this is happening because of the authorization issue. Because after i restarted the openlens it asked me for permission to access to the desktop,. after i gave the permission it appeared in the list.

still, full access to the container takes some time, until that time, i'm not able to see the pods, or anything.

Edit: same issue still happens after permission given, but it appears in the list after couple of minutes.

[carltian]

I think it's your .yaml doc has some error. u can copy content in your .yaml doc to 【File】-【Add Clusters】check it.