kubeless
kubeless copied to clipboard
vmware-archive
consider archiving the project
Considering the lack of on-going development and limited maintenance we should do something so that newcomers don't get in a dead-end.
As original creator of the project I believe we should now archive it or at a minimum make a bold statement in the readme.
We should send future users to Knative which provides the same functionality with a huge development velocity.
Hi Seb! we appreciate your interest in the project. As you mentioned, there is active maintenance (we recently updated it to work with Kubernetes 1.16). In any case, we welcome active involvement and PRs.
I mean on Kubeless @pouledodue (I am not involved in the Knative project)
Hey Guys! This is an awesome project. We will use Kubeless in our production. It's in a POC state. I request you guys not to close this project. Thanks
I've been using Kubeless with the Serverless Framework for almost 8 months now and have a running on-prem solution running in production without problems. It actually helped to speed up the development faster than other frameworks like Garden, FnProject etc. However, I wasn't aware until now of Knative so I'll give it a look.
the project is definitely useful, but with other efforts like knative the long term sustainability of the kubeless is in doubt at best. Only Andres contributes to it now.
I would say that ** Kubless ** has more advantages than you think, for sure Kubless is very easy to implement because you don't have to install any extra network layer like it is required in Knative.
In my project, we just creating many different version of our application for QA team and auto-test, so it is important for us that K8s infrastructure is simple, use a minimum of resources and require a minimum of maintenance. From what I have seen in Knative documentation, it looks more complicated and uses more resources than Kubeless.
Of course, Knative is an interesting project, but I wouldn't say it is similar to Kubeless.
