Ahh yes, finally. Someone makes a video promoting OpenLens. The malicious practice of Mirantis and Lens team to force account creation and then not provide OpenLens binaries or proper releases of OpenLens really put a bad taste in my mouth. We converted our entire company over to binaries we build in house when they did this.
Nice video!! Is it possible to get a video on how to deploy an HA K3S cluster and deploy openlens using a web interface inside of the cluster instead of installing a desktop client?
it doesn't seem to be possible anymore to install automatically prometheus... the "lens extensions" menu item, under the cluster settings is not there anymore
so it looks like the open lens developer has said to not expect any more updates since Lens has closed its source code. What do folks recommend as an alternative GUI for K3S?
I was happy when i saw this, but now OpenLens doesnt allow me to see logs or do anything with Pods for example ? Its just UI to show stuff, not interact (Except editing yaml.)
On the unsigned binaries- so they can inject malware into it at any time and corrupt your cluster? This is insane. This needs to be done by the team in the open with github build scripts and signing keys.
Mark, I agree, this seems to be such an easy fix and would I think garner much better adoption of the project. However, this may be one of the major reasons to choose Lens as opposed to OpenLens.
If I have kube-prometheus-stack helm chart for metrics server, what parameter i need to set in openlens settings for it to see the beautiful graphs (for cluster,nodes etc)?
Thanks for the info, actually i have a query like. I have a cluster running on AWS (Linux servers) and I downloading Openlense on my Windows 10 machine but while i was trying to connect with openlense it was not connecting, giving proxy errors. Any suggestions on fixing this issue?
@user-oc5vu5gc2s thank you for the comment! Hmm, that sounds like a connectivity issue of some sort. Sign up on the forums and we can discuss it in more detail: www.virtualizationhowto.com/community
Jeremy, looking at their development information, I see the following listed: TypeScript (front-end/back-end) ReactJS (front-end, ui) MobX (app-state-management, back-end/front-end) ElectronJS (chrome/node) NodeJS (api docs)
OpenLens has a serious problem: it doesn't show CPU/RAM for pods. Therefore compared to K9s it wins in looks but fails in functionality which is what matters for most admins. K9s shows CPU/RAM both actual and resource settings. Huge advantage. And of course it's lighter.
@@gdevelek well congrats on ignoring what he was saying. OpenLens works with pre-installed Prometheus, you just have to configure it to do so, as he was saying. And this is because it is doing proper Promethues metrics and not just `top` like k9s does.
@@jslay88 Setting your sarcasm aside, around the 7:00 mark he is showing his view which doesn't contain pod metrics. Where does he talk about configuring it for prei-nstalled Prometheus?
I don't really see OpenLens lasting very long, going to be very difficult to keep up with the paid version of Lens IDE. For just 20 bucks per month in a business scenario, it's worth it IMO.
Aaron, it will be interesting to see where it goes. However, I think at least for now, it will be actively developed as it is the project that Lens springs from.
Seeing as how its the base for Lens, the core functionallity will, by nature, be kept up with Lens. Commericialization features are all cloud based fluff that no one really needs. Lens is just only the commericialized plugins stacked on top of OpenLens.
I wouldn't recommend Lens if you're concern privacy even if disable all privacy option. Lens is still pinging command in my terminal. '/Applications/Lens.app/Contents/MacOS/Lens' -p '"xxxxxxxxxxxxx" + JSON.stringify(process.env) + "xxxxxxxxxx"'
