OpenLens 6.3.0 - No Logs or Shell buttons

[lukjaw]

Describe the bug After installing OpenLens v 6.3.0 i cannot see Logs and Shell buttons under pods / nodes

To Reproduce Steps to reproduce the behavior:

1. Install OpenLens on Windows using scoop
2. Launching OpenLens

Expected behavior I would like to see the Logs and Shell buttons like in standard Lens IDE

Screenshots

Environment (please complete the following information):

• Lens Version: OpenLens v 6.3.0
• OS: Windows 10 Build 19044.2364
• Installation method (e.g. snap or AppImage in Linux): scoop

Logs: When you run the application executable from command line you will see some logging output. Please paste them here:

info:    Ôľ¬ ­čöî Starting LensProxy +0ms
info:    Ôľ¬ [LENS-PROXY]: Proxy server has started at 127.0.0.1:53779 +5ms
info:    Ôľ¬ ­čöÄ Testing LensProxy connection ... +2ms
info:    Ôľ¬ [LENS-USER-STORE]: LOADING ... +7ms
info:    Ôľ¬ [LENS-USER-STORE]: LOADED from C:\Users\lukjaw\AppData\Roaming\OpenLens\lens-user-store.json +14ms
info:    Ôľ¬ [LENS-CLUSTER-STORE]: LOADING ... +0ms
info:    Ôľ¬ [LENS-CLUSTER-STORE]: LOADED from C:\Users\lukjaw\AppData\Roaming\OpenLens\lens-cluster-store.json +140ms
info:    Ôľ¬ ÔÜí LensProxy connection OK +16ms
info:    Ôľ¬ [CREATE-ELECTRON-WINDOW]: Loading content for window "splash" from file: C:\Users\lukjaw\scoop\apps\openlens\current\resources\app.asar\static\splash.html... +48ms
info:    Ôľ¬ [CREATE-ELECTRON-WINDOW]: Window "splash" loaded +222ms
info:    Ôľ¬ [LENS-EXTENSIONS]: LOADING ... +21ms
info:    Ôľ¬ [LENS-EXTENSIONS]: LOADED from C:\Users\lukjaw\AppData\Roaming\OpenLens\lens-extensions.json +3ms
info:    Ôľ¬ [LENS-WEBLINK-STORE]: LOADING ... +5ms
info:    Ôľ¬ [LENS-WEBLINK-STORE]: LOADED from C:\Users\lukjaw\AppData\Roaming\OpenLens\lens-weblink-store.json +12ms
info:    Ôľ¬ ­čôč Setting protocol client for lens:// +8ms
info:    Ôľ¬ ­čôč Protocol client register succeeded Ôťů +2ms
info:    Ôľ¬ ­čžę Initializing extensions +4ms
info:    Ôľ¬ [LENS-FILESYSTEM-PROVISIONER-STORE]: LOADING ... +41ms
info:    Ôľ¬ [LENS-FILESYSTEM-PROVISIONER-STORE]: LOADED from C:\Users\lukjaw\AppData\Roaming\OpenLens\lens-filesystem-provisioner-store.json +4ms
info:    Ôľ¬ ­čÉÜ Syncing shell environment +0ms
info:    Ôľ¬ [EXTENSIONS-LOADER]: auto initializing extensions +23ms
info:    Ôľ¬ [LENS-HOTBAR-STORE]: LOADING ... +2ms
info:    Ôľ¬ [LENS-HOTBAR-STORE]: LOADED from C:\Users\lukjaw\AppData\Roaming\OpenLens\lens-hotbar-store.json +10ms
info:    Ôľ¬ [EXTENSION-DISCOVERY] loading extensions from C:\Users\lukjaw\AppData\Roaming\OpenLens +9ms
info:    Ôľ¬ [EXTENSION-DISCOVERY] watching extension add/remove in C:\Users\lukjaw\.k8slens\extensions +12ms
info:    Ôľ¬ [CREATE-ELECTRON-WINDOW]: Loading content for window "first-application-window" from url: http://localhost:53779... +17ms
info:    Ôľ¬ [CREATE-ELECTRON-WINDOW]: Window "first-application-window" loaded +2s
Checking for update
info:    Ôľ¬ [KUBECONFIG-SYNC]: starting requested syncs +444ms
info:    ÔöĆ [KUBECONFIG-SYNC]: starting sync of file/folder +2ms
info:    ÔöŚ [1] { filePath: 'C:\\Users\\lukjaw\\AppData\\Roaming\\OpenLens\\kubeconfigs' }
info:    ÔöĆ [KUBECONFIG-SYNC]: starting sync of file/folder +2ms
info:    ÔöŚ [1] { filePath: 'C:\\Users\\lukjaw\\.kube' }

Error: Error: Cannot find channel "latest.yml" update info: HttpError: 404
"method: GET url: https://github.com/MuhammedKalkan/OpenLens/releases/download/Latest/latest.yml?noCache=1gkstml0t\n\nPlease double check that your authentication token is correct. Due to security reasons, actual status maybe not reported, but 404.\n"
Headers: {
  "server": "GitHub.com",
  "date": "Thu, 22 Dec 2022 12:42:34 GMT",
  "content-type": "text/plain; charset=utf-8",
  "vary": "X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, Accept-Encoding, Accept, X-Requested-With",
  "cache-control": "no-cache",
  "strict-transport-security": "max-age=31536000; includeSubdomains; preload",
  "x-frame-options": "deny",
  "x-content-type-options": "nosniff",
  "x-xss-protection": "0",
  "referrer-policy": "no-referrer-when-downgrade",
  "content-security-policy": "default-src 'none'; base-uri 'self'; connect-src 'self'; form-action 'self'; img-src 'self' data:; script-src 'self'; style-src 'unsafe-inline'",
  "content-encoding": "gzip",
  "content-length": "29",
  "x-github-request-id": "D228:79F3:8527612:893D291:63A450BA"
}
    at createHttpError (C:\Users\lukjaw\scoop\apps\openlens\6.3.0\resources\app.asar\node_modules\electron-updater\node_modules\builder-util-runtime\out\httpExecutor.js:14:12)
    at ElectronHttpExecutor.handleResponse (C:\Users\lukjaw\scoop\apps\openlens\6.3.0\resources\app.asar\node_modules\electron-updater\node_modules\builder-util-runtime\out\httpExecutor.js:116:20)
    at ClientRequest.<anonymous> (C:\Users\lukjaw\scoop\apps\openlens\6.3.0\resources\app.asar\node_modules\electron-updater\node_modules\builder-util-runtime\out\httpExecutor.js:82:26)
    at ClientRequest.emit (node:events:526:28)
    at ClientRequest.emit (node:domain:475:12)
    at SimpleURLLoaderWrapper.<anonymous> (node:electron/js2c/browser_init:101:6917)
    at SimpleURLLoaderWrapper.emit (node:events:526:28)
    at SimpleURLLoaderWrapper.emit (node:domain:475:12)
    at Object.newError (C:\Users\lukjaw\scoop\apps\openlens\6.3.0\resources\app.asar\node_modules\electron-updater\node_modules\builder-util-runtime\out\index.js:47:19)
    at GenericProvider.getLatestVersion (C:\Users\lukjaw\scoop\apps\openlens\6.3.0\resources\app.asar\node_modules\electron-updater\out\providers\GenericProvider.js:27:50)
    at async NsisUpdater.getUpdateInfoAndProvider (C:\Users\lukjaw\scoop\apps\openlens\6.3.0\resources\app.asar\node_modules\electron-updater\out\AppUpdater.js:298:19)
    at async NsisUpdater.doCheckForUpdates (C:\Users\lukjaw\scoop\apps\openlens\6.3.0\resources\app.asar\node_modules\electron-updater\out\AppUpdater.js:312:24)
    at async C:\Users\lukjaw\scoop\apps\openlens\6.3.0\resources\app.asar\static\build\main.js:2:413995
    at async r (C:\Users\lukjaw\scoop\apps\openlens\6.3.0\resources\app.asar\static\build\main.js:2:414485)
    at async C:\Users\lukjaw\scoop\apps\openlens\6.3.0\resources\app.asar\static\build\main.js:2:417149
error:   ÔöĆ [UPDATE-APP/CHECK-FOR-UPDATES] Cannot find channel "latest.yml" update info: HttpError: 404
"method: GET url: https://github.com/MuhammedKalkan/OpenLens/releases/download/Latest/latest.yml?noCache=1gkstml0t\n\nPlease double check that your authentication token is correct. Due to security reasons, actual status maybe not reported, but 404.\n"
Headers: {
  "server": "GitHub.com",
  "date": "Thu, 22 Dec 2022 12:42:34 GMT",
  "content-type": "text/plain; charset=utf-8",
  "vary": "X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, Accept-Encoding, Accept, X-Requested-With",
  "cache-control": "no-cache",
  "strict-transport-security": "max-age=31536000; includeSubdomains; preload",
  "x-frame-options": "deny",
  "x-content-type-options": "nosniff",
  "x-xss-protection": "0",
  "referrer-policy": "no-referrer-when-downgrade",
  "content-security-policy": "default-src 'none'; base-uri 'self'; connect-src 'self'; form-action 'self'; img-src 'self' data:; script-src 'self'; style-src 'unsafe-inline'",
  "content-encoding": "gzip",
  "content-length": "29",
  "x-github-request-id": "D228:79F3:8527612:893D291:63A450BA"
}
    at createHttpError (C:\Users\lukjaw\scoop\apps\openlens\6.3.0\resources\app.asar\node_modules\electron-updater\node_modules\builder-util-runtime\out\httpExecutor.js:14:12)
    at ElectronHttpExecutor.handleResponse (C:\Users\lukjaw\scoop\apps\openlens\6.3.0\resources\app.asar\node_modules\electron-updater\node_modules\builder-util-runtime\out\httpExecutor.js:116:20)
    at ClientRequest.<anonymous> (C:\Users\lukjaw\scoop\apps\openlens\6.3.0\resources\app.asar\node_modules\electron-updater\node_modules\builder-util-runtime\out\httpExecutor.js:82:26)
    at ClientRequest.emit (node:events:526:28)
    at ClientRequest.emit (node:domain:475:12)
    at SimpleURLLoaderWrapper.<anonymous> (node:electron/js2c/browser_init:101:6917)
    at SimpleURLLoaderWrapper.emit (node:events:526:28)
    at SimpleURLLoaderWrapper.emit (node:domain:475:12) +286ms
error:   Ôöâ [ 1] Error: Cannot find channel "latest.yml" update info: HttpError: 404
error:   Ôöâ [ 2] "method: GET url: https://github.com/MuhammedKalkan/OpenLens/releases/download/Latest/latest.yml?noCache=1gkstml0t\n\nPlease double check that your authentication token is correct. Due to security reasons, actual status maybe not reported, but 404.\n"
error:   Ôöâ [ 3] Headers: {
error:   Ôöâ [ 4]   "server": "GitHub.com",
error:   Ôöâ [ 5]   "date": "Thu, 22 Dec 2022 12:42:34 GMT",
error:   Ôöâ [ 6]   "content-type": "text/plain; charset=utf-8",
error:   Ôöâ [ 7]   "vary": "X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, Accept-Encoding, Accept, X-Requested-With",
error:   Ôöâ [ 8]   "cache-control": "no-cache",
error:   Ôöâ [ 9]   "strict-transport-security": "max-age=31536000; includeSubdomains; preload",
error:   Ôöâ [10]   "x-frame-options": "deny",
error:   Ôöâ [11]   "x-content-type-options": "nosniff",
error:   Ôöâ [12]   "x-xss-protection": "0",
error:   Ôöâ [13]   "referrer-policy": "no-referrer-when-downgrade",
error:   Ôöâ [14]   "content-security-policy": "default-src 'none'; base-uri 'self'; connect-src 'self'; form-action 'self'; img-src 'self' data:; script-src 'self'; style-src 'unsafe-inline'",
error:   Ôöâ [15]   "content-encoding": "gzip",
error:   Ôöâ [16]   "content-length": "29",
error:   Ôöâ [17]   "x-github-request-id": "D228:79F3:8527612:893D291:63A450BA"
error:   Ôöâ [18] }
error:   Ôöâ [19]     at createHttpError (C:\Users\lukjaw\scoop\apps\openlens\6.3.0\resources\app.asar\node_modules\electron-updater\node_modules\builder-util-runtime\out\httpExecutor.js:14:12)
error:   Ôöâ [20]     at ElectronHttpExecutor.handleResponse (C:\Users\lukjaw\scoop\apps\openlens\6.3.0\resources\app.asar\node_modules\electron-updater\node_modules\builder-util-runtime\out\httpExecutor.js:116:20)
error:   Ôöâ [21]     at ClientRequest.<anonymous> (C:\Users\lukjaw\scoop\apps\openlens\6.3.0\resources\app.asar\node_modules\electron-updater\node_modules\builder-util-runtime\out\httpExecutor.js:82:26)
error:   Ôöâ [22]     at ClientRequest.emit (node:events:526:28)
error:   Ôöâ [23]     at ClientRequest.emit (node:domain:475:12)
error:   Ôöâ [24]     at SimpleURLLoaderWrapper.<anonymous> (node:electron/js2c/browser_init:101:6917)
error:   Ôöâ [25]     at SimpleURLLoaderWrapper.emit (node:events:526:28)
error:   Ôöâ [26]     at SimpleURLLoaderWrapper.emit (node:domain:475:12)
error:   Ôöâ [27]     at Object.newError (C:\Users\lukjaw\scoop\apps\openlens\6.3.0\resources\app.asar\node_modules\electron-updater\node_modules\builder-util-runtime\out\index.js:47:19)
error:   Ôöâ [28]     at GenericProvider.getLatestVersion (C:\Users\lukjaw\scoop\apps\openlens\6.3.0\resources\app.asar\node_modules\electron-updater\out\providers\GenericProvider.js:27:50)
error:   Ôöâ [29]     at async NsisUpdater.getUpdateInfoAndProvider (C:\Users\lukjaw\scoop\apps\openlens\6.3.0\resources\app.asar\node_modules\electron-updater\out\AppUpdater.js:298:19)
error:   Ôöâ [30]     at async NsisUpdater.doCheckForUpdates (C:\Users\lukjaw\scoop\apps\openlens\6.3.0\resources\app.asar\node_modules\electron-updater\out\AppUpdater.js:312:24)
error:   Ôöâ [31]     at async C:\Users\lukjaw\scoop\apps\openlens\6.3.0\resources\app.asar\static\build\main.js:2:413995
error:   Ôöâ [32]     at async r (C:\Users\lukjaw\scoop\apps\openlens\6.3.0\resources\app.asar\static\build\main.js:2:414485)
error:   Ôöâ [33]     at async C:\Users\lukjaw\scoop\apps\openlens\6.3.0\resources\app.asar\static\build\main.js:2:417149
error:   ÔöŚ [34] { code: 'ERR_UPDATER_CHANNEL_FILE_NOT_FOUND' }

Additional context I Was using Lens IDE on a license grace period and i wanted to switch to OpenLens.

I removed previous Lens version and cleared all /User/Appdata files and any remaining files from old installations, rebooted, re-installed OpenLens again, tried also solution mentioned in here:

https://github.com/lensapp/lens/issues/1690#issuecomment-886260245

But i ran npm install from the scoop folder (C:\Users****\scoop\apps\openlens\6.3.0\resources\app.asar.unpacked\node_modules)

[kumar-cloud]

Guys, I found this plugin much useful for pod logs and terminal. Add below plugin name in extensions tab in OpenLens @alebcay/openlens-node-pod-menu

[inquinity]

At the risk of beating a proverbial dead horse, I have to agree that this was a badly timed and communicated change. I represent several hundreds of users at a fortune 10 company, and we are in the process of switch from Lens to OpenLens. I tested OpenLens 6.2.5, found that it works acceptably, and recommended the upgrade path. I have been receiving numerous support requests from people who went straight to version 6.3.0 and were understandably frustrated with the missing functionality. Sadly, I think this has damaged OpenLens' reputation and lost users.

I understand the intention, but the lack of communication and visible roadmap created huge confusion at a time of maximum impact (due to the volume of new OpenLens users).

For my part, I will keep my development teams on 6.2.5 until the functionality is restored; however, that has created a great deal of extra work just communicating with my internal users.

[javier-tarazaga]

@inquinity buy you can get that functionality back in the latest version. In 6.3.0 you can simply open the Extensions page, type @alebcay/openlens-node-pod-menu, click install and voila, logs and shell are back again into OpenLens.

I can understand the confusion around the miscommunication and the fact that those features disappeared from the product with an update and was not even notified in the app itself that it was the case (I had to search online myself to figure out what in the world happened), but I guess by simply letting the OpenLens team simply communicate were you can get back the functionality lost before the update by installing extensions which were installed by default I guess would simply solve the issue.

For OpenLens team, maybe a slight suggestion is that in the Extension page you have a list of known extensions and possibly mark some of them as "oficial" or "reviewed" or similar), with some basic info and a link to the source, add a possibility to simply click install and good to go. This would heavily reduce the friction of finding new extensions.

[halllo]

@javier-tarazaga Thanks! I started to get familiar with kubectl logs <pod name> again :)

[paul-civitas]

• While ejecting in-tree extensions, we didn't (yet) decide where these ejected components would live. We had various ideas but it was no top priority. As you can imagine, these ejected components are also used by the official Lens Desktop application available from https://k8slens.dev. We'd need to resolve this topic before we can even ship a new version ourselves!

@miskun These ejected components are responsible for core functionality we use every day. Have you decided yet whether these ejected components will live in an open source licensed public repo? Or if they will live in a private repo?

The reason people are concerned is because rather than being moved to a different place, such as a different folder or a different open source repo, the components disappeared entirely and a new version was released without any ability to add the components back.

Obviously this functionality isn't going to be removed from the commercial version of lens, so what happened has people thinking that these ejected components are going to be living in a private git repository from now on. You could calm tensions a lot by promising that these components will be open sourced.

[paul-civitas]

We had various ideas but it was no top priority.

We'd need to resolve this topic before we can even ship a new version ourselves!

This is strange phrasing. If it's a blocker for a shipping a new version why isn't it a top priority?

[dj-thd2]

Thank you for ruining a wonderful opensource project, I will not use Lens nor recommend it anymore to anyone else

[omniproc]

Classic RedHat move.

[inquinity]

@inquinity buy you can get that functionality back in the latest version. In 6.3.0 you can simply open the Extensions page, type @alebcay/openlens-node-pod-menu, click install and voila, logs and shell are back again into OpenLens.

I can understand the confusion around the miscommunication and the fact that those features disappeared from the product with an update and was not even notified in the app itself that it was the case (I had to search online myself to figure out what in the world happened), but I guess by simply letting the OpenLens team simply communicate were you can get back the functionality lost before the update by installing extensions which were installed by default I guess would simply solve the issue.

For OpenLens team, maybe a slight suggestion is that in the Extension page you have a list of known extensions and possibly mark some of them as "oficial" or "reviewed" or similar), with some basic info and a link to the source, add a possibility to simply click install and good to go. This would heavily reduce the friction of finding new extensions.

@javier-tarazaga I appreciate the advice. With up to several thousand developers all looking to me as the "expert" on using OpenLens, having to instruct them all on adding extensions to get essential functionality could be unfeasible.

My point to the development team is that producing a version that installs without the expected and necessary functionality is not workable. My point to the community is that we are al human, give the development team some time to come up with a solution. There are no villains; at the same time, forthright and honest communication is the foundation of the open source community.

[cubed-it]

While I understand all the frustration and confusion around this topic, I think it's been getting a bit out of hand. It's quite funny for me to think why some people have a tendency to think that we (people who created Lens to become what it is today) are somehow on a mission to sabotage this project on purpose. Let me ask you: how many projects with >20k stars on Github have you ever created? Let's imagine you have created one. Why would you then start sabotaging it? I guess nobody would. It’s something to be proud of and you’ll want to take super good care of it!

We are quite proud of what we have created and want to keep on working on this project to make it even more awesome in the future. Something that works for our own needs but also for those who want to build their own versions and flavors.

I hope this brings clarity for the issue. We appreciate all constructive feedback on this matter but if the comments in here are just expressing your frustration or suggestions for using X, Y or Z instead of using Lens we’ll close the commenting as it does not have value for the issue.

Then why is this PR still open and never got feedback? https://github.com/lensapp/lens/pull/5772

[JAZ-013]

At a minimum the extension should be listed in the Lens Extensions repository which is linked from the app extensions page. To that affect, if I have created a PR with the minimum required changes. See: https://github.com/lensapp/lens-extensions/pull/21

As a new user of OpenLens, it was MUCH harder to find this functionality than it should have been. I kinda understand why it was removed and why extensions shouldn't be in the main repo, but honestly this functionality should not be implemented as an extension in the first place. It is the reason I use this app.

[ricardo-overhaul]

from https://github.com/MuhammedKalkan/OpenLens/issues/127#issuecomment-1451852949

This is due to a breaking change in the Lens project, to move non core functionality into extensions: lensapp/lens#6823 and lensapp/lens#6983

Why pods and logs are considered optional? I've got no idea.

The fix is to install https://github.com/alebcay/openlens-node-pod-menu through the extensions.

[UmarFKhawaja]

There is another piece of functionality that has gone missing.

One used to be able to install Prometheus monitoring for the cluster via the Preferences. That has gone missing. Does someone know whether that functionality has also gone AWOL due to project restructuring, and if it is available as an extension?

[SalahAdDin]

from MuhammedKalkan/OpenLens#127 (comment)

This is due to a breaking change in the Lens project, to move non core functionality into extensions: lensapp/lens#6823 and lensapp/lens#6983 Why pods and logs are considered optional? I've got no idea. The fix is to install https://github.com/alebcay/openlens-node-pod-menu through the extensions.

Cool, thanks!

[madduci]

from MuhammedKalkan/OpenLens#127 (comment)

This is due to a breaking change in the Lens project, to move non core functionality into extensions: lensapp/lens#6823 and lensapp/lens#6983 Why pods and logs are considered optional? I've got no idea. The fix is to install https://github.com/alebcay/openlens-node-pod-menu through the extensions.

I've tested the plugin on Windows on latest Open Lens and it still doesn't show the logs

[andreivasy]

I've tested https://github.com/alebcay/openlens-node-pod-menu on OpenLens 6.4.11 and it works

[JAZ-013]

I created a pull request on this ages ago that still has not been merged.

https://github.com/lensapp/lens-extensions/pull/21

[madduci]

I've tested https://github.com/alebcay/openlens-node-pod-menu on OpenLens 6.4.11 and it works

I've tested it too with 6.4.11 installed via chocolatey and it doesn't show up

[SalahAdDin]

I created a pull request on this ages ago that still has not been merged.

lensapp/lens-extensions#21

I did find the extension, but I don't remember where, hahaha

[andreivasy]

I've tested https://github.com/alebcay/openlens-node-pod-menu on OpenLens 6.4.11 and it works

I've tested it too with 6.4.11 installed via chocolatey and it doesn't show up

Is it enabled?

I installed OpenLens using the EXE from here: https://github.com/MuhammedKalkan/OpenLens/releases

[tibistibi]

Yes. Go to extensions (ctrl+shift+e) add this name in the box: @alebcay/openlens-node-pod-menu and hit install. After that all was a bit buggy but after restart it works fine and i have the menu options back

[grimlokason]

it's enabled on 6.4.15, but didn't work :/ going back to the one previous 6.3,

Quite a bad move to remove fonction like those whle wanting to create a modular apps without providing them.

[naydoo]

Yes. Go to extensions (ctrl+shift+e) add this name in the box: @alebcay/openlens-node-pod-menu and hit install. After that all was a bit buggy but after restart it works fine and i have the menu options back

This worked for me

[alvarezdaniel]

Yes. Go to extensions (ctrl+shift+e) add this name in the box: @alebcay/openlens-node-pod-menu and hit install. After that all was a bit buggy but after restart it works fine and i have the menu options back

Thanks, shell and logs are back!

[ChrisNoSim]

Thx all is working again!!! Nice job 🙏

[ns-rloffelmacher]

FWIW I needed to enable the plugin after adding

[grimlokason]

The plugin didn't worked here.

tried a lot of things in various order: uninstall/reinstall the plugin. enable/disable it, restart openlens... the only solution was to revert to the last version with it.

[fabio-andre-rodrigues]

The plugin didn't worked here.

tried a lot of things in various order: uninstall/reinstall the plugin. enable/disable it, restart openlens... the only solution was to revert to the last version with it.

The same. After last update no more logs

[SalahAdDin]

The plugin didn't work here. tried a lot of things in various orders: uninstall/reinstall the plugin. enable/disable it, restart open lens... the only solution was to revert to the last version with it.

The same. After the last update no more logs

Don't tell us this!

[kbocock-krg]

Not working in this version. Literally the logs are the 1 feature I use the most. Please fix asap. OpenLens: 6.5.2-309

[maximkosheev]

plugin not work on version 6.5.2-356 even after enabled.

[SalahAdDin]

Seems the plugin needs to be updated.

[FyiurAmron]

FWIW, please take the discussions about the plugin to the plugin page. It doesn't make any sense to discuss it here. (and it works for me, on OpenLens 6.5.2-356 , you just need to terminate OpenLens right after the install and then restart it, it works then)

[alebcay]

For what it's worth, I have been using version 0.1.0 of the plugin with OpenLens 6.5.2-366 without any issues. I'll cut a new release soon but it's unclear to me if this will actually fix any of the problems that people have been running into.

In the future, please use the issue board on the plugin itself for discussing these concerns. I don't actively follow this thread much anymore, so I will be better able to respond to any compatibility issues that people are running into and we can keep track of the outstanding issues in one place.

[marafa-sugarcrm]

this was automagically fixed for me

[gudge25]

@alebcay/openlens-node-pod-menu do the trick but better it to be build in

• cant find Prometheus installation anymore

[pbv7]

@alebcay/openlens-node-pod-menu do the trick but better it to be build in

• cant find Prometheus installation anymore

Workaround @shilazi/openlens-lens-metrics

[swagfin]

Yes. Go to extensions (ctrl+shift+e) add this name in the box: @alebcay/openlens-node-pod-menu and hit install. After that all was a bit buggy but after restart it works fine and i have the menu options back

This has worked on v6.5.2, thank you. I had to open extension again and manually enable it

[ro0NL]

lol why isnt this enabled by default?

[danilogco]

lol why isnt this enabled by default?

They have a paid version and free subscription is gone. Strategy? :moneybag:

Btw, if anyone has a problem trying to install extensions, I suggest trying deleting everything from the directory `~/.var/app/dev.k8slens.OpenLens/'. It worked for me. The flatpak version didn't worked well here, I installed via https://github.com/MuhammedKalkan/OpenLens.

[Laser42]

Yes. Go to extensions (ctrl+shift+e) add this name in the box: @alebcay/openlens-node-pod-menu and hit install. After that all was a bit buggy but after restart it works fine and i have the menu options back

This doesn't work for me. I tried to force use a registry from my global .npmrc. Was it security restriction or not, i've found the simplest way, because compiling extension from the sources is much more harder.

So:

1. npm install -g @alebcay/openlens-node-pod-menu
2. Locate downloaded package, navigate into @alebcay folder
3. Use archive tool (I used 7zip) to add openlens-node-pod-menu directory into new tar archive
4. Just drag-and-drop tar archive into OpenLens > File > Extensions window

Voila, I hope this can help someone

[krafcik02]

In OpenLens open Extension (Win – Ctrl + Shift + e, 🍎 - Command + Shift + e), Enter @alebcay/openlens-node-pod-menu and install Enjoy!

[JAZ-013]

In OpenLens open Extension (Win – Ctrl + Shift + e, 🍎 - Command + Shift + e), Enter @alebcay/openlens-node-pod-menu and install Enjoy!

Dude, this was closed like a year ago.

[krafcik02]

Yesterday I ran into this issue, i have found a solution and so I wanted to share that. What is your problem?

št 7. 3. 2024 o 23:35 Jamie Carl @.***> napísal(a):

In OpenLens open Extension (Win – Ctrl + Shift + e, 🍎 - Command + Shift + e), Enter @alebcay/openlens-node-pod-menu and install Enjoy!

Dude, this was closed like a year ago.

— Reply to this email directly, view it on GitHub https://github.com/lensapp/lens/issues/6823#issuecomment-1984666683, or unsubscribe https://github.com/notifications/unsubscribe-auth/AYWUYRFJAMJXCITOWEEANCTYXDTSVAVCNFSM6AAAAAATGWPL56VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGY3DMNRYGM . You are receiving this because you commented.Message ID: @.***>