Public sources are gone about openlens HOT 19 OPEN

As OpenSource lover I think frustrating to close this kind of useful app apreciated by many people.
I am fullstack js developper for years and DevSecOps for months so I propose to maintain, at least OpenLens starting from v6.5.2.
For sure it is really a big challenge and I won't be able to do it alone.
But I think with a community we can at least upgrade code base and libraries in order to use a recent Nodejs version and keep the project alive.
So I have just forked the project as is here and next step will be to publish own libs inside package folder.

Hope to find other motivated people to maintain this nice project.

from openlens.

I can't imagine that 6.5.2 is the last version we want to have. As OSes are updated, we will need updates, as security issues arise, we will need updates, as bugs are discovered, we will need updates.

Is there still an open-source community that is interested in forking the project and continuing?

from openlens.

It is sad that there is no open source equivalent :(. I'm no developer but it would be nice to form an open community around the code base before it was closed off.

from openlens.

I shifted to using devtron, which seems promising https://github.com/devtron-labs/devtron

from openlens.

As OpenSource lover I think frustrating to close this kind of useful app apreciated by many people. I am fullstack js developper for years and DevSecOps for months so I propose to maintain, at least OpenLens starting from v6.5.2. For sure it is really a big challenge and I won't be able to do it alone. But I think with a community we can at least upgrade code base and libraries in order to use a recent Nodejs version and keep the project alive. So I have just forked the project as is here and next step will be to publish own libs inside package folder.

Hope to find other motivated people to maintain this nice project.

Count me in @fbaldo31, and my axe!

from openlens.

This was foreseen about one and a half years ago. No surprises

Keeping this issue open for info to those who pays a visit

from openlens.

Why "as expected"?

from openlens.

Is there still an open-source community that is interested in forking the project and continuing?

https://github.com/LibreLens/lens tried it, but had no success. Lens is a really complex software, with tons of Javascript that not easy to understand. The undocumented re-build process was already a pain.

from openlens.

lensapp/lens@master...lens-desktop they could at least learn how to use pull requests ;)

from openlens.

Headlamp is not bad.

from openlens.

Why "as expected"?

Mirantis cancel OpenLens one year ago. While the sources still available, they clarify that the code will not touched anymore. The reason was, that the OpenLens community says Lens is great, no more development is required....

Its a logical step to cleanup the repository to have one more platform to advertise the pay variant.

from openlens.

The source code has been archived in the master branch, but it seems that they will no longer maintain.

https://github.com/lensapp/lens/tree/master

from openlens.

Not sure whether its the cracks starting to show, usually get a feel of my tools getting out of date when the fan kicks in even when the app is sitting idle (Mac). Running into this quite so often with OpenLens since this week. I am going to miss this beautiful product :|

from openlens.

This post and mention of it in reddit thread got me thinking.. as to why not make new k8s GUI client if one does not exists..

One that will be cross platform - but not web.

I zeroed in on python and QT framework for it.. and in last 3-4 days I could create a small barebone UI in it. It was not VERY hard.

https://github.com/dharapvj/kuboculus
Short video of current state of how application looks

I would like more people involved because I am Python as well as QT noob (but I have 20+years of development experience, so.. I will pick them up, eventually)

Interested folks - please respond / raise issue on the project and we can churn this out together.

from openlens.

As OpenSource lover I think frustrating to close this kind of useful app apreciated by many people. I am fullstack js developper for years and DevSecOps for months so I propose to maintain, at least OpenLens starting from v6.5.2. For sure it is really a big challenge and I won't be able to do it alone. But I think with a community we can at least upgrade code base and libraries in order to use a recent Nodejs version and keep the project alive. So I have just forked the project as is here and next step will be to publish own libs inside package folder.

Hope to find other motivated people to maintain this nice project.

@fbaldo31, I'm in. How do we communicate in the forked repo?

from openlens.

@inquinity I have openned a project in the new repo feel free to open issues & cards in the project to track what we should do.
I will sort and priorize like a product owner 😄

from openlens.

I tried other solutions and they are all sub-par, compared to OpenLens.

from openlens.

As OpenSource lover I think frustrating to close this kind of useful app apreciated by many people. I am fullstack js developper for years and DevSecOps for months so I propose to maintain, at least OpenLens starting from v6.5.2. For sure it is really a big challenge and I won't be able to do it alone. But I think with a community we can at least upgrade code base and libraries in order to use a recent Nodejs version and keep the project alive. So I have just forked the project as is here and next step will be to publish own libs inside package folder.

Hope to find other motivated people to maintain this nice project.

@fbaldo31: I am considering contributing too. Background: Cloud/Infra/DevOps Engineer at the moment and software developer (mostly frontend - Angular, Typescript, Electron) in "past life".

from openlens.

Why "as expected"?

Mirantis cancel OpenLens one year ago. While the sources still available, they clarify that the code will not touched anymore. The reason was, that the OpenLens community says Lens is great, no more development is required....

Its a logical step to cleanup the repository to have one more platform to advertise the pay variant.

There is already pricing on upstream project

https://k8slens.dev/pricing

from openlens.