What is Knative?

Knative is a new and exciting open source platform released as a collaborative effort by IBM, Google, Lyft, and many more. But what exactly does Knative do and how does it make a developer's life easier? Sai Vennam is back to explain the basics of Knative, showing how Knative provides developers with the building blocks for serverless platforms to run on Kubernetes.

#Knative #Istio #Kubernetes

Really loved the style used on this video, great job!

[funcmethod]

It's mind-blowing how good IBM engineers are at writing backwards!

[hassanhashemi]

Great, Your painting skill is amazing.

[ayanpal]

KNATIVE seems like a great platform! Great job team!

[vishakhrameshan]

After watching couple of videos including this the only question that’s comes into my mind is how can I deploy more than one service where there is a web application which talks with intermediate service and that service talks with another
In knative how do I specify the connection between those services as I do not directly handle any yaml files like we do on k8 ?

[AdekunleLawal]

Very clearly explained. You're really good at this :)

[brennan]

Looks like writing on clear glass in front of you but seems like there is more to it. What software, hardware, setup, etc are you using to create this presentation?

[romantsyupryk]

Thanks so much for this video tutorial.

[jkuang]

The only use case worthy of discussion ins Knative Eventing, which is the actually the core of Knative capabilities to arrange processes around events.

1) Build - we already have Jenkins and many other build processes. And frankly speaking, why do I want to bundle build platform with deployment platform?

2) Serving - Istio Server Mesh already have everything you described. What is the "killer app" you want to provide, other than trying to replace Istio? And how do you actually replace Istio? It has much more feature than just serving. What do you offer that excites me to use introduce a new component, the Knative Seving, for routing and traffice splitting which have been in Istio Service Mesh? OK, Knative has request-monitoring autoscale to zero capability. And Kubernetes has resource-monistoring autoscaling. Kubernetes takes longer to scale. Fair enough. For companies that have buget boundary, yes it the a great selling point. But many companies don't really have microservices that just sit idles for a long period of time. So it has a use case, but a use case that is relatively niched, if you don't have thousands of microservices or functions, and sitting idle even for a short period of time has huge financial impact.

3) The real use case is Knative Eventing. This capability allows any Kubernetes Cluster to hook up to an underlying event source, such as Kafka, Pulsar, Google Cloud, or many other streaming platforms. So this is a real use case. For this use case alone, it is worth to investigate the Knative and including it as part of your infrastructure (and the complexity it brings to the infrastructure)

[IVANLUISLG]

"build" is not part of knative core anymore, now is an independent componente named tekton

[sjblackhawk]

Hi, just wondering the similar features are available already in openshift, so is it bringing anything different than that? Redhat is also integrating istio and knative so what are the added features ?? Thanks

[GID-GR]

If this was a sales pitch, it would fail. The benefits I see can come from Istio by itself. I don't see other benefits. And bringing the building process into my cluster is the last thing I would want. If there are other benefits, they were not presented effectively here.

[riscnx]

What's up with KNative now a days?