News for hackers. Stuff that matters.
Re:Knative – Kubernetes-based platform to manage modern serv... by peterwwillis on Tuesday July 24, 2018 @03:04PM (#17603982)
Thank you for the link to the samples, they are much more informative. But it still doesn't quite explain it.

The samples show that you can make an app, make a container, and make a service config file, and deploy your app to K8s. Yes, we've been able to do that for some time now.

This thing is supposed to provide a bunch of advanced features for devs to not have to think about. However, the build repo says this:

"While Knative builds are optimized for building, testing, and deploying source code, you are still responsible for developing the corresponding components that: + Retrieve source code from repositories. + Run multiple sequential jobs against a shared filesystem (for example, Install dependencies, Run unit and integration tests). + Build container images. + Push container images to an image registry, or deploy them to a cluster."

"While today, a Knative build does not provide a complete standalone CI/CD solution, it does however, provide a lower-level building block that was purposefully designed to enable integration and utilization in larger systems."

So as a developer you still have to have all the things you had before, but with extra layers of abstraction now, apparently just to support hybrid cloud installations.

The marketing lingo appeals to developers as if it makes all this simple, when in fact it may be more complicated.

Re:Knative – Kubernetes-based platform to manage modern serv... by pas on Wednesday July 25, 2018 @03:08AM (#17607401)
I don't get it either. It seems like a big clapping for hot air. Yeah, it's great that there's a proper build, serve and events responsibility group, and now what? What's the "killer app" here, "the use case"?

This seems nice though: https://github.com/knative/docs/tree/master/serving#more-sam...

It seems to have OpenTracing (Zipkin) integration: https://github.com/knative/docs/blob/master/serving/debuggin... (you need to install elasticsearch and stuff for it of course: https://github.com/knative/docs/blob/master/serving/installi... )

And assigning a custom domain: https://github.com/knative/docs/blob/master/serving/using-a-... ... okay, I was hoping that I can specify a whole URL where to mount the "app" (something like https://my.fancy.pants.tld/api/app2/

It seems to me that the weakest part of this is build currently. Mostly because that's what's pretty linear and one-off, and well explored by other projects (GitLab CI/CD can easily run on and deploy to k8s), and knative is mostly about serving and eventing, meaning all the interaction between the lifecycles of stuff on k8s.