Lens: Lens 4.0 Breaking on MAC

Created on 8 Dec 2020  路  10Comments  路  Source: lensapp/lens

Describe the bug
Unable to use & load any section after upgrading to 4.0.0 on MAC.

To Reproduce
Steps to reproduce the behavior:

  1. Update to 4.0.0
  2. Start Lens
  3. Open Developer console to see the error

Expected behavior
All sections should load the Kubernetes related resources properly

Screenshots
Screen Shot 2020-12-08 at 6 41 30 PM

Environment (please complete the following information):

  • Lens Version: 4.0.0
  • OS: [e.g. MacOS High Sierra Version 10.13.6]
  • Installation method (e.g. snap or AppImage in Linux): Auto Upgrade
bug

Most helpful comment

I manually specified the namespaces I have access to on the cluster

  • File -> Cluster Settings (Ctrl-Shift-S)

Lens appears to be working again.

PS

  • Restart Lens after adding namespaces

All 10 comments

I have the same issue. And when I open a lower version, it auto updates to v4. Now I can only use lens by continually reinstalling v3.6.9

Why on earth isn't it possible to deactivate auto-update? Maybe you could try to restrict write-access to the binary to prevent it from overwriting the current version?

Facing the same issue. I reinstalled 3.9.6 but it doesn't work anymore.

@ub-wroteIt do you have admin on the cluster - I have similar issue on clusters where I am not admin (and it works fine on ones I am), both on Macs and Windows https://github.com/lensapp/lens/issues/1682

Same here, opened lens in debug mode on windows and no error are show in logs.
With lens 3.6.9 it works fine. I'm not cluster admin.

@Arnonrgo No, I am not an admin on a cluster. The same cluster was working on an older version(with non-admin role).

Same issue here too. Works with 3.9.6. Broken with 4.0. Forced to upgrade. Also not admin on the cluster.

I manually specified the namespaces I have access to on the cluster

  • File -> Cluster Settings (Ctrl-Shift-S)

Lens appears to be working again.

PS

  • Restart Lens after adding namespaces

@myspotontheweb , This workaround dint worked for me

Is anybody from Lens working on this!? We lost an access to our clusters and had to switch to kubectl CLI

Was this page helpful?
0 / 5 - 0 ratings

Related issues

kotcev picture kotcev  路  3Comments

headcr4sh picture headcr4sh  路  5Comments

diemus picture diemus  路  3Comments

ocdi picture ocdi  路  4Comments

jtackaberry picture jtackaberry  路  6Comments