> Knative is about to hit v1.0 and become «stable», has a solid community.<p>I'm sorry for the negativity but I'm skeptical about the reliability.<p>AFAIK it still doesn't really address instabilities. Software crashes, hardware fails, power goes out. It is trivial to lose data, and it is trivial to be blissfully unaware that there is a possibility of data loss because when everything's green, things work perfectly fine.<p>My anecdote is, I was at a conference, listening to the "Introduction to Knative" talk. Knew just the name and that serverless is a hot new thing. There was a simple app that has sourced earthquakes and displayed a map, or something like that. Things looked neat and simple, so I wanted to jump on that bandwagon, but... My first (and quite obvious) question was, "what happens if during the event processing a hardware node that runs a service instance suddenly goes dark?".<p>I was surprised that there wasn't a meaningful answer, so I've tried to research it myself and found that - in my understanding - the event is just lost. Unless someone had taken extra care to implement such guarantees by adding more and more statefulness. As I get it, it's still K8s, and I can deploy my own message bus/queue, but this devalues Knative for me.<p><a href="https://github.com/knative/eventing-contrib/issues/656" rel="nofollow">https://github.com/knative/eventing-contrib/issues/656</a> is the issue that tracks it, and it was shoved away to the eventing-contrib repo...<p>It could be that I don't understand something, or that I've made the wrong conclusions.<p>---<p>Update: Found <a href="https://github.com/knative/eventing/pull/1949" rel="nofollow">https://github.com/knative/eventing/pull/1949</a> - seems that they've merged in something just <i>yesterday</i>. Seems that things are improving. That's good.
Still waiting for it to support basic, but crucial functionality like tolerations and node affinities. And no, using admission plugins like PodNodeSelector is not viable on managed clusters like GKE.