Kel: An Open-Source, Kubernetes-Based PaaS Built in Python and Go
kelproject.com
kelproject.com
Maybe someone who's looked at the code could explain what this is for and what value it adds to the existing Kubernetes API?
(Protip: if you have six projects with six identical README files, the README probably isn't adding any value.)
The others (Java, PHP, Staticfile, Binary) were written specifically for Cloud Foundry.
Source: I worked on the CF Buildpacks team for a while.
Operations loves flavor of the month tools under active development, right?
Disclaimer: I work on Flynn
Don't know alternatives well enough to compare. Disclaimer: I work at Red Hat on manageiq/openshift integration.
Reading the page tells me little about whats actually going on inside, apart from the fact that its "Awesome, great, etc." and a bunch of irrelevant implementation details. And I'm not picking on Kel or Gondor here, its par for the course.
Techs take note: You need to up your ken on spruiking your shit. We are all special little snowflakes. Aquire customer empathy.
The 'it just works' approach might be great with simple scenarios, but it's horrible for complex use cases where you need to have detailed control over the pieces that will run in production and - once they are properly setup -, you would anyway automate accordingly your specific usecase.
Hence my: "Additional hidden complexity doesn't seem to be a good thing in this case".
Beside that, I really have no idea about what they specifically mean with "Kubernetes-based PaaS". What is it? Abstracting kubernetes cluster setup? If this is the case, i remark that I need more fine-grained access on the internals rather than additional abstractions that internally do "god-knows-what".
An important dimension is the data store. These all depend on a HA consensus based database: Etcd, Consul, Zookeeper. Set up, automation, monitoring and scaling is different with each.
Aside from this schedulers are undifferentiated technology. Tell it what you want to run and trust it'll fulfil your request.
User Interface is generally going to be a matter of taste. A beautiful web app doesn't matter if your team wants a CLI tool or a fully automated CD flow.
I don't have first hand experience by my research shows that Mesos is the most mature but is pretty heavy to set up and manage. And that DC/OS is a very polished interface.
Looking at the code, only GCE is supported.
As the others have mentioned, documentation is not great.
Disclaimer: I used to work on Kubernetes and its related projects.
I'm not sure if the OP is a project member but it would be helpful to see more details in the docs covering how exactly the project aims to or already makes Kuberenetes easier to use.
Mesos on the other hand is a data center management. You actually can run Kubernetes on top of it as you can run chronos (distributed cron), marathon (containers such as docker) etc.
When something is early in the HN hype cycle, all anyone knows is blog posts and "hello world" experiments. So it's awesome. Once you use something for a real project, you inevitably run into real-world issues or limitations. So it sucks. And you chase the dragon toward the next newly-hyped thing.
In all seriousness, though... sheesh. Django isn't even a decade old yet. Rails is older, and Sinatra and its clones are barely any younger. There really haven't been any revolutionary ideas in MVC frameworks this decade.
Django was made in 2003, Rails in 2004. Django was had a public, working, open source release in 2005, and Rails later that year.
Are you claiming that the class of project for which Django is still an excellent fit, no longer exists?
Even if you ARE putting most logic on the client-side, you will always need endpoints to provide server-side functionality.
By the time you've finished writing interceptor middleware, proper CSRF protections, and other things you'll need in a real-world application... you will have written your own MVC framework. And probably done a far more lousy job than the people who focus on that full-time.
A fairly basic server-side framework is only "huge technical debt" if you're an unemployed college student tinkering with "TodoMVC" examples.
It appears that Gondor is a managed PaaS, which can justify the additional cost for businesses with capital. It is likely not intended for hobbyists.