-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenLens 6.3.0 - No Logs or Shell buttons #6823
Comments
Same issue with clean setup using OpenLens-6.3.0.exe |
On MacOS same thing. @dedo1911 I may know you from some Ingress events, I'm Dedo. :) |
Same issue here on windows, using installer. |
Same on Ubuntu. It looks like a regression of version 6.3.0 |
The in-tree extensions have been removed from with 6.3.0, see the following issues / PRs that explain the background:
Functionality is still available with the latest stable binary version from our website https://k8slens.dev/. |
That's complete bullshit. You took an open-source project and made it un-buildable for commercial purposes. Own it. |
..and just like that, my evaluation of the product is complete, straight to /dev/null with Lens, at least with a dev team trying to cover their crap so sloppily. |
For those of you looking for an alternative, I'll be looking at Monokle Desktop, which just released "Cluster Mode". I haven't tried it yet but thought I'd share. Are there any other GUI clients? |
Seriously folks ? That's exactly how to lose your community (and potential customers)! That's not how you do Open Source. |
My team and I, a pretty large global team, have been evaluating Lens for the last 3 months and it was looking really promising. This change has made our decision for us. We will look elsewhere now. |
anyone gonna fork this tool now? |
There is a fork called OpenLens. I switched to that awhile ago when Lens started requiring a login just to use it. I have been using Lens for about a year and a half at home (and loved it). That is why I recommended it to my company (an example of why the community is important....). But with this happening, I can't even use it personally. I can't check my logs or shell in without needing to do a rebuild or digging into the source code? So why would I stick my neck out and recommend it to my employer? I am personally switching back to k9s for now and trying out Monokle. I may come back to Lens if they fix this, but I surely will not be recommending it anymore in a professional setting. We are starting to have conversations about alternatives since Lens is no longer an option for us. |
The open-source project (this repo) is still buildable, we even provide a way to build it with a single command. |
... and require out-of-band account management with the prebuilt binaries, while making it harder for open source maintainers like @MuhammedKalkan to keep binary builds going. I appreciate Lens and the work put into it a lot, which is exactly why these latest moves feel like a big middle finger to the existing community. |
And why you remove existing code? I read the reason the PR for technical reasons. But then in the same post, you said its available in the Lens Desktop binary builds. Can you explain @jakolehm why the technical reasons are not effected by Lens Desktop? You removed the extensions to save startup time, but re-introduce them downstream? Why? |
I don't want to sound too snarky but code is being removed (and added) every day, it's the normal practice with software development. If someone needs the removed code it is available via version control (git).
Lens Desktop includes many extensions that are not part of this repo (even before 6.3.0). Technical reasons for removing extensions from this repo should be pretty clear (as described in the linked issues/PRs) and everyone can still install those extensions manually to OpenLens if they desire to do so.
Startup time improvements have nothing to do directly with number of extensions being included in a build, we actually improved the performance and stability of bundled extensions loader. |
@msa0311 These reasons explained why you removed them from the installer, not why these extensions aren't available for installing. |
Then please provide the actual source code location of the extensions that are used in Lens Desktop. |
How do I do it? Could you please add the instruction to Readme or anywhere else? I believe such major changes to functionality should be reflected in the documentation. |
@kdeyko This should be in the extensions list, I opened a case for it (linked above). |
I was mistaken in my original understanding of the situation, better conversation below. |
nice, I spent so much time advocating for lens, now this. thanks. will drop and discourage the usage on my current employer |
just yesterday i added lens to our internal wiki of apps to use. and just now i removed it |
I've tested https://github.com/alebcay/openlens-node-pod-menu on OpenLens 6.4.11 and it works |
I created a pull request on this ages ago that still has not been merged. |
I've tested it too with 6.4.11 installed via chocolatey and it doesn't show up |
I did find the extension, but I don't remember where, hahaha |
I installed OpenLens using the EXE from here: https://github.com/MuhammedKalkan/OpenLens/releases |
Yes. Go to extensions (ctrl+shift+e) add this name in the box: |
it's enabled on 6.4.15, but didn't work :/ Quite a bad move to remove fonction like those whle wanting to create a modular apps without providing them. |
This worked for me |
Thanks, shell and logs are back! |
Thx all is working again!!! Nice job 🙏 |
FWIW I needed to enable the plugin after adding |
The plugin didn't worked here. tried a lot of things in various order: uninstall/reinstall the plugin. enable/disable it, restart openlens... |
The same. After last update no more logs |
Don't tell us this! |
Not working in this version. Literally the logs are the 1 feature I use the most. Please fix asap. OpenLens: 6.5.2-309 |
plugin not work on version 6.5.2-356 even after enabled. |
Seems the plugin needs to be updated. |
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) |
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. |
this was automagically fixed for me |
@alebcay/openlens-node-pod-menu
|
Workaround @shilazi/openlens-lens-metrics |
This has worked on v6.5.2, thank you. I had to open extension again and manually enable it |
lol why isnt this enabled by default? |
They have a paid version and free subscription is gone. Strategy? 💰 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. |
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:
Voila, I hope this can help someone |
In OpenLens open Extension (Win – Ctrl + Shift + e, 🍎 - Command + Shift + e), |
Dude, this was closed like a year ago. |
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
<#6823 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYWUYRFJAMJXCITOWEEANCTYXDTSVAVCNFSM6AAAAAATGWPL56VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGY3DMNRYGM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
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:
Expected behavior
I would like to see the Logs and Shell buttons like in standard Lens IDE
Screenshots
Environment (please complete the following information):
Logs:
When you run the application executable from command line you will see some logging output. Please paste them here:
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:
#1690 (comment)
But i ran
npm install
from the scoop folder (C:\Users****\scoop\apps\openlens\6.3.0\resources\app.asar.unpacked\node_modules)The text was updated successfully, but these errors were encountered: