Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Knative – Kubernetes-based platform to manage modern serverless workloads

cloud.google.com

Post reply on HN
Print view View original

41–50 of 168 posts

Re: Knative – Kubernetes-based platform to manage modern serverless workloads

#41

Post by villeaikas »

evankanderson wrote: post #38
dgllghr wrote: post #19

I'm a bit confused about the "eventing" application. Is it a message bus like NATS? a persistent event log like Kafka? or is it an adapter that allows applications to interact with both?

"eventing" is building an ecosystem to make it easy to connect events to event consumers (whether they are Knative Services, k8s services, VMs, or even a SaaS). In order to do this, we've broken the problem down into 3 parts: Buses provide a k8s-native abstraction over message buses like NATS or Kafka. At this level, the abstraction is basically publish-subscribe; events are published to a Channel, and Subscriptions…

Sources also can expose multiple Types of events (EventType) they can emit, for example Github has 40 or so events, so you can choose which types of events you want to consume from your handler.

Re: Knative – Kubernetes-based platform to manage modern serverless workloads

#43

Post by smarterclayton »

dewitt wrote: post #20
gregwebs wrote: post #11

I am glad to see attempts at making a high-level platform. However, I feel like it will be too opinionated for many to pick Istio and solve build and FaaS all at once. Will there be some push-down of some of the functionality into Kubernetes? Will any of this turn into specification with alternative implementations?

One of the goals is to make the components loosely coupled at the top (so a product can choose among them as needed), and also pluggable at the bottom (so you can swap out implementations as needed, for example logging and monitoring). I expect that some of this will end up upstreamed into Kubernetes proper if it's broadly useful (autoscaler work, to pick an example), but this is still super early so let's see what p…

Re: upstreaming - Kubernetes has tried really hard to make it easy to be extended, and knative also tries to use those mechanisms and be nice, clean, reusable APIs that can be used on any Kubernetes cluster. I think it's increasingly likely that "upstreaming" an API pattern means "everyone installs it to their cluster", but we'll need to see how that plays out.

Re: Knative – Kubernetes-based platform to manage modern serverless workloads

#45

Post by isdal »

mikevm wrote: post #28

Why would you use something like this over, say, Google App Engine Flex?

I'm the engineering manager at Google responsible for both Knative and App Engine Flex. What we heard from a lot of customers is that they want a serverless / App Engine Flex-like experience but one that works multi-cloud or in hybrid/on-prem setups. The goal for Knative is to fill that need, especially for people that already use kubernetes. That being said, App Engine Flex is a solid GA service that provides a fully managed experience and runs huge services today. Knative is not there yet but is getting better by the day.

Re: Knative – Kubernetes-based platform to manage modern serverless workloads

#48

Post by bigdubs »

perfunctory wrote: post #46

So Kunernetes by itself is not high-level enough, we need a layer on top of it? Turtles all the way up.

Have you ever used Kubernetes? The abstraction it focuses on is running container images; building them and getting them to a registry is a whole separate abstraction.
Post reply on HN