Governing the Cloud Native Event Bus: Applying ServiceMesh to Knative E... (Part 1)
summary
Workshop argues that applying Istio to Knative Eventing restores centralized governance for event-driven serverless by adding Istio mTLS, policy and observability to Knative’s brokers/channels/triggers. Demo stack: OpenShift + Knative Serving/Eventing, Maistra (Istio) operator, Apache Kafka for channels, Camel K for test workloads, Prometheus/Kiali/Jaeger for telemetry. Key realities: Knative Eventing does not work with Istio out of the box — it requires sidecar injection, webhook/network-policy changes and explicit broker wiring. Demo runs (one service at scale, one at zero) but needs extra config. CloudEvents and scale-to-zero remain central.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:04Agenda
- 2:37Workshop Intro
- 4:47History of Cloud Native
- 7:10Enterprise Service Bus
- 8:14Moving to the Cloud
- 12:44Cloud Native Architecture
- 16:32Serverless
- 19:41Knative Eventing
- 23:30Governing
- 25:49Governance in Kubernetes
- 29:59Is Knative enough
- 33:00Cloud Event Specification
- 35:21Why Knative
- 40:29Knative Serving
- 42:33Knative Serving Integration
- 43:55Canadian Eventing
- 45:30Simple Delivery
- 49:55vetting
- 50:33hexagonal architecture
- 52:00Demo
related talks
35mStop Calling Knative Serverless!
01h 02mModern Event-Driven Workloads with Knative
48mLet's Go Knative
28mIstio on Knative Lessons Learned: How Istio is Fit for Serverless Platform
29mAccelerate AppDev with KIK (Kubernetes-Istio-Knative)
52mServerless with Knative
26mService Mesh, Serverless and Event Drive
34mModern Serverless Workloads with KNative and Kubernetes