Re:Did we market Knative wrong?
by rektide on Friday June 18, 2021 @11:24AM
(#27551333)
> I think Knative should have been just the serving component.
There are so many different ingresses (& now gateway) providers in Kubernetes. Serving continues to strike me as fairly unremarkable, and something already hotly fought for. Knative builds upon & extends a handful of the existing options, but it feels like Kubernetes Gateway API[1] will probably take over a large part of the special sauce type behavior that Knative used to be useful for abstracting over, & go a long way towards unifying serverless serving.
Eventing, on the other hand, is a hugely absent & missing abstraction in Kubernetes. There's lots of function as a service systems, plenty of fancy ingress/gateway options for routing traffic, but in terms of connecting up a panoply of services together, having a system to transport events around, there are very few Kubernetes-related offerings.
Knative Eventing is an unmatched offering. This article suggests the serving component should have been emphasized, and indeed, I think it's more core to the servlerless idea than eventing. But it's also far far better served, far more competitive a realm, to the degree that now there is participation & cooperation going on across the many providers to create a Kubernetes Gateway specification as a high-powered replacement for Ingress. What we need, what has unique value, is Knative Eventing.
There are so many different ingresses (& now gateway) providers in Kubernetes. Serving continues to strike me as fairly unremarkable, and something already hotly fought for. Knative builds upon & extends a handful of the existing options, but it feels like Kubernetes Gateway API[1] will probably take over a large part of the special sauce type behavior that Knative used to be useful for abstracting over, & go a long way towards unifying serverless serving.
Eventing, on the other hand, is a hugely absent & missing abstraction in Kubernetes. There's lots of function as a service systems, plenty of fancy ingress/gateway options for routing traffic, but in terms of connecting up a panoply of services together, having a system to transport events around, there are very few Kubernetes-related offerings.
Knative Eventing is an unmatched offering. This article suggests the serving component should have been emphasized, and indeed, I think it's more core to the servlerless idea than eventing. But it's also far far better served, far more competitive a realm, to the degree that now there is participation & cooperation going on across the many providers to create a Kubernetes Gateway specification as a high-powered replacement for Ingress. What we need, what has unique value, is Knative Eventing.
[1] https://kubernetes.io/blog/2021/04/22/evolving-kubernetes-ne...